I've exported a 1920 x 1080 DNxHD QT from Media Composer. It successfully plays in QuickTime player with picture and audio. But when I bring it into Adobe Media Encoder, I can find no setting that brings up video. I tried to transcode it to H.264 and, under video settings, it sees the file as 720 x 480 and at the end of the transcode, I have audio, but no video.
Any idea what I'm doing wrong?
Martin
Not sure why you are seeing this but ....
I would suggest leaving DNxHD QT behind. Try making an DNx HD Op1a MXF instead.
1. It will be faster.
2. It will be more reliable.
3. QT is the devil.
Jef
_____________________________________________
Jef Huey
Senior Editor
Old Stuff http://vimeo.com/album/3037796
Well, fine Jef, but then what. Can I pull DNx HD Op1a MXF into Media Encoder?
Yes, you can put a DNxHD Op1a into Media Encoder. If it can spit it out, it can bring it in.
You can also restart Media Encoder and see if it works with the original file. It sometimes gets...silly.
One thing you can't do with the more recent Media Encoder releases is use a QuickTime reference movie. They took the cue from Apple regarding legacy format support and stopped reading QT Reference movies.
Must think of something clever to go here...
With effect from the 2018 version Media Encoder dropped QT support. See here:
https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html
The 2017 version still supports it.
hbrock: You can also restart Media Encoder and see if it works with the original file. It sometimes gets...silly.
That seemed to do it. When I tried this morning it accepted the file.
Thanks,
GT: With effect from the 2018 version Media Encoder dropped QT support. See here: https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html The 2017 version still supports it.
For clarification, Adobe CC 2018+ drops the dependency from QT7. It still supports the QT platform but through its own engine. DNxHD MOV should still be viewable in 2018.
DQS
www.mpenyc.com
Martin in Chicago: hbrock: You can also restart Media Encoder and see if it works with the original file. It sometimes gets...silly. That seemed to do it. When I tried this morning it accepted the file. Thanks, Martin
Good news. You still should play with the Op1a mxf workflow. It is the way forward.
I guess I left out a couple of the steps I went through last night. Per your suggestion, Jef, I did try an Op1a mxf export and then brought it to ME. Last night, ME rejected it, this morning it was happy.
Now I just need to read up on what Op1a is.
Martin in Chicago:Now I just need to read up on what Op1a is.
MXF is a container like MOV, MP4, etc. and part of the larger AAF data format.
OP1A is just a subset of MXF. It is very similar to Avid's native MXF format (OP-Atom). The biggest difference is OP1A has the audio essence embedded and not separated.
Thanks Dom, that helps.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller