Jim Simon wrote:I'm still lost. I'm just gonna beg off this one.
It is complicate.
1) lets say that you set the timeline color to rec709/gamma2.4. When you export a DCP, resolve will implicitly convert rec709/gamma2.4 to XYZ/2.4 all is good, IF AND ONLY IF you where looking and coloring to a rec709/gamma2.4 screen, if by any chance you where correcting on a P3DCI white point projector, the conversion will be wrong.
2) but, let’s say that you want to use that setting in the color phase. I have an Alexa camera, and my color space is AlexaLogC. Let’s say that I want to take advantage of the very convenient right click menu in a node that convert the color space I use for my coloring to (for example) linear light. Very simple, I do right click, [linear] (or Lab, or whatever) and do my correction/effect, whatever.
What really is happening under the hood, resolve use the Timeline setting to go from the coloring space to [linear] in my example, and if I want to do it correctly, I have to set the [timeline color] to AlexaLogC.
Same for the default in [ofx color space transform]... they obey to [timeline coilor] setting and in my case, if i want to uniform a timeline color space I need to set it up to AlexaLogC.
If you have the color space in AlexaLogC and you got to the final display (let’s say P3DCI) with a look/LUT/whatever, and you attempt to do a DCP, the math in the delivery page will be AlexaLogC to XYZ/2.6..... being completely wrong....
There is that....