Feature: Save thumbnails to relative folder
I'd like to be able to save thumbnails to a relative folder that doesn't require editing. It seems that I can currently only save to a specific folder, or the source folder. It would be nice to be able to save to e.g. {source}\thumbs\, for instance. If there are subfolders included in the process, an option to save these either in {video source}\thumbs\ or {top level source}\thumbs\{subfolder}\ etc.
Yes, but it doesn't do the above thing exactly. You need to select a specific folder for that one, from what I can tell.
I'd like to set it to e.g. "\thumbnails\" and not "C:\thumbnails\" with folder preservation.
As "C:\thumbnails\" with preservation, all processed files would be saved as:
"C:\thumbnails\{source path}\filename.jpg"
With "\thumbnails\" it would always look like:
"{source path}\thumbnails\filename.jpg"
No matter which folder I choose as source. The position is relative to the source.
And stuff like "..\thumbnails\" would output to "\thumbnails\" on the same directory level as "{source path}\"
I'd like to set it to e.g. "\thumbnails\" and not "C:\thumbnails\" with folder preservation.
As "C:\thumbnails\" with preservation, all processed files would be saved as:
"C:\thumbnails\{source path}\filename.jpg"
With "\thumbnails\" it would always look like:
"{source path}\thumbnails\filename.jpg"
No matter which folder I choose as source. The position is relative to the source.
And stuff like "..\thumbnails\" would output to "\thumbnails\" on the same directory level as "{source path}\"
Hmm, it'd only make double folders if you set it to do that, so I'm not sure you got the right idea. Sorry that I fail to explain it properly.
It's basically the same as choosing a folder with "Save thumbnails to your folder", but with the source folder deciding the top level.
Example:
I have videos in "C:\My Videos" and "D:\Import\Phone Videos". I want to make thumbs for all videos in both those folders, but save thumbs to relative folders called "thumbs". Setting up this in the program and adding those videos to the processing list, thumbnails will be saved in "C:\My Videos\thumbs" and "D:\Import\Phone Videos\thumbs" respectively, without me having to do anything in between because the program saves thumbnails to "{source folder}\thumbs".
Extended example for certain cases:
Like with the "Preserve folder structure", it would also be nice to have a similar option here when subfolders are included, to save all thumbnails relative to the top level source folder, or relative to the video source folder. So if in the above example exists a "C:\My Videos\2014-11" and "C:\My Videos\2014-10" in addition to videos in "C:\My Videos", you can easily set it to save all images in "C:\My Videos\thumbs" (relative, but static as top folder), or make a new directory for each level: "C:\My Videos\thumbs", "C:\My Videos\2014-11\thumbs" and "C:\My Videos\2014-10\thumbs". I assume this extended example of a static top level folder would only work well if you tell the program to make thumbnails of all the videos in the folder and subfolders of the chosen directory. I.e. Telling VTM to "Make thumbnails for "C:\My Videos" and its subfolders. For my own use, I just want to see the basic relativity, where it makes a custom (in this case: "\thumbs") folder relative to each video source.
And as an extra note, in case it's not obvious, I want the folders to be customizable. I used "\thumbs" here for consistency, but it could just as well be "\cascade\1\" or "\thumbnails in here". The main point is using the video source as the top level, and then set it to whatever you want/need below that. There could even be previously existing subfolders you'd want to nest the thumbnails or screenshots into.
Currently, from what I can see, there's only the choice of using the variable {source folder} (with no subfolders) or a {static output folder} (with an option to have the same subfolder structure as the source folder). It's not hard to move the thumbnails to a custom folder manually after making them, but automation would be nice.
It's basically the same as choosing a folder with "Save thumbnails to your folder", but with the source folder deciding the top level.
Example:
I have videos in "C:\My Videos" and "D:\Import\Phone Videos". I want to make thumbs for all videos in both those folders, but save thumbs to relative folders called "thumbs". Setting up this in the program and adding those videos to the processing list, thumbnails will be saved in "C:\My Videos\thumbs" and "D:\Import\Phone Videos\thumbs" respectively, without me having to do anything in between because the program saves thumbnails to "{source folder}\thumbs".
Extended example for certain cases:
Like with the "Preserve folder structure", it would also be nice to have a similar option here when subfolders are included, to save all thumbnails relative to the top level source folder, or relative to the video source folder. So if in the above example exists a "C:\My Videos\2014-11" and "C:\My Videos\2014-10" in addition to videos in "C:\My Videos", you can easily set it to save all images in "C:\My Videos\thumbs" (relative, but static as top folder), or make a new directory for each level: "C:\My Videos\thumbs", "C:\My Videos\2014-11\thumbs" and "C:\My Videos\2014-10\thumbs". I assume this extended example of a static top level folder would only work well if you tell the program to make thumbnails of all the videos in the folder and subfolders of the chosen directory. I.e. Telling VTM to "Make thumbnails for "C:\My Videos" and its subfolders. For my own use, I just want to see the basic relativity, where it makes a custom (in this case: "\thumbs") folder relative to each video source.
And as an extra note, in case it's not obvious, I want the folders to be customizable. I used "\thumbs" here for consistency, but it could just as well be "\cascade\1\" or "\thumbnails in here". The main point is using the video source as the top level, and then set it to whatever you want/need below that. There could even be previously existing subfolders you'd want to nest the thumbnails or screenshots into.
Currently, from what I can see, there's only the choice of using the variable {source folder} (with no subfolders) or a {static output folder} (with an option to have the same subfolder structure as the source folder). It's not hard to move the thumbnails to a custom folder manually after making them, but automation would be nice.
Thank you for such rich explanation.
Finally, it is clear to me
I could implement an approach, but it will make interface a bit more complicated.
I have not decided yet to implement it or not.
My idea was to use Videonizer and do not care about physical location of videos and pictures (including thumbnail sheets) on the disk.
Finally, it is clear to me
I could implement an approach, but it will make interface a bit more complicated.
I have not decided yet to implement it or not.
My idea was to use Videonizer and do not care about physical location of videos and pictures (including thumbnail sheets) on the disk.