Sat Apr 25, 2015 6:31 pm
If you have a "scope", the output value discrepancy would be obvious. This is a larger issue than just a couple of misinterpretations -- monitor profiles that are handled differently under various display applications, whether 0-1024 means 0-100 or not (relative to RGB vs Y'CbCr 709 linear video), whether the "Auto" selection is being influenced by the sequence settings from the edit-source timeline, ambiguities in how codecs wrap code values, obsolete operating systems that still treat display media as graphics (gamma coefficient differences), and of course a certain amount attributable to poor monitor calibration. Typically the complaint is that exactly the same file will appear to be different on the same monitor under different software control.
Recently, I round-tripped a series of commercials through a UI-only system (not my setup or preference), and we got this result. Sequences were cut from original camera source material -- exported to Resolve in its native format and then rendered back out in ProRes. Changing the render scaling to full-scale digital 0--1024 fixed the issue. Several of the NLEs ask you to set the scaling interpretation on import -- Media Composer does this, and we get this discrepancy often with ProRes4444 because there is no flag reporting whether the media is RGB or Y'CbCr.
its annoying. But necessary.
jPo