Same here. We can easily do this through the API by re-generating configs on the fly as outlined in this thread. However, 3rd party tools that have standard OCIO integration are not aware of our

It's complicated. Metadata, file naming conventions, and color space dictates/restrictions in the specification of particular file formats may all be mutually contradictory. What do you do? What is

Hi, > May I suggest making parseColorSpaceFromString() optionally a little more strict? I'm certainly happy to add in this functionality if it makes your lives easier. > This is an especially

I've been bitten by this as well. Ended up writing my own parsing function.

+1 on the suggestion of recognizing OCIO color spaces in the filenames only if they are fully delimited. This is an especially egregious failure, considering that JPEG files are by specification LDR

May I suggest making parseColorSpaceFromString() optionally a little more strict? The basic problem is that as we're transitioning to using OCIO, there are still many situations

Hello, I'm trying to build 1.0.9 on OSX 10.9, but the build is failing compiling ociocheck: To do the static build I'm just setting OCIO_BUILD_SHARED to OFF and OCIO_BUILD_STATIC to ON.

Yes, this is basically what I was thinking. It'd probably work for us.

If you're working in a single facility and have some way of prompting configs to be regenerated, the Python API gives you most of the functionality needed for an inheritance model. Something along

I've also been thinking about the general idea of configs "inheriting" from one another. I haven't delved far into the API for manipulating configs yet, so perhaps there is some support there if

Hello, I'm working on a project that has a base set of well-defined transforms and a more extended set of transforms/color spaces that are less well-defined. The 'less well defined' transforms are

Hi guys I was wondering what the strategy is between the project and the Foundry as far as keeping python modules up to date etc. As I have found the there are changes to the ocionuke module

Trying to build master and the build process is failing trying to process tinyxml and yaml, such as this: 2>------ Build started: Project: tinyxml, Configuration: Debug x64 ------ 2> Building Custom

Hi Paul, Could you perhaps copy in the link errors here? Also are you building OCIO with the same C++11 features enabled? Cheers, Mark

I'm trying to use OCIO with an application built with XCode 5.1.1. I can configure and build OCIO fine, but when I try to link it into my application there are link errors. I'm not using boost

Hi, I'm trying to hook up OCIO properly to blender's color picker system and allow choosing an arbitrary color tranform before uploading the color picker colors to our display device. In blender, by

Hi Mark, thanks for your reply. I'm using Python 2.7.8, downloaded from python.org. Thanks for taking a look at it! Best regards, Simon ------------------------------- Simon Björk Compositor/TD +46

Hi Simon, Unfortunately I haven't really had much of a look into the windows building process. Just wanted to clarify a few things though. Which version of python are you using (and was it one

I'm trying to install PyOpenColorIO on my Windows machine, but I'm not having any success. Does anyone have this working? I've tried with both Marie's build and the one that comes with the precompiled

When I looked at trying to use per-shot grades last, I ended up with the limitation that you couldn't dynamically determine the representation which meant you could not have say a 3D LUT for one shot