FFAStrans forum

Hey. I am very sorry about this question, but how can I move the source file, after transcoding is finshed?
I work with a watch folder, transcoding is fine and the finished file is moved via "Folder" processor. But how can I move the source file, after the trnascode is done? How to identify the correct file ("Folder" does not have a file input..)

Thank you!

Hi Jan,

there are many ways to do that, one of them is to use a populate processor and set After that, it should work to move the file with a delivery processor and "move" checkbox on.

There is just one catch with that, the delivery processor will always tend to remember and use the "name" of the original file as target file name (independent of current %s_source% value), so in more complex scenarios, when we switch s_source often, we can just store the "original" source file at the workflow start to a user variable using a populate processor: In this case, you can still use the same technique from above but you set s_source back to s_my_source before you move it.

Another way of moving files is a cmd executor processor of course, instead of a populate and deliver processor you can do cmd exec like: lets know if it worked for you

Yep, another way I like to use is putting a populate variable node at the end of the workflow (after you've already delivered the encoded file etc) followed by a delivery node.

The populate node will set s_source = s_original_full so that you now have the file that got picked up at the beginning with the full path to it.
The delivery node is the same as usual and you can use all the functionality you know and love, it's just that this time it will move the original file.

Thank you! I will try it.

This is (was) working. Thank you! Now I have another question. Could you check my workflow? I need different transcoding nodes, when I work with MXF files with a "colour_range_Original: Full" tag (MediaInfo). These files are handled as full range files, but it is coded legal in real. Maybe the ffmpeg command could be rewritten to handle both cases (wrong full flag and correct legal flag)? But the important thing is, the original files won't move after successfull transcoding. In a more simple workflow your solution was fine. Any idea?

There shouldn't be any harm in using the force legal one you wrote even on limited tv range files that are correctly flagged as you're flagging them as limited anyway and interpreting them as limited.

Other than that, I can't really comment on the other NVEnc parameters as I don't actually really use it as its buffer control is sub-par and in general the quality of hardware encoding is always lower than software encoding, even on modern cards (although the bridge isn't quite as wide as it used to be).

jan2ooo wrote: ↑Thu Dec 04, 2025 2:31 pm the original files won't move after successfull transcoding. In a more simple workflow your solution was fine. Any idea?

It means that they're still being used. Make sure the workflow isn't branching out in multiple places and all conditionals are one after the other with the execute on failure.

FranceBB wrote: ↑Thu Dec 04, 2025 11:54 pm There shouldn't be any harm in using the force legal one you wrote even on limited tv range files that are correctly flagged as you're flagging them as limited anyway and interpreting them as limited.

I had errors on ProRes4444 files with this setup. So I created another ffmpeg node.

FranceBB wrote: ↑Thu Dec 04, 2025 11:54 pm Other than that, I can't really comment on the other NVEnc parameters as I don't actually really use it as its buffer control is sub-par and in general the quality of hardware encoding is always lower than software encoding, even on modern cards (although the bridge isn't quite as wide as it used to be).

I am with you, but in this case the main goal is a good speed/quality ratio.

I will investigate the other isses, thank you!