Hello,
when transcoding clips in a project set to RGB to ProRes444 all files are actually ProRes422HQ.
MC tells me they are Prores444 which is not true.
When i open these files in Resolve + ffmpeg they give me ProRes422HQ as the codec.
This becomes even more strange when using different transcode settings.
If i choose Source Size and Source Framerate the file is reported by MC to be YCrCb (ffmpeg gives me yuv422p10le).
If i choose Project Size and Project Framerate the file is reported by MC to be RGB (ffmpeg gives me yuv444p10le - so that is not even RGB).
Of course in both cases the project is set to RGB, source and project do have the same raster size and the same frame rate.
Sounds like a big bug. Or?
What version of MC / Resolve are you using?
-- Kevin
MC is 8.7.2.
Resolve is 12.5.4 but it does not affect this.
Quicktime does report 422HQ too.
And just to verify, you are opening the MXF files you created during the trasncode, not exporting a QuickTime movie back to Resolve?
Also, what's the source you're transcoding from?
In Resolve you cannot open the MXF file directly. The combination of MXF with ProRes is not working there.
I can export Same as Source to MOV container (low CPU usage - heavy disk i/o).
But don't focus on Resolve - it's not an issue with Resolve. It's only a sample application to check the files.
With ffmpeg/ffprobe i can have a look at the MXF essence. This is telling me what is inside the MXF. I can rewrap (without re-encoding!) to MOV with it and also verify it with any QT based application that it is 422HQ.
I did the initial transcode from DPX 10bit link with AMA. To verify this i transcoded to DNxHR444 (which was fine) and re-transcoded the DNxHR444 to ProRes444. This one was also YCbCr 422HQ.
The reason I asked is that I recently consolidated ProRes444 QuickTimes to Avid, then exported out SAS QuickTimes, and those are reporting to be ProRes444 in QuickTime.
Now, I consolidated (instead of transcoded), but I also used MC v8.8.x. So perhaps there is a bug either in your MC version or somewhere in the transcoding process.
Any chance you can try MC 8.8.1?
With 8.8.1 (OS 10.10.5) I have just had an issue where I transcoded a 1080 50i timeline to ProRes HQ AAF for graphics. The only clips they could open where 2 Title tool place holders. A second AAF a day later using the the same export template of just 4 changed clips (replacing the place holders) and they could open all of the clips.Looking at the two sets of clips in the 1 folder showed the first group were all ProRes422HQ. The 4 updates were all ProResHQ.The original timeline had some clips with higher than HD resolutions and some with higher frame rates. The second set were all 1080 XDCAM. On the first set I may also have not used the convert option pop up at export by the timeline having mixed frame rates.Re exporting the first group using the "Convert" suggestion during the transcode and all transcoded clips were ProResHQ and worked for the graphics people. They are Mac based, use Premiere and tried opening the ProRes422HQ clips in that, After effects, QuickTime (X and 7) and Resolve without any success.
Sorry I cannot be more precise but very tight deadlines will prevent me from exploring this issue further at this time.
On another machine with version 8.6.3 i added subtitles on an existing ProRes4444 mov. after a mixdown to ProRes4444 and SaS export, the file was verified by Tektronix Aurora.
It also says that the pixel format is 422 and not 444.
There's no chance to update any machine to 8.8.x - instead i guess it will be the same with a newer version.
If you can't update, we'll have to see if anyone else on 8.6.3 or 8.7.x see this problem. I can't back rev, and it *seems* to be OK on 8.8.x, but it was a different workflow.
Kevin Klimek: we'll have to see if anyone else on 8.6.3 or 8.7.x see this problem.
we'll have to see if anyone else on 8.6.3 or 8.7.x see this problem.
I´m on 10.10.5 and have just finished a project with Alexa APR 444 media ..
Now just to find the time to install an older Avid version and test ..
Tomas
Hi Kevin,
are you verifying your files with any other application than Media Composer?
I'm asking because in the versions on my place (i do have 8 MC seats) all MCs shows ProRes444 in the bin view.
But all other applications do say it is 422.
If MC is the point of failure it should not verify itself. I don't believe that this is fixed accidentally in 8.8.x.
Thanks.
QuickTime 7 and AE report the files as ProRes 444, not just MC.
ok. i did it the hard way. i upgraded the least significant machine to 8.8.2.
the bug is still the same!
1080p25 rgb project -> ama link dpx -> transcode with or without source or project dimensions and framerate = codec profile 422HQ.
it is not 4444!
Hmmmm...perhaps the cause is related to PAL or the DPX files?
Mine was 1080p/23.976, standard QuickTime movies in and out.
i hope you agree that if i select ProRes444 in MC the resulting file should be ProRes444 and nothing else - no matter what the source file is. The file format, codec, framerate or whatever detail of the source file is not responsible for things generated inside MC.
As you can read above i transcoded a DNxHR444 file to ProRes444 with the same result.
Please give me a brief description what to do to convince you that this is a bug.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller