Hi Brendan, Thanks, glad you like it! Your understanding of Fast vs. Exact is correct. Regarding the ability to control this from the public API, we have a PR in progress that will allow you to do tha

Sean, thank you for the detailed and well thought out proposal. I fully support it but agree the versioning plan needs some more discussion. Given that OCIO v2 has some features that are specifically

This is perhaps more of a question for ACESCentral, but here is some info that may help you: 1) MacOS uses ICC color management for the display. OCIO is not integrated with that. So to some extent, th

Thanks for pulling that list together JF! Your list was correct relative to the Autodesk products. (Flame and 3dsMax do not currently support OCIO.) From: <ocio-dev@...> on behalf of Jean-Fr

Hi all, We currently have the good fortune of having a number of developers involved in the Google Summer of Code project looking to get involved with OCIO. One of our prerequisites is that they compl

>I guess there have been some changes in this area. So I take it OPTIMIZATION_LUT_INV_FAST has now taken > taken the place of not using FINALIZATION_EXACT. And the exact mode is used if you don't incl

> I've been using "default" (aka ROLE_DEFAULT) as my default color spaces, but then looking at the docs, I guess the > "default" role isn't required to be in a config. Is "scene_linear" required? Any

That's a good suggestion Brendan, we will look into adding that. And as Troy wrote, ociocheck does in fact throw an error if the following roles are not present: OCIO::ROLE_DEFAULT, OCIO::ROLE_SCENE_L

> How is this overridden with an environment variable? Check out OCIO_OPTIMIZATION_FLAGS_ENVVAR in OpenColorTypes.h. > If I do getDefaultCPUProcessor(), it's always the same as getOptimizedCPUProcesso

Was just reading the CHANGELOG.md and noticed that the first named release, 0.5.4, was dated June 1, 2010. I believe the discussion started on the original google-group a few months earlier but nevert

Cheers Jeremy! The name was an inspired choice. Many great projects rebrand at some point. I remember several of us had to get our Image Interchange Framework tattoos removed when the name was changed

Thanks for the report Paul. We will investigate the issue. It's good timing because we are actually preparing a PR involving display/view stuff at the moment anyway. Doug

Hi Paul, We'd like to investigate the issue you found. Could you send us the config or the shader that it produced? (Feel free to use Slack, if it's easier.) thanks, Doug

By "2021" do you actually mean Rec.2100? If so, then yes, the ACES config handles these. The "2020" terminology is quite confusing since Rec.2020 never really took off as a video delivery format. Howe

Hi all, As you hopefully heard at the SIGGRAPH and ASWF BoFs, development of OpenColorIO is currently in a stabilization and testing phase in preparation for the official release of v2 around the end

Hi all, We have just tagged master as the second beta for OCIO v2. The release candidate is not far off, we request people test this thoroughly and help us find any issues. Here are the noteworthy cha

Hi all, Today we have tagged master and created an RB-2.0 branch as the first release candidate for OCIO v2. The final release is about two weeks away and we request people test this thoroughly and he

Dear OCIO community, We are pleased to announce that the beta testing period has concluded and that the official release 2.0.0 of OpenColorIO is now available! For those of you who have been following

Please register and then join us via Zoom tomorrow (August 4th) at 10:15 am Pacific time for the OCIO session at the Academy Software Foundation's Open Source Days event. https://events.linuxfoundatio

Dear OCIO community, We are pleased to announce the release of OpenColorIO 2.1.0! This release features support for the ACES 1.3 Gamut Compression algorithm, an initial set of OpenFX plug-ins, and ins