Re: Standard OCIO Directories

Brendan Bolles <bre...@...>

On Apr 17, 2012, at 9:41 AM, Larry Gritz wrote:

Do these plans include a provision for handling two (or more) different 3rd party apps, each with OCIO embedded, that may want to install mutually-incompatible OCIO default color space definitions? If there is a single preferred location for color configurations, will they clobber each other in troublesome ways?

Nuke already stores OCIO configurations in its own application-specific directories. Since it has multiple plug-in directories, it should already have some logic for what to do if two configurations with the same name appear in different places. If they recognized the shared location, presumably it would get lower priority to the application-specific ones.

I'm trying to address what I see to be the common case for "regular" users: wanting multiple applications to share the same OCIO configurations. I think most people will not have two configurations that are named the same but behave differently. The simple way to handle that in a shared directory would be to name the other configuration "spi-vfx-v2" or whatever.

For those here who want to juggle multiple configurations, versions, etc., then the $OCIO environment variable method you've been using is what you'll probably want to stick with.


Join to automatically receive all group messages.