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

Any status updates on this? Would love this as well. Will need the View Transforms to be able to be applied as additional transforms as well.

R19 beta is here with this feature ??

SCR-20240414-ivdr.png (33.12 KiB) Viewed 1621 times

Indeed, already spotted this in the features pdf. Looks promising. Especially additional ICC profile support for both Win and Mac. This must be to make HDR function as well on Windows which they also finally added but won't be made available yet until v19 release version according to the new features pdf.

But great to see added OCIODisplay for the viewer and the viewer clipping issue being resolved.
I'm not spotting an ACES Transform though so I wonder how that works when using ACES project wide. Can't test v19 just yet myself. (screengrab from their demo video)

Untitled.png (58.12 KiB) Viewed 1598 times

Can't test v19 just yet myself.

I'll have to wait the end of the month and finishing a project before try this ...

Hmm... had my hopes up when reading "2.3 Support", but sadly still no "Looks" supported:

Looks.png (4.25 KiB) Viewed 1588 times

Hmm... had my hopes up when reading "2.3 Support", but sadly still no "Looks" supported:

Looks.png

Yikes... come on BMD...

Hmm... had my hopes up when reading "2.3 Support", but sadly still no "Looks" supported:

The attachment Looks.png is no longer available

There is! But only in the viewers.

2024-04-15_10-42-36.jpg (70.1 KiB) Viewed 1466 times

Would love if it existed as a separate node also.

Hmm... had my hopes up when reading "2.3 Support", but sadly still no "Looks" supported:

The attachment Looks.png is no longer available

There is! But only in the viewers.

These are Displays and Views. Looks aren't there:

Views.png (20.94 KiB) Viewed 1461 times

The same config in e.g. Blender looks like this:

Looks_Blender.png (8.33 KiB) Viewed 1461 times

I ah I see what you mean. Yeah that is sadly missing. At least we can view Views now. Half the battle won Let's hope BMD sees this and adds the looks

Agreed! The biggest new "feature" for me (which was included in one of the last few 18.x updates IIRC) is that GPU accelerated OCIO ViewLUTs no longer clamp colors or cause severe banding. I always had to use OCIOColorspace nodes in the flow to view the correct result, which was more like a punishment than a "workflow"

+1 to all of this.
The developers don't look here. Go to the DaVinci Forum and into the DaVinci 19 Beta group. Post it as an issue there that OCIO 2 is only present as a display lut and not as a tool. Request the OCIO tool to be updated.

+1
It would be fundamental for my work, the old version is very slow, being q 2, it is much better

[Peter Chamberlain]

+1 to all of this.
The developers don't look here.

Simply false.

+1
It would be fundamental for my work, the old version is very slow, being q 2, it is much better

The devs haven't bin super active before so I have gotten that feeling too but I'm super happy to see way more interaction lately!

These are Displays and Views. Looks aren't there:

Hey Steffen, I know BMD should adress this asap but you can work around it for the time being. You can customize the config to incorporate the look into the Views with a simple edit. You can do this for the config directly from blender, or if you prefer, create a seperate config folder for Fusion specifically. (Just don't forget to copy both lut folders and the config file in that case.)

Here's what you'd add under Displays in the sRGB list:

Code: Select all

    - !<View> {name: AgX-MedHiContrast, colorspace: AgX Base sRGB, look: AgX - Medium High Contrast}


And add this entry in the Active Views list:

Code: Select all

AgX-MedHiContrast

The way it works is that the name part is just any given name, the look is the name of the actual look which are defined at the bottom of the config.

You can repeat that for any look you'd want but you have to do it per Display if you want P3 included as well for example, which sort of defeats the purporse of a Look tranfsorm in this context but again, for a workaround it's manageable.

For convenience I attached my example config below.

These are Displays and Views. Looks aren't there:

...

For convenience I attached my example config below.

Awesome! Thanks a lot.
I remember doing a similar hack when Filmic came out.