RikshaDriver wrote:The only discrepancy I would find in Resolve 15/16/17 at the moment is that the ACES implementation in RCM has a D65 white point, not a ~D60 white point as per ACES specs.
But this is something that's been there for a while and most users probably aren't aware of it or even notice for that matter. The other issues are more usability quirks (i.e. Color Checker behavior, lack of RRT in RCM etc.)
With that said, the reason for this thread is that the "ACES DCTL" feature introduced in Resolve 17 seems half baked to be brutally honest. The implementation appears to be heavily focused on ODTs rather than IDTs and the documentation around practical implementation is still very sparse.
I tried developing some IDTs using the specs and after a while just.gave.up. It seems to require hacks to get something usable for IDTs... like Apollo 13 duct-tape level.
for IDT, when we do need them, we leve the IDT in resolve"as is" (ACES space), so resolve does not do anything to the file and do the DCTL as we like form teh whatever color space to that ACES space.
BUT, I have someone else program that for me, i'm a donkey...