You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've followed a practice established long ago by the original pyTivo where you could put the Tivo metadata files in a directory named ".meta" as a subfolder to the video files. It was used to keep the video folder less clutterred, but pyTivo could stiill be able to find the metadata for each video file. Currently, when kmttg runs Atomic Parsley via the button, it looks for the metadata in the same directory as the video file, and errors out if the metadata file is not present. I have a need to update a lot of metadata files to embed that metadata into the video file using atomic parsley within kmttg, My process now requires copying the metadata files into the video folder to update and then delete the metadata files in the video folder
Please consider enhancing kmttg to search an addtional location, such as "..meta" or the path environment varable for the metadata file.
The text was updated successfully, but these errors were encountered:
I've followed a practice established long ago by the original pyTivo where you could put the Tivo metadata files in a directory named ".meta" as a subfolder to the video files. It was used to keep the video folder less clutterred, but pyTivo could stiill be able to find the metadata for each video file. Currently, when kmttg runs Atomic Parsley via the button, it looks for the metadata in the same directory as the video file, and errors out if the metadata file is not present. I have a need to update a lot of metadata files to embed that metadata into the video file using atomic parsley within kmttg, My process now requires copying the metadata files into the video folder to update and then delete the metadata files in the video folder
Please consider enhancing kmttg to search an addtional location, such as "..meta" or the path environment varable for the metadata file.
The text was updated successfully, but these errors were encountered: