After checking out your pull request, I realized that Larry added support in master to the algos for passing a ColorConfig: https://github.com/OpenImageIO/oiio/commit/40bf793107c3bef3a646f3ccb402d99203c22585
Unfortunately, for me it only solves part of the problem. The OCIO configs can contain variables that get resolved via a context. For instance, $SHOW / $SCENE / $SHOT. When the config gets loaded, it will end up using your current environment. So what I end up having to do is what I had previously mentioned, where I have a global lock, and I modify the current env, then load the ColorConfig, and then restore the env. I think the C++ side of things would need to expose that OpenColorIO Context concept on the ColorConfig, so that you could set the context variables directly, instead of having it default to your current environment. On Mon, Jul 20, 2015 at 1:22 PM Jep Hill <[email protected]> wrote: > Thanks for confirming, Justin. > > I’ve submitted a pull request (#1187) that exposes the ability to specify > different ColorConfigs via the python bindings. > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
