Wed Jun 12, 2024 11:43 pm
Same issue on my end. Round tripping DCP back into Resolve has a lifted gamma. I am submitting to a festival that is projecting in DCI-P3 Gamma 2.6. Film is mastered in Rec.709 Gamma 2.4. Resolve project settings are DaVinci YRGB, Input timeline Color Space is ARRI LogC3, Output is Rec.709 Gamma 2.4.
Round trip steps are:
-CST output node on timeline node tree from Rec.709 G2.4 to DCI-P3 G2.6 (with no tone/gamut mapping or any other transform settings)
-DCP Render
-Import DCP MXF, lay it on its own Timeline with Input Color Space set to XYZ (CIE) Gamma 2.6, and Output Color Space set to Rec709 Gamma 2.4
-Apply CST to the DCP MXF on this timeline and set input to XYZ (CIE) / Gamma 2.6, and Output to Rec.709 / Gamma 2.4 (with no tone/gamut mapping or any other transform settings)
-Then take a still frame, switch to original Rec709/G2.4 timeline and lineup the frame and A|B. Color appears the same but Gamma is lifted.
If I change that final CST to input gamma to DCI instead of 2.6, the still frame reference lines up perfectly. So the only place in the chain I can think that the Gamma is shifting is the DCP export from Resolve. There is no step on the deliver tab to modify Gamma, so my assumption was Resolve is doing the DCP standard, which I believe is Gamma 2.6. Is this not true?
Is it a similar situation to Rec.709 and Gamma 2.4 where the real target is not quite 2.4, but people generally set their reference levels to 2.4. So technically its deviating from the SMPTE standard, but its become its own standard in a way. Is this another situation like that? Where DCI is the target, technically slightly different than 2.6, but 2.6 is more widely adopted or something? If that is the case, is DCP exporting from Resolve not going to work since it is outputting true DCI Gamma whereas the theatre I'm submitting too is asking specifically for a Gamma of 2.6 deliverable?
Any help would be greatly appreciated,
Spencer