The Prores specs specifically say that they are always video range. -deke
On Wed, Jan 4, 2012 at 12:13, Ed Mendez <[email protected]> wrote: > We are running into a slight offset in color/levels between ProRes422HQ > files on different systems. Resolve, Smoke, and Nuke. Just wondering if > anyone has run into a similar issue? I don't believe it is a .mov gamma > flag thing, but I could be wrong... > > We rendered some Rec709 ProRes422HQ files out of Resolve to DPX – no color > correction added. When the resulting DPX sequence was brought back into > Resolve and compared to the original ProRes file – everything > (colors/levels) matched nicely. They also matched when compared in Smoke. > However, when the ProRes file was compared to the DPX files in NUKE the > ProRes file looks like it is being read as video range while the DPX > sequence is being read as full range. Consequently the blacks are lifted > and the whites dropped when looking at the DPX sequence. The read nodes > for each the ProRes and DPX's are both set to Rec709 as is the display. > Equally there is a similar offset when setting the read nodes to any of the > other colorspaces as well... > > To add to the matter – when the same ProRes file is rendered out of Nuke > via Rec709 in a write node, the resulting DPX sequence will match the > ProRes when viewing back in Nuke… > > Is there any way to tell Nuke to read a file as full range or video range? Or > is the another way to address this issue? > > Thanks, > ed > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
