Copy link to clipboard
Copied
I hope someone can help me with this...
The workflow in my studio has people working in Premiere Pro CC feeding an Avid Media Composer that's tied in with live broadcasting hardware.
The Premiere Pro machines export QuickTime DNxHD directly to the Avid Media Server and the files are immediately live for the main editor to use.
This week, our exports suddenly will not link through the Avid's normally stable AMA linking process. All the Avid sees is a green or yellow blank screen, but the data is all still in the Quicktime file. My Avid Codecs on my Premiere machine only show a blank white screen too, but if I throw the .movs into Handbrake and convert them to an .m4p, they play fine in Windows Media Player.
I've tried reloading the Premiere Application and I've gone over the export settings a dozen times, using my existing presets and every other combination we can think of. I also reinstalled the Avid codecs on my machine, which were already up to date.
The kicker: we used an old machine running Premiere CS5 and those work perfectly, right into the Avid... and all the settings there match our presets on the current machines.
We were able to export to AVC-Intra and those linked okay, which saved the day for us, but you cannot link files/animations with no audio, so the editor wants us to get the .movs working.
In broadcast work, sometimes we're forced to use legacy formats and I sure hope someone can figure out why this is happening.
Thanks, John.
2 Correct answers
They changed the way they 'build' mxf files a while back, to be more 'technically correct' ... but there's quite a number of users who've had problems trying to work between Pr and Avid with the new supposedly correct file header or whatever.
Let's make sure one of the format supers is aware of your issues ... @Fergus H ... an mxf issue here ...
Neil
I reinstalled Version 22.2 in Premiere, After Effects and Media Encoder and my problem is SOLVED.
I wish Adobe would have dealt this issue differently.
Thanks friends.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Anybody have any ideas here? I guess I need to send a ticket to Adobe?
Copy link to clipboard
Copied
Are those Quicktime DNx files? If so, can you use the MXF-op1a form of DNx?
Neil
Copy link to clipboard
Copied
Thank you for your suggestion. I'm trying this now...
Copy link to clipboard
Copied
So yes, the MXF.op1a form of DNx works just like the AVC-Intra 100. These both work.
But when I tried exporting in these formats with the audio disabled, the Avid Media Composer chokes and crashes. I'm guessing these formats use audio for clocking or something.
Our Quicktime exports can link 'with' or 'without' audio... and for the dozens of little animations, our editor wants us to use Quicktime .movs.
So if the machine running older Premiere generates Quicktimes that the Avid links to, then why won't MY machine running the latest version of Premiere work? I'm wondering if my machine won't properly utilize the Avid codec, even though I've reinstalled it. (??) Is there any way for me to check that?
Thanks for your ideas.
Copy link to clipboard
Copied
They changed the way they 'build' mxf files a while back, to be more 'technically correct' ... but there's quite a number of users who've had problems trying to work between Pr and Avid with the new supposedly correct file header or whatever.
Let's make sure one of the format supers is aware of your issues ... @Fergus H ... an mxf issue here ...
Neil
Copy link to clipboard
Copied
I reinstalled Version 22.2 in Premiere, After Effects and Media Encoder and my problem is SOLVED.
I wish Adobe would have dealt this issue differently.
Thanks friends.
Copy link to clipboard
Copied
Your issue may be related to this:
Announcement: Changes to QuickTime DNxHD support in Premiere Pro 22.3
Also, QuickTime ProRes 422 HQ and QuickTime ProRes 44444 with Alpha instead of QuickTime DNxHD should import fine via Avid Media Access, but take just a little longer.
-Warren
Copy link to clipboard
Copied
Thank you Warren. I don't know why I couldn't find that when I searched, but THIS IS the issue. Many thanks.

