shebbe wrote:This is where your implied issue lies I guess. In an ACES workflow there is no such thing as Input DRT. Everything is internally technically converted to a single colorspace and only the output has a designed display rendering transform so no matter what colorspace you would work in the output would always be the same.
You are implying that in RCM2, everything is not converted to single timeline colorspace? If it isn’t it makes any reasoning about the RCM2 hopeless because everything becomes relative.
ACES can do Input DRT allright, if you choose one of the ODTs as IDT. This applies inverse ODT and inverse RRT. In Nuke I use this all the time to reverse stuff that has gone through ODT, usually to check that what I wrote out is correct.
I’m not sure what benefits Input DRT is supposed to serve in RCM2, how do you all understand the motivation behind it? To me it looks more like doubled forward tonemapping...