Variable for destination file?

[momocampo]

Hello,

Is it possible to catch a variable for the destination file? Strange I didn't look for before but now I need one.
For example :
Monitor folder> encoder> [destination variable for new encoded file]> command executor with this destination variable.

Someone knows how to do that?

Thank you very much.

Cheers.

B.

[emcodem]

Hey Benjamin,

%s_source% is what you are looking for. I's value will change after each and every step which created a new file.
Some example:

"Monitor folder" > %s_source% == "\\server\share\inputfile.mxf"
"A/V Decoder" > %s_source% == "...ffastrans_cache_folder\jobid\some_guid.avs" (the source file changes to an avisynth script file here)
"encoder" > %s_source% == "...ffastrans_cache_folder\jobid\inputfile.mp4" (ffmpeg reads the avisynth script and generates an mp4 file)
"deliver to folder" > %s_source% == "...outputdirectory\inputfile.mp4" (depending on the settings, deliver to folder generated a new filename and moves the filt to a new directory, it will override s_source with the new information)

When using the command executor, you can use %s_source% as the path to the latest file of interest in the workflow on input. In case your command executor generates a new file, you check the "set %s_source% to value... option and input the path and name to the file that was generated by the command executor -> this way you can use other standard processors after the command executor.

Please try to use the "generate text file" processor and write %s_source% to a text file after each step (check the "append" option). this way you can see how s_source changes while the job is executing

cheers,
emcodem

[momocampo]

My god!!!!!
Damn! I was always sure the %source% variable was only for the input file. I'm going to test this immediately !
Thank you very much for this complete explanation, very very useful
Cheers my friend.

Benjamin

[ThomasM]

+1
thank you for this explanation, emcodem!