I've sorted this out, I think.
In a nutshell, same-as-source quicktime exports of DNxHD and ProRes
material matches if the export uses RGB levels, but not if they are
exported with CCIR levels. I don't know if that's a bug, or just the
way life is with ProRes, but it's certainly worth knowing.
Confirmed by aligning the exports in After Effects, composited using
difference mode. The RGB exports are almost identical (pixel difference
values in the range 0-2), while the CCIR exports have much larger
difference values between the ProRes and DNxHD versions.
My impression is that the ProRes same-as-source export produces the same
values regardless of whether you choose CCIR or RGB, but I didn't get
around to confirming this in After Effects.
--Michael
On 12-09-17 9:28 AM, Michael Brockington wrote:
>
> I thought the ProRes native handling was supposed to fix this kind of
> stuff, but the following gives me unexpected results (Running MC 6.0.3
> software only on 10.7.4)
>
> 1. import the belle-nuit test chart as DNx220
> 2. transcode to ProRes HQ. The original and the transcode appear
> identical inside Avid.
> 3. Export a still of both DNx and ProRes as TIFFs -- they appear
> identical.
> 4. Export both the DNx and ProRes versions same-as-source, CCIR levels.
> They look different. The ProRes version looks like it has been exported
> with RGB levels -- blacks crushed, whites truncated.
>
> This should work, right? Can anyone else confirm this behavior?
>
> Thanks,
> --Michael
>
>
[Non-text portions of this message have been removed]
No comments:
Post a Comment