-
Transcode bug?
Hey y’all,
When I’m transcoding an AMA ProResHQ file to an MXF proResHQ file, I’m given an insanely large “Space Required” quote. What should be 54 GBs is quoted at 270 GBs. When the file is completed, its the right size, and a quote for DNx space is also the right size. There is also no difference in the quote size between Proxy and HQ. Is this a know bug? Is there anyway to defeat the Space Required quote so that I can properly transcode?
My source material is ProResHq and my delivery format is as well, which is why I’m trying not to go to DNx, but, of course, I will if needed. I’m on OS X MC v6.0.1. Software only.
-
4 Replies
-
The secret for native MXF wrapped ProRes in Media Composer is to import, and not AMA. With AMA, it will do through a decode, re-encode process even if you select the same codec/data rate.
The process is to import, which will be a fast import.
Michael
-
[Michael Phillips] “The secret for native MXF wrapped ProRes in Media Composer is to import, and not AMA. With AMA, it will do through a decode, re-encode process even if you select the same codec/data rate.
The process is to import, which will be a fast import.
Michael
“Thanks, Michael. I’m getting conflicting reports about AMA not doing Fast Import with ProRes. According to the Avid website it does, but you and a few others have told me it doesn’t. Its also been suggested by several people as the best way to avoid the notorious Gamma shift, which it does seem to do.
On the other hand I did two direct Fast Imports last night (because of the disk space counter bug) without any Gamma issues, so maybe there isn’t a problem at all. Maybe its just that I hadn’t been using the Media Creation settings properly in the past. Its the little things that take a while to drip in.
-
I was told by engineering that the only way to keep ProRes as ProRes but got from a QT wrapper to MXF was to an import with the proper import settings and codec set. Setting should be “proper size/aspect ratio” and Rec.709 for color space. For destination codec, select the same one as source (whatever it is on the original file). Marketing can get a little ahead of itself with AMA being the second coming of “you know who”. but it still has a ways to go to be that.
Michael
-
[Michael Phillips] ” was told by engineering that the only way to keep ProRes as ProRes but got from a QT wrapper to MXF was to an import with the proper import settings and codec set.”
Cool! Can’t argue. It worked flawlessly for me last night. Thanks.
Reply to this Discussion! Login or Sign Up