I have a simple 8.1 workflow:
Watchfolder01 > DNxHD.mov > FTP to server. Seems to work great with what I pitched to it so far.
But this is where it gets complicated:
I have a server that will play out DNxHD.mov files. The server is not particular on things such as 145, 220 bitrate, or how many audio channels it has.
What I would like to do is that when any type of interlaced DNxHD.mov file is placed in Watchfolder01, that file is not "reprocessed" but gets sent FTP to the server. Additionally when a DNxHD.MXF or even a DNxHD.mov of a "different frame rate" is dropped into the folder, it does get processed into the selected DNxHD.MOV format before being FTP'd.
I would love to have a GUI form of an acceptable to move to the next stage without processing pick list, but I know that is a big ask.
Why would I need this? Because "I" will not be the one that will be pitching to the folder, speed of transfer and less processing on the server is better.
If this is covered in some tutorial or additional feature somewhere please let me know the link. -Thank you
Need a third folder option or is it just in need of scripting?
Re: Need a third folder option or is it just in need of scripting?
Hi Ray4x4x4,
This scenario is exactly why you have the "Conditional" node and loads of media variables, so that you can construct workflows that adapts to the incoming media. Take a look at the "Conditional" node and the variables section and see if you can figure out how to use it. If you can't, please let me know.
PS: Look for the %i_interlaced% and %f_frame_rate% variables...
-steinar
This scenario is exactly why you have the "Conditional" node and loads of media variables, so that you can construct workflows that adapts to the incoming media. Take a look at the "Conditional" node and the variables section and see if you can figure out how to use it. If you can't, please let me know.
PS: Look for the %i_interlaced% and %f_frame_rate% variables...
-steinar
Re: Need a third folder option or is it just in need of scripting?
Hi steinar,
Thank you, I do have a couple of questions. I just want to verify that when using the %f_frame_rate% the example is shown looks to be in frames, whereas in the DNxHD Encoder block, the pick list seems to be shown in fields. The variable is truly wanting a value in video frames (where 2 fields = 1frame)- yes?
The other I have question is:
If I was to use the codec variable, is it the commercial name "DNxHD", or is it "AVdn", or is it "DNxHD 145", or perhaps something else that the variable is looking for? Would it be case sensitive?
I admit naivete as I do not know if 29.97 is used in other standards. I know that interlace is not the "world standard" so the following is background info for those readers in not familiar with NTSC legacy issues as the moderators are:
In the NTSC legacy areas, 1080i 29.97 frame rate is the same as saying it is at a 59.94 field rate. However, a 59.94 frame rate setting is not valid although ffmpeg and certain other software will be happy to do it. In 720p format, there is a 59.94 frame rate, and a 60 frame rate. Yet 29.97 as a rate for 720p is invalid, making the fields/frame assumptions all the more confusing. So what best describes what the NTSC legacy frame rate needs to be in limited shorthand? To add to the mess, some software will list a 1080i 29.97 frame rate selection for transcode as "1080i60" (Even pricey professional video editing software enjoy playing this special mind game for their export transcode pick lists)
Regards,
Ray
Thank you, I do have a couple of questions. I just want to verify that when using the %f_frame_rate% the example is shown looks to be in frames, whereas in the DNxHD Encoder block, the pick list seems to be shown in fields. The variable is truly wanting a value in video frames (where 2 fields = 1frame)- yes?
The other I have question is:
If I was to use the codec variable, is it the commercial name "DNxHD", or is it "AVdn", or is it "DNxHD 145", or perhaps something else that the variable is looking for? Would it be case sensitive?
I admit naivete as I do not know if 29.97 is used in other standards. I know that interlace is not the "world standard" so the following is background info for those readers in not familiar with NTSC legacy issues as the moderators are:
In the NTSC legacy areas, 1080i 29.97 frame rate is the same as saying it is at a 59.94 field rate. However, a 59.94 frame rate setting is not valid although ffmpeg and certain other software will be happy to do it. In 720p format, there is a 59.94 frame rate, and a 60 frame rate. Yet 29.97 as a rate for 720p is invalid, making the fields/frame assumptions all the more confusing. So what best describes what the NTSC legacy frame rate needs to be in limited shorthand? To add to the mess, some software will list a 1080i 29.97 frame rate selection for transcode as "1080i60" (Even pricey professional video editing software enjoy playing this special mind game for their export transcode pick lists)
Regards,
Ray
Re: Need a third folder option or is it just in need of scripting?
FFAStrans will normally show 25 and 29.97 for interlace video. So, when the variable %i_interlaced% > 0 then it's interlaced, and you can double the frame rates 25->50 or 29.97->59.94.
I advise you to create a dummy "Conditional"-node to test the variables and submit a sample file directly to the node. You don't need to connect it to any other nodes. If you wonder what data a particular variable represent, you just compare it to an empty string and check the status monitor. It will display the result.
Only the '==' operator is case sensitive.
-steinar
I advise you to create a dummy "Conditional"-node to test the variables and submit a sample file directly to the node. You don't need to connect it to any other nodes. If you wonder what data a particular variable represent, you just compare it to an empty string and check the status monitor. It will display the result.
Only the '==' operator is case sensitive.
-steinar