Open-colorIO

Hello, first post here, are there any plans to incorporate Open-colorIO in Resolve 9 when it comes out of Beta at all? Thanks

"OCIO is compatible with the Academy Color Encoding Specification (ACES)"

If it's ACES compliant then it should already be in there?

No, OCIO is an open source framework for configuring and applying colour transformations, its used in the reference implementation of ACES, but is by no means necessary..

The LUT compatibility stuff in OCIO would be neat to have, but a little but redundant as Resolve is already pretty good in that department.
Being able to configure Resolve using an OCIO config file might be handy, but that's really designed for rolling out complex colour pipeline decisions to lots of people who might not individually understand what's going on (ie: not colourists).

What could be cool on the other hand would be allowing Resolve to generate a complex sequence/shots specific OCIO configs. Allowing resolve to take a sequence from a film, generate per shot 3D luts and associate them with specific shots (via the config) so that other people using Nuke or Rv can see their shots through the current grade in dailies and on their desktops.
(you would need a lot of very granular control over exactly how this OCIO config was written to avoid creating a big mess though)

More than OCIO I'd like to see CTL (Color Transformation Language) implemented in Resolve. Whilst OCIO is used to load and apply luts in the ACES reference implementation, CTL is what's used to actually define what they do.
Allowing Resolve to accept CTL directly would allow you to "write" your colour transformations programatically rather than just adjusting knobs..

[edited for terrible spelling]

Hi,

It's really important to have good pipeline between grading and VFX House... It's will more than awesome.

Hope Blackmagic is listening

Fred

Hey BMD,

I was wondering what your thoughts about supporting OpenColorIO for lut handling is?

Would be great to merge this with this existing thread:
viewtopic.php?f=3&t=242

[Joshua Helling]

Would be great to merge this with this existing thread:
viewtopic.php?f=3&t=242

Done! Thanks.

Any chance that this is getting implemented? You see, any EXR files imported from Blender3D (files rendered using the new "Filmic Blender" colorspace setting which expands Blender's dynamic range from 5 f-stops to 25), do not work properly on Davinci Resolve or your compositor. Filmic Blender uses OpenColorIO as its LUT engine: http://opencolorio.org/ and word is that it's going to become the default on the new Blender version that comes out in May. If that's true, then that means that all renders imported on your products won't have the expanded DR, and they will just look wrong.

Any chance that this is getting implemented? You see, any EXR files imported from Blender3D (files rendered using the new "Filmic Blender" colorspace setting which expands Blender's dynamic range from 5 f-stops to 25), do not work properly on Davinci Resolve or your compositor. Filmic Blender uses OpenColorIO as its LUT engine: http://opencolorio.org/ and word is that it's going to become the default on the new Blender version that comes out in May. If that's true, then that means that all renders imported on your products won't have the expanded DR, and they will just look wrong.

While OpenColorIO is nice in one way it sucks in others. For example nearly anything has to be delivered as a Look Up table. Haven't seen math besides some lg2/lg10 predefined function in OpenColorIO. But you could easily add your own transforms to Resolve as DCTLs to handle anything - if you are unhappy with RCM/ACES which can do a lot. An open color management with a lot more settings and a way to add individual color spaces and gamma curve formulas of course would be nice too

While some of the color management in Resolve is a bit cumbersome, you can already use EXR files but you have to know how to handle the extended dynamic range. Problem with Blender is that as far as I understand it despite the color management saving to EXR means it's always saving Linear sRGB. So no direct way to ACES for example as no individual IDTs are supported. But there are a few solutions around it. (For example http://acescentral.com/t/adding-idts-to-resolve/161. Haven't tried it but according to this you can put a DCTL with sRGB -> ACES-AP0 into your LUT folder, select it as an Input LUT and select No IDT for ACES and you can use the file in an ACES workflow)

I use some custom tools where I can easily pass Linear sRGB through the ACES chain in Resolve and it looks good. You just have to use the tools to handle the scene linear data corretly.

Feel free to ask me more if you don't find a way. Could post some more on the weekend maybe, for now it's too late and I have to sign out for today.

While it would be great to see open color IO or something like it implemented into resolve it seems unlikely.
They whole point of OCIO was to create a a platform independent color transformation. If you use Nuke, Maya,Flame or ... the exact same math,configuration and luts can be applied.

So in an ideal world, you can work between Maya, Fusion and resolve with a single configuration file and be confident that color is not changing.

The reality is that on one show there will be DCTL,CTL, GL fragments,Cg code, ICC, and a combination of under the hood color management and luts. Every platform and engine will be custom requiring diligence for each software update and look update. Each managed externally and without overriding organizational and QC tools. Every time an image passes hands is a new opportunity for a one off bug to appear.