Standard OCIO Directories


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

I'd like to propose that we define standard directories on each
platform where OCIO configurations might live. Nuke has taken a step
in this direction now that they are shipping with OCIO. They have some
users who launch it with a regular double-click after all, so they let
you store configurations in plug-in path directories and they'll show
up in a user-friendly pop-up menu under the viewer preferences. If we
define a standard directory, then all applications could operate this
way, pointing to the same set of configs.

In the After Effects plug-in, I'm currently storing the .ocio path,
but this ends up being fragile if you move the project or open it on
another platform. If I could just store the name of the configuration
and look for it in a standard location, that would make projects much
more portable. ICC profiles currently work this way.

I don't think this has to get any programming support in the OCIO
library. It would be left up to application developers to scan the
directory, build the menu, and pass a path to
OCIO::Config::CreateFromFile().

My path suggestions:
Mac: /Library/Application Support/OpenColorIO
Windows: C:\Program Files\Common Files\OpenColorIO
Linux: /usr/share/OpenColorIO


Brendan

Join ocio-dev@lists.aswf.io to automatically receive all group messages.