Forum Replies Created
-
Ah got it. You still have a copy of your QT prores, I don’t since I transcoded from DSLR H.264 but I could reconnect to the DSLR footage though…
Frederic Lumiere
Producer
Lumiere Media -
It worked for you with ProRes MXFs? I still get the ‘unsupported MXF’ error for each file.
Frederic Lumiere
Producer
Lumiere Media -
Frederic Lumiere
December 28, 2011 at 12:08 pm in reply to: MC6 to After Effects with Automatic DuckJust tested the Boris Transfer tool, same thing as AutoDuck, it doesn’t recognize Prores MXFs.
I guess it’s just a matter of time before they update their software in order to support AVID Prores MXFs since it’s so new (MC6).
Frederic Lumiere
Producer
Lumiere Media -
Nevermind – the Dnx stuff works in AE as long as it wraps the Dnx into a QT (won’t open MXF directly – at least not AVID’s).
So the issue is Prores MXF as it must be wrapped in a QT for AE to understand it and Automatic Duck doesn’t recognize it.
Frederic Lumiere
Producer
Lumiere Media -
Hey guys – any resolution with this error?
Thanks!
Frederic Lumiere
Producer
Lumiere Media -
Hmm… did a test with Dnx and AE doesn’t recognize it either. Perhaps the problem isn’t ProRes…
Frederic Lumiere
Producer
Lumiere Media -
Looks to me that the “ProRes Workflow” AVID advertises is only in AMA mode which isn’t recommended by any pro editor (for good reasons) essentially making ProRes not really useable on MC.
Looks like I’m going to have to re-transcode 40 hours to Dnx…
Frederic Lumiere
Producer
Lumiere Media -
I re-read the Media Composer 6 page on AVID puzzled by my decision to go Prores… I guess the following lead me to believe that MC6 to AE using Prores should be a no-brainer:
“Get full native ProRes support on Mac (encode and decode) and Windows (decode only) for easy integration into any ProRes workflow”
Frederic Lumiere
Producer
Lumiere Media -
Great question Scott. Well, I’m completely new to AVID. I’m one of the FCP convert after Apple abandoned professional editors. When AVID raved about the ‘Prores’ feature of MC6 I figured it would be a safer switch incase I needed to go back to FCP for this project in panic mode… Didn’t realized that for MC6 to operated really smoothly it would wrap the Prores in an MXF – which is fine I guess.
I also didn’t know if AE would do well with DnxHD (I guess it does). Anyway, I committed to the change (40 hours of footage and counting) and am now realizing that the issue is most likely the Prores wrapped in MXF that AE does not recognize.
So now it looks like I have 1 of 2 choices:
1. Re-transcode everything to DNx
2. Export AAF from MC6 to AE with the re-encode option (really don’t want to do that)
I used to teach post workflow at NAB, Macworld, etc… and I used to start my classes with ‘TEST YOUR COMPLETE WORKFLOW BEFORE YOU START A PROJECT’ and here I am. I didn’t. 🙁
In my defense, I had to wait for a new system to handle MC6 (64 bit) and didn’t want to wait on the encoding from 5D H.264. I made an assumption that Prores would be a safe way to go since I had used it for years… Well, we all know what happens when we ASSume…
Frederic Lumiere
Producer
Lumiere Media -
Frederic Lumiere
December 23, 2011 at 6:31 am in reply to: Only Prores 444 during imports and transcodes in MC6?Daniel,
You have no idea how you just gave me a major gift! Thank you!!!
Indeed, Prores 422 is now available via the transcode but the best part is that a 3hr clip being converted from 5D H.264 to Prores 422 with FCP’s Media Manager (only thing I found other than MC to keep multi tracks of audio intact) takes 10 hours on a Mac Pro 12 core with 64 GB RAM. In MC6 it takes 2 hours!
I have 40 hours of footage soon to be 100hrs!
Happy Holidays and thanks again Daniel.
Frederic
Frederic Lumiere
Producer
Lumiere Media