Thanks for the information Dennis. If we do end up trying to tackle the OpenGL code path ourselves, I would definitely be interested in the idea of using your changes as a starting point, and an

This issue not just tetrahedral interpolation, it is the fact that the existing OCIO OpenGL GPU path folds all LUTs into a single 3D LUT, and this is not sufficient for many transformations

Without tetrahedral interpolation you can get better results by creating 65x cubes instead of the default of 32x that the example OCIO configs use (very easy to create with Hp's python script included

I have no insight into the activity of the project - but from the outside the project does appears rather dead (no commits to the repo since Sep 2014, tickets piling up with little response, even

Hello all, This is mostly directed at those currently leading the OpenColorIO project, but I would be happy for any input or information anyone else can provide. Most of you are likely aware of the

I didn't check for ok in the code snippet I provided, but ok is True, and colorBuf.geterror() returns an empty string.

There is, you just weren't checking it: import OpenImageIO srcBuf = ImageBuf(src_path) colorBuf = ImageBuf() ok = OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear') if not ok :

I don't know where the ocio config could be coming from since I don't have an OCIO environment variable set, and I couldn't find any config files. When I run oiiotool --help it shows at the bottom:

In OIIO 1.6, if OCIO is disabled (support not compiled at build time, or no OCIO configuration file is found at runtime), all it knows how to do is convert between sRGB or Rec709 and linear. BUT... if

I'm using OpenImageIO-1.6.14-cp27-cp27m-win_amd64.whl which I downloaded from here: http://www.lfd.uci.edu/~gohlke/pythonlibs/ . I found it too much of a pain to build the source for Windows. This

Phrases like "looks lighter in Nuke" always make me suspicious, there are too many ways things can go wrong. Let's start from first principles. oiiotool -pattern fill:color=.5,.5,.5 256x256 3 -o

Also, which version of OIIO? -- Larry Gritz l...@...

It depends on the colorspaces defined in your config.ocio file set by your $OCIO environment variable. Which profile are you using from the examples or did you roll your own?

Hi, I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks

Wednesday July *27* Sorry for the mixup. -- Larry Gritz l...@...

6th annual Open Source VFX Beer of a Feather For those of you attending SIGGRAPH 2016 in Anaheim, we will be once again holding an event for developers and users of VFX-specific open source projects.

Hi, I am building on osx 10.11 and receive the following error at compile time building 1.0.9 from here https://github.com/imageworks/OpenColorIO/archive/v1.0.9.tar.gz In file included

Hi, We are in the process of publishing the draft VFX Reference Platform for CY2017 so please can you give an update on when you expect this next release to drop and, if it's in time for vendors to

Actually, what we found was creating an actual OCIO config out of the LUT file transform produced the proper results. Not entirely sure what the actual difference is under the cover.

Hello Gene, The ACES 1.0.1 OCIO config can be found here: https://github.com/hpd/OpenColorIO-Configs/tree/master/aces_1.0.1 General information about ACES can be found