where is OCIO v2.x support?

What is happening with OCIO v2.x support?
We now have CST and ACESTransform nodes in standalone which is good of course but OCIO itself is pretty much dead? It reads 2.x configs for quite a while already, but...

- Missing OCIODisplay in nodes or in the viewer.
- Missing OCIOLookTransform
- The 'look' in the OCIOColorSpace doesn't work
- Missing OCIONamedTransform

This makes it simply impossible to use v2 configs because we can't even get a proper view transform out.
You can make an argument that we can just use the ACESTransform natively but ACES isn't the only color pipeline that can run through OCIO and even within ACES one might want to deploy custom configs rather than the default full list.

I absolutely agree. OCIO 2.x is becoming more and more important as most of the current configs / applications now use this version.

On the bright side I was feeling like x-mas coming early this year as I read in the latest Fusion Studio change log:

Addressed issues with clipping and transforms in OCIO viewer LUTs.

Finally I can use Viewer LUTs without getting weird clipping artefacts or color shifts.
Thanks a lot, Blackmagic!

What is happening with OCIO v2.x support?
We now have CST and ACESTransform nodes in standalone which is good of course but OCIO itself is pretty much dead? It reads 2.x configs for quite a while already, but...

First step it would be awesome for us to be able to use ACESTransform / CST as a Viewing LUT.

First step it would be awesome for us to be able to use ACESTransform / CST as a Viewing LUT.

Agreed! But doing both should be expected at this point. Otherwise they should just remove OCIO 2.x support and say we don't care. It's really silly at this point that these color management issues are still a thing ever since Fusion got integrated with Resolve. The solutions and implementation requirements are crystal clear, yet years later we still don't have anything proper to work with.

Throwing my +1 on this request. I'm trying very hard to drag Houdini forward, but now I can't fully test against my favorite compositor because the Look transform doesn't work. I used to trust Fusion as my ground truth for color space handling. Would be very good if I could do so again

+1

As much as I like the idea of USD and Hydra delegates, this is a bigger deal. Resolve/Fusion needs to allow for interdepartmental cooperation and color reproduction is a primary consideration between software and departments. Especially going into Comp. Round tripping should be painless. The sooner they get these kinds of things worked out the sooner we can recommend their products for end to end post production work.

It took Nuke several versions to get OCIO 2.x right, but Fusion is again left in the dust. Like in the old days.

Currently what Fusion needs RIGHT NOW:

-multi-channel EXR support - some kind of shuffle node, to pull channels from one Loader.

-Zdefocus/Bokeh native node

-OCIO 2.x all around support, to properly support ACES 1.3 and other color management configurations.

+1

big +1 on this one! Currently it's imposible to use OCIO's 2.x configs in Fusion the way they are meant to be used. Sure fusion can load them but you still have to build them as if they were 1.x configs.
Please please please fix

+1