4 Jul
2017
4 Jul
'17
12:05 p.m.
Hi Carsten.
Hmm that's interesting about Resolve. The post house presented the image
sequence as being a "DCDM" which I took to mean it should already be in
DCI colour space.
NB The post house weren't contracted by me - the filmmakers got these
materials made up and I was just presented with them to make the DCP.
Thanks again for all your help with this.
Jim
On 04/07/2017 12:19, Carsten Kurz wrote:
But thanks
loads Carsten for all the detailed info. I intend to get back on the case next week and
will post on the list when I have got to the bottom of it. My working assumption at
present is that the post house exported the TIFF image sequence with wrong white point.
That’s most likely the case. It is important to know that DCP-o-matic is specifically
targeted at the DCI parameters for it’s color conversion. If you want to bypass DOMs color
handling, it must be clear that the source media, be it XYZ-J2k or XYZ-TIFF, must already
contain ALL parameters for DCI compliant colour rendering - that is, XYZ, DCI whitepoint,
Gamma 2.6.
I played with Resolve a bit, and I noticed that the J2K and XYZ TIFF export do not
automatically conform to these parameters, but it is expected that whitepoint and gamma
are adjusted as part of the color space setting and grading process. That is, if you
simply work in rec.709 in Resolve, and then export to XYZ, neither gamma nor whitepoint is
automatically adjusted to DCI specs.
- Carsten