Thank you for your answer.
My goal is to generate image files with the RRT that we can use directly in our projection room. Unfortunately, I don’t have precise details about the projection setup or the exact specifications of the system.
What I do know is that our artists currently work on sRGB monitors using the Output – sRGB transform from the OCIO config. To check the result in our projection room, we convert the images using the Output – DCDM transform (from the ACES 1.1 / 1.2 OCIO configs). The resulting images are encoded as J2C files, which can then be used directly by asdcp/OpenDCP to generate the XML and DCP package that our projection system reads.
I wasn’t involved when this workflow was originally set up, but visually the result in the projection room matches quite well what the artists see on their screens, and this process has been used for years. So we assume the workflow is reasonably correct, even if it may not be technically perfect.
The issue is that in the ACES 2.0 OCIO config there is no longer a “pure” DCDM output. I also checked in Resolve 20 and it seems to be the same. The available outputs now are ACES 2.0 – SDR 100 nits (P3 D65) and ACES 2.0 – SDR 100 nits (P3 D60 in XYZ E).
Would it be possible to use one of these outputs to keep a similar workflow? Or should we reconsider the whole process of generating the J2C files for our projection room?
Our current workflow is very simple and convenient: we render in ACES from Nuke and convert the images directly to J2C files for projection checks in our screening room using the DCDM output transform, without any additional conversion steps in between.