Adobe Media Encoder will do it but it adds 3:2 pulldown not 2:3. Also it creates files with non drop code. I haven't found a way to change the time code to drop in AME but I use QT Change to make it drop frame after the conversion.
Given the streaming dominates broadcast quality better make sure the 2:3 or 3:2 pulldown is acceptable. Some cable networks no longer allow 2:3 pulldown or any interlace artifacts, of which 2:3 pulldown is deemed to be an interlace artifact. Bottom line is that when it goes to Hulu etc.... the split frames cause issue. Given they air old series TV like Rockford Files etc... I don't know why they can stream those but not modern day 2:3. I'd bet it's that much of the modern day is random cadence so it's harder to remove pull down. It has been pointed out by Mr. Oliver that much of the old series TV that was onlined on tape also had random cadence so again I don't know why they can't process modern random cadence like they seem to do for antique random cadence.
It's all just a moving target. My current series we finally jumped into 23.976 but then they want the tape backups to be 59.94 while the primary files are 23.976. I guess they intend to add pulldown or 2:2:2:4 to the files for broadcast but want the true 23.976 file for streaming concerns. Now we can't seem to figure out what time code they want on the slates. We had thought we'd be delivering everything at 59.94 with pulldown so everything is zeroed and slated in DF TC but now with the files being delivered at 23.976 the slates still read in DF TC. My gut says DF for actual running time is the way to go because I assume they will take my 23.976 file and create their own 59.94 file for broadcast purposes. We are still waiting for clarification on this.
If you want to stay in Avid you can do the mixdown in 23.976 and open a sequence in 59.94 project using the mixdown then adjust the motion adapter to your delivery requirement of 2:3 pulldown or 2:2:2:4 cadence. Wouldn't it be nice to have universal mastering capabilities with files?
Posted by: Mark Spano <cutandcover@gmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
No comments:
Post a Comment