Improve Handling of Watch Folders, Image Sequences, and "Source" Folder
Many times animations are rendered out in image sequences, and while the watch folder implementation is helpful to transcode to other video formats, the system has one critical flaw:
Currently, if you import an image sequence into a watch folder, and there are multiple output presets associated with that watch folder, only the first process completes successfully. Any other processes after that fail to transcode - since the source images have been moved to the source folder and are no longer available in the watch folder.
It would be awesome to improve/implement the following:
Allow the user more control and customization to define the source folders in the preset. This could be used using tokens like in Cinema 4D. ie $date, $time, $fileformat etc.
Prevent image sequences (or any file format) from being moved to the source folder before all subsets/outputs in the preset have been executed.
Introduce a nodal visual system such as FFASTrans that allows for multiple workflows. Something like AE's mini flowchart comes to mind (this is likely a stretch - but you're Adobe!).
Thanks for everything.
rawandrendered
shared this idea
1 comment
-
edouard
commented
I agree!
It would require a system that detects that for such file, in the control folder, has already been transcoded.
This could be done via file(s) "ignore" a bit like Git with the ".gitignore".
This will allow the "source" file to not be moved after transcoding.