https://github.com/imageworks/OpenColorIO/pull/247

https://github.com/imageworks/OpenColorIO/pull/248

I just noticed that you can edit any files (in your own forks) directly though github. (I presume this has been there for awhile, but this it's the first time I have used it). While editing *code* ove

This breaks ABI compatibility. Let me know if anyone has any concerns? https://github.com/imageworks/OpenColorIO/pull/250 Example diff: https://github.com/jeremyselan/OpenColorIO/commit/f83809c28cfae5

https://github.com/imageworks/OpenColorIO/pull/251 On a slightly related note, there's a bug in cmake <2.8.7 which causes "make test" (or "ctest") to take about 30 seconds (instead of the ~30 millisec

Cinema sandbox apparently includes OpenColorIO support. http://mycryengine.com/index.php?conid=59 I wonder if they've just pulled out our lut reading code, or have full blown $OCIO profile support...

For those who are looking to have an 'easy' system install of OCIO on the mac, you can now do it using homebrew. http://mxcl.github.com/homebrew/ http://braumeister.org/formula/opencolorio Thanks to 2

Adding support for IRIDAS .look LUT's should be easy, but a few test files are needed. https://github.com/imageworks/OpenColorIO/issues/249 If you have access to a bit of IRIDAS software which can wri

Hey guys, it's been quiet for a while so I thought I'd check in. I'm still interested in packaging OCIO for Fedora and with Jeremy's patch to use the new yaml-cpp 0.3.0 building works fine. I'm guessi

Sorry, it's not quite ready yet. There was one issue in yaml-cpp 0.3.0 I had to track down. Let's aim for the end of next week? -- Jeremy

https://github.com/imageworks/OpenColorIO/pull/254 (Sam: Thanks! The test files were perfect)

https://github.com/imageworks/OpenColorIO/pull/255

Hi there, I am a bit of a newbie here, so please be gentle :-) I built openColorIO yesterday on the windows platform, and while the process had parts that i had to do manually (for yaml and tinyxml),

https://github.com/imageworks/OpenColorIO/pull/258 https://github.com/imageworks/OpenColorIO/issues/19

https://github.com/imageworks/OpenColorIO/pull/260

I'm currently integrating OpenColorIO into an application that uses CUDA for GPU processing. In order to use OCIO's shader path, we'd need to copy our images over to OpenGL textures and back again. If

Hi, I have a library that wraps color processing engines including OCIO. This library has a call to inverse. Whilst I am able to generate the inverse of a 3d lut (with all the usual caveats and edge c

This release is a duesy. OCIO 1.0.7 is ABI and source compatible with all 1.X versions (of course), but has a lot of features / fixes: Version 1.0.7 (April 17 2012): * IRIDAS .look support * ociolutim

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 s

https://github.com/imageworks/OpenColorIO/pull/267