Going from Davinci Resolve non-color managed with DPX into Nuke, the LUT exported from Davinci works only if OCIOfiletransform is used to add a shaper LUT converting the working space for the LUT from the one used in Resolve (for example Rec.709) to Nuke’s linear working space. This works on the DPX file which is in log space, as LUTS need to be in log. Since this is a non-color managed workflow the DPX is read into Nuke with the input color space set to the same as the view transform.
However, when working with DaVinci color management on, with the working space (i.e. timeline space) set to the default non-log color space of Rec.709, the resulting LUT will clip exposure values in Nuke, even with the shaper converting the working space. This is fixed if the working space in Resolve (timeline) is set to log, which makes sense to me. It’s also how ACES works (the ACEScc working space being log for DI).
My question is: am I correct that if one wants to work color managed in Resolve that the working space has to be log, rather than a limited color space like Rec709 for LUTS to work? Some colorists we work with are resistant to working in log rather than Rec709, so I’m wondering if there is a workaround I am missing.