


And if resolve’s DWG settings are adding some kind of transform, what is the process for using a different one? Does DWG mean that LUTs applied to a node no longer work anymore? I understand that if you are working with raw footage resolve will apply the proper conversion LUT based on Meta tags. The Sony sLog3.cine clip then appears not completely flat as if it was unmodified, nor is the contrast and saturation in the ballpark as it would be if a LUT has been applied using the old Da Vinci YRGB settings as they were in resolve 16. Under DWG in the settings page the log clip is undergoing some kind of conversion. I’m just seeing that under da Vinci Wide Gamut the behavior looks like a second LUT is being applied somewhere which, if that is what is happening, I can’t track down. To clarify, I am not applying two different LUTs as far as I know. However I am interested in making use of the Sony created LUT FX9 footage to bring it as close to the Sony Venice color science as possible as that is what the LUT was created for. I can hand correct and bring into proper range the non-LUT footage. If I choose the Sony LUT for Sony sLog3.cine to rec709 for Venice (or any other LUT for that matter) the image then becomes unusably oversaturated. However it has no LUT applied (that I can find.) DEFINITELY not as flat as SONY log footage and definitely in proper range. If I choose YRGB COLOR MANAGED and DaVinci WIDE GAMUT in the color management preset box, The clip is converted to an image close to the original scene minus a bit of contrast and saturation.

In project settings, if I set up the color management as DaVinci YRGB the clip looks like regular log footage. I am working with Sony sLog3.cine footage which should require a user chosen normalization LUT. I’m suspecting that somehow the normalization LUT (chosen from the LUT list either at the node level or in the media pool) is somehow being applied a second time which results in unusable super saturation and increased density of the image. I realize this must not be a widespread problem, although I’ve seen others on different forums present the same issue :
