-
Final Cut Pro to Avid Workflow Debacle (why is 24p a thing?!)
Hi everyone.
I am running Avid MC6. My project lives on an internal RAID while all the media files sit on two separate 8TB drives. One is mostly empty and was where I was going to dump all my MXF media. The other, contains the project so far.
The Story Thus Far:
The footage has all been converted to ProRes 422(Proxy). Some footage is 23.98fps, some is 24fps. It varies from card to card. The director organized all the footage in Final Cut Pro 7, hence the decision for ProRes and the lack of attention regarding FPS. They also ran all the footage through PluralEyes so the media is synced with the production audio. All of this is great. Except now we’re using Avid instead.
The Problems:
I assumed I would get back a bunch of raw dailies. They shot on the C300 (at 24p), occasionally a 5D, GoPro, the usual suspects. When I opened the drive I was surprised to find that everything had already been converted to ProRes 422 Proxy. Before knowing that our media was ProRes, my plan was to transcode all of it to DNxHD36. But after researching a ProRes workflow, it seems I can rewrap the ProRes in an MXF codec and not have to convert it all to DHxHD. I planned on doing this via AMA and CONSOLIDATE or Right Click –> Import.
But hold on, what about all that organization in Final Cut Pro? I dug out my old Automatic Duck plugin, as it’s the only one I could think of that would help make the jump from FCP to Avid relatively painless. I export a timeline using the following settings:
I imported my AAF into Avid and it came through but with all the media offline. So I Right Click –> Relink to the files on the original media drive. Either Avid fails to find them or I get a Media Segmented error and Avid crashes. Okay…
In the past, I would use Batch Import to get files back online and transcode them at the same time. So I right click –> Batch Import –> point to media drive –> choose Apple ProRes 422 Proxy MXF –> change RGB to 601/709 –> Import. It works! The imported sequence from the FCP-created AAF even updates with the new footage.
So now I think I’m a hot shot and figured out my problem. I can keep the PluralEyes sync and still have MXF files. So I export another AAF from FCP. Follow the same procedure. Right click to try my batch method except the footage is 24p and…
Well shit. That kind screws everything up. So I try to relink to the original media again. Crash. I import a single 24p clip and try to consolidate it but I get the “foreign compression types” error message.
So now I have a ton of media that’s a rogue FPS and a bunch of PluralEyes sync files and project organization in FCP that seems virtually useless now if I can’t figure out a way to link the Timeline to something that is Avid-friendly. Not to mention Avid can’t even handle the 24p timeline and makes a 23.98 copy instead.
Would I be better off importing everything wrapped as an MXF? Can I still do a PluralEyes sync from Avid afterwards? How will my audio be affected if I change everything to 23.98?


