Hi there! I just posted this question on the ACES website: http://acescentral.com/t/why-utility-raw-as-reference-for-aces1-0-3-and-not-aces2065-1/1378 It seems like it's not just me that is unsure, ho

Hello, I would like to implement OpenColor IO in Maya and 3ds Max at startup. Can you explain me how can I do that from Python please ? The goal is that Open Color IO will be implemented at startup of

Hi there! Thanks for your answer. The reason for a reference colourspace and the 'star topology' of the colorspaces is perspicous for me. I was just wandering, why the ACES 1.0.3 config has at least 2

Hi Abraham, The reference colorspace is the one that every colorspace defined in the config converts from (or to). It may or may not be defined in the config. If it does, the to_reference and from_ref

Convert the xy coordinates to XYZ, with red being the first column, then green, then blue. That forms a 3x3 matrix for taking linearized RGB to the XYZ domain. From there you would need to perform a c

Hi, This is likely a very old request. I am charged with setting up a global config for a new startup. I am basing the .ocio on aces1.0.3 I'm confused on how to customise profiles, looks etc ... I do

Hi All, I'm a new to both Nuke and OCIO. For some reason, I need to develop a nuke OP similar to OCIOFileTransform. But when I add just one simple line such as "OCIO::GetCurrentConfig()", I got a cras

Hi, For some reason, I need to write a pixelOp similar to OCIOFileTransform with OCIO API. But when I add just one simple line such as "OCIO::GetCurrentConfig()", I got a crash with the terrible "Pure

Hi all, I would like to know if OCIO java public interface is used? and should be maintained ? OCIO currently supports three public interfaces: 1) The native C++, 2) The Python interface (built on top

Hello all, With the help of our lovely contributors, we have just set up the 1.1.0 release branch. This is currently regarded as a Release Candidate since the official 1.1.0 tag has not been assigned

Hello all, With a little bit of movement on the OCIO repo working towards addressing the most egregious image-quality-effecting bugs, we need to look to locking off to a 1.0.10 to help our users, and

I would really like to see OCIO support .cdl files in addition to .cc and .ccc as an direct input for the FileTransform and CDLTransform. Of course there are ways and tools like cdl_convert to convert

FileTransform will attempt to load the specified lut formats, if the initial read fails. I also had to make some of the 3D lut loaders use stricter parsing as they now get called (in error conditions)

The latter mostly, most VFX studios that maintain the project don't actively use After Effects so it's not usually on our minds. So its also a question of, if its broken who cares enough to do somethi

Currently, I am using OCIO with a mixed CPU/GPU pipeline. Luts are 4 float colors which get fed like: // // Compute lutMin, lutMax, and scale and offset // values, lutM and lutT, so that // // lutM *

I have a GL Lut that is not created with OCIO. Instead an initial identity lut is created and this lut is passed on to the gfx card by my own code. So long, so good. However, this lut is not a perf

https://sourceforge.net/projects/mrviewer/files/v3.8.4 This version of mrViewer is the first to add some support for OCIO. Please add this software to the compatible list. Thank you.

Hi there, I'm taking a passing glance at colour management in After Effects and I found the OCIO plugin maintained as part of the OCIO Github project. https://github.com/imageworks/OpenColorIO/tree/ma

For those of you attending SIGGRAPH 2017 (conference pass required) in Los Angeles, we will be hosting a "Birds of a Feather" event for users and developers of OpenColorIO to get together and discuss

Hi, I know it is an old question but I could not find a working solution. Is there a walkthrough to build OCIO including PyOpenColorIO on Windows? Or something precompiled that might work? My current