Command Executor run on encoded files.

[as1000]

I'm trying to do this in one workflow but maybe it should be split into two?

Taking an MP4 file, converting to Avid DNXHD .mxf's. This is spitting out 1 video & 4 Audio files. I'd like to call an outside Python Application which will take input file's like so: python batch.py "Z:\path\to\clip1-v1.mxf" "Z:\path\to\clip1-a1.mxf" "Z:\path\to\clip1-a2.mxf" "OUTPUTFILE.xxx"
If it is possible to do in 1 workflow that's the goal.
What is best way to scrape the files my Avid DNXHD processing node is spitting out? I feel like I'm overlooking something really simple but can't seem to find the output variables I need.

Thanks!
A

[admin]

Hi as1000,

I'm not sure if I read you correctly, but if it's DNxHD files with all audio and video into ONE SINGLE file you want then the node can already do this. You just need to deselect "Avid project". But maybe I misunderstand something? If so, can you please clarify?

-steinar

[as1000]

Thanks for the Reply. I apologize I wasn't more clear.

I'm generating an .aaf out of the split dnxhd mxf op atom files. I'm trying to include this operation inside of FFAStrans workflow. So i basically need a list of output files the DNXHD node is creating. Wondering if that is a variable inside of the system or how best to generate it.

I've tried sticking a generate text file node in there to test my options but haven't found a way to get the output files as a list or as a variable.

Thanks!!
Adam

[as1000]

Just Bumping on this thread.

Looking to get the filename location of the dnxhd encoded file as a variable. not sure if this is built in. I am trying to feed it to another command

[admin]

Ok, I think I see the problem:
When FFAStrans creates the DNxHD files as Avid structure, the %s_source% variable becomes a folder, not a file. This folder holds the various DNxHD video and audio files. So the links to those files would be:
"%s_source%\%s_original_name%_v1.mxf"
"%s_source%\%s_original_name%_a1.mxf"
"%s_source%\%s_original_name%_a2.mxf"
"%s_source%\%s_original_name%_a3.mxf"
"%s_source%\%s_original_name%_a4.mxf"

Now, the %s_original_name% is the DEFAULT setting in the "Clip name" field of the encoder node. Now, FFAStrans will evaluate the string in the the "Clip name" field of the encoder node. The default for that is %s_original_name%, but if you change it fo f.ex. "my cool clip" then your links would be:

"%s_source%\my cool clip_v1.mxf"
"%s_source%\my cool clip_a1.mxf"
"%s_source%\my cool clip_a2.mxf"
"%s_source%\my cool clip_a3.mxf"
"%s_source%\my cool clip_a4.mxf"

Hope this clarify! Also, I'm sorry for the fact that the %s_source% variable can change from a file to a path has not been made clear, and so I will fix that for the next version.

-steinar