FFAStrans forum

The wanted behaviour:
- I put filexyz.mov in the watchfolder and it gets transcoded
- shortly after that I modify the file (e.g. new version, updated duration) and copy it to the watchfolder again, resulting in the same filename, with different timestamp
- ffastrans detects that the file has changed (timestamp is different), and transcodes the file again

It seems the current situation is: updates to the file are not noticed and the updated file(s) are not transcoded again.
Is that a config issue or is that the expected behavior?

Hello wvku,

I think it's normal and it's because the media cache is active.Without cache there would be a loop (FFastrans will transcode and transcode again indefinitely).
So, if you want to avoid this, right clic on your workflow, maintenance menu and check "remove monitored file record from history cache". BEWARE, if you want it works, you must add a command executor node at the end of your workflow to delete the original file (with "%comspec% /c "del /f /q "%s_original_full%""). In that case, drop your video file, first encoding, delivery encoding file, delete original file. Drop again the same original video file and it will be re encoding and delete at the end, etc.
Last thing, don't forget to configure your delivery node with overwrite or unique name for a well delivery otherwise "file already exists".



Benjamin

thanks Benjamin. Will take a look at this workaround. Sounds promising.
In general, don't think this workflow is very uncommon. Would be nice if there would be more standard support for this in the future.

You're welcome ! I know this kind of workflow is quiet useful when you have to do several modifications of video files.
Cheers.

B.