I am hoping that some bedrock aliases will remain in the event that a configuration is added and reconciliation cannot be made in a DCC. Without aliases, the whole system would have to revert to hard

> 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

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,

On Mon, May 11, 2020 at 03:02 PM, Doug Walker wrote: But note that (as with a number of other OCIO features) it is also possible for users to override the optimization setting via an environment

On Mon, May 11, 2020 at 03:36 PM, Doug Walker wrote: A v2 config must specify a default color space, but this could either be done using the default role or a default file rule. So if the config does

ociocheck and sanity check should abide by the following pre-established roles I believe: ``` ociocheck --iconfig config.ocio OpenColorIO Library Version: 1.1.1 OpenColorIO Library VersionHex:

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

>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

The ociocheck tool and the sanity check API should flag missing default roles. With respect, TJS

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

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 include

OpenColorIO Dev Discussion Upcoming Events OpenColorIO TSC meeting (weekly) When: Monday, 11 May 2020, 9:30am to 10:00am (GMT-07:00) America/Los

This issue has been created to further discuss a starting point for the future of OpenColorIO-Configs and the ACES config. https://github.com/imageworks/OpenColorIO-Configs/issues/19 We're getting

OpenColorIO Dev Discussion Upcoming Events OpenColorIO TSC meeting (weekly) When: Monday, 4 May 2020, 9:30am to 10:00am (GMT-07:00) America/Los

Sent. Let me know if there are any issues.

To sagland@... please. Sent from my phone.

Oh, if the entire ASWF uses Zoom as a standard, then I guess using it makes sense. Although it might have seemed so, my main reason for the suggestion was to use and promote open source tech. instead

We're really drafting off the fact that all the ASWF groups (and I assume the rest of the Linux Foundation) use Zoom as their standard for meetings. So really, if this is an important topic, it is one

Hi all, This is my first message on the list here, so if I get something wrong, I apologize for that. The title explains it all though. Zoom has come under a lot of scrutiny lately. Letting unwanted

OpenColorIO Dev Discussion Upcoming Events OpenColorIO TSC meeting (weekly) When: Monday, 27 April 2020, 9:30am to 10:00am (GMT-07:00) America/Los