Re: OCIO Configuration Reference Values
Joseph Slomka <joseph...@...>
toggle quoted messageShow quoted text
The shortest path is going to be an RP of having an CIE1931XYZ named space. There is a certain bit of manual glue required, as OCIO only manages image transforms and standardize the processing.
The next shortest is making it a requirement, and having it fail a sanity check and throw a flag if not implemented.
If it's agreed to then it should make it to the trunk. It sounds like OCIO needs more builds and more feedback to get user input and involvement. I am not a fan of a required role, but if it is a choice between that and dealing with dozens of VFX houses each with their own color management tools I'd much rather have required roles.The slightly longer path is to make a metadata component to OCIO that provides some minimal API to manage color state of images.
Ideally OCIO would be the part of a project that manages color. It sounds like there is a need for a color management framework that track image state,executes logic and interacts with other color management systems.
On Mon, Oct 24, 2016 at 10:13 PM, Troy Sobotka <troy.s...@...> wrote: