Sorry I don't have an answer, but I am trying to do the same thing and having no luck. Were you ever able to get it working? If I can figure it out I will post my findings. Thanks

I'm not really a part of the OCIO dev community, so take my opinion with a grain of salt, but, I agree that any discussion about design or big issues of implementation really should happen on the

I would be interested in joining the Slack channel (although I'd rather discussions happened "in the open" - only so discussion/decisions can be easily referenced in future. However as long as people

I'd really like to see https://github.com/imageworks/OpenColorIO/pull/381 or some equivalent in the next official release. I personally don't like closed-door development of

Hey guys, I'd love to join the Slack channel (provided our corporate proxy will let me use slack :/ ) I'm really pleased to see forward momentum, both in terms of discussions and

Hello all, With a little bit of movement on the OCIO repo working towards addressing the most egregious image-quality-effecting bugs, we need to look to locking off to a 1.0.10 to help our users, and

Thanks Sean! I'll have a look at this and do some tests. Seems like it could do the trick :). ------------------------------- Simon Björk Compositor/TD +46

I'll also point to this: https://github.com/imageworks/OpenColorIO/issues/234

Per-shot colorspaces are generally handeled by the OCIOLooks not OCIOColorspace. Additionally, with Looks you are able to use conditionals (atleast on unix, Id have to try it on other systems) So if

Thanks Kevin, seems like it would work. However (if I'm not misunderstanding) this would require all shot luts to be named the same and also be in separate directories? In my case I would prefer to

Create a null lut is about the best you can do, combined with the search path you could do search_path: path/to/${SHOT}:path/to/null then use a name like "mylut.cube" if you squint hard you can make

I'm trying to add a colorspace that is using a $SHOT env. It all works as expected if the shot lut exist. If the shot lut does not exist an error is thrown: The specified file reference

Hi guys, we were forcing Nuke restarts for a long time now just to make OCIO's context work for fresh opened scripts. This is really unconvenient and artist-unfriendly. Thats why I wanted to give

So...the "input" color space would be XYZ and the "output" would be device color space RGB when using ociobakelut? Is that what you're saying?

For input footage, I'd recommend using the OCIO plug-in for After Effects. Depending on your parameters, there are many transformations that the current code can not bake into an ICC profile. Where

Joshua, It's not a problem to make a profile work as you envision it. All you need to is make the XYZ PCS space as the linear color space that each colorpspaces transfers to and from. -Joseph

Sorry for the bad grammar, I'm attempting to type all of this on a phone...

Is it possible to use ocio to crest an icc profile that can fully define a color space with XYZ PCS like a classic srgb or adobe rgb profile? What getting at is that I've defined a device color

I don't have

Assuming that you have OCIO compiled, the command line tool "ociobakelut" should fill that need. ociobakelut --lut <your_lut.3dl> --format icc --description <description> <output_file.icc> There is an