So in the OP’s situation you get a LUT which transforms from DaVinci ACES to Rec.709. Resolve bakes in a transform from the working space, the RRT, and the current ODT (but not the IDT) when exporting a LUT. I find the best approach is to temporarily modify the node graph when exporting the LUT.

The other thing is that depending on the working space, you may need to make changes to LUTs, or modify append another transform before you apply the LUT. Is there something I am missing when building the LUT? Or something I should be doing differently? My image procesing is 32 bit floating point, my color science is DaVinci ACES, my ACES version is 1.0.2, my input Transform is Alexa, and my output transform is Rec. Can someone help me understand what I am missing? I am using DaVinci Resolve 12.5. My only conclusion is that I missed a step in the ACES architecture somewhere along the way that is being retained in the data of the new LUT I am creating, and then when I apply the LUT it is doubling whatever setting I missed. The color shifts I had made were similar, but the exposure, contrast, and saturation looked like they had all been affected when I didn’t touch any exposure, contrast, or saturation tools when building the look. When I applied the new ACES LUT it looked nothing like the look I had designed. What I did expect though, was that when I designed a new look in the DaVinci ACES color science and generated a LUT that the look I designed would be baked in using the new LUT. 709 or LogC to work in the ACES workflow as they were designed around a different color science (DaVinci YRGB).

I did not expect my old LUTs that I built around Rec.

The one thing I’ve noticed however is that LUT generation is significantly different. And I have downloaded and applied a few LUTs for ACES that I really like. Color matching different cameras has never been easier. I am fairly new to the ACES workflow, but I am really liking it so far.

How to export luts davinci resolve