Hmmm, that patch doesnt quite work for us locally at Imageworks. (I think it's probably because we use a namespaced version of boost, and the macro isn't quite right in our context). Let me see if I c

Branch: refs/heads/master Home: http://github.com/imageworks/OpenColorIO Commit: 77639305a291d929b257bb1b3211462b8c9428ed http://github.com/imageworks/OpenColorIO/commit/77639305a291d929b257bb1b321146

Testing, 1 2 3... I've updated our github acct. so all pull requests get cc'd to this list. I really like how OpenImageIO reviews commits in their public dev forum before adding them to the repo, this

Hi All, I recently started using OpenColorIO and I have some questions: In my current code, I'm using a 32x32x32 lut, just for the display, not for processing. Is it a good size? How do you choose a 3

Branch: refs/heads/master Home: http://github.com/imageworks/OpenColorIO Commit: 5a24dca1b81c5275051b769adeaef6c634a10e1d http://github.com/imageworks/OpenColorIO/commit/5a24dca1b81c5275051b769adeaef6

Version 0.6.1 (Oct 5 2010): * Exposed ExponentTransform * Added CineonLogToLinTransform - a simple 'straight-line' negative linearization. Not strictly needed (could be done previously with LUTs) but

Hi, I have a few emails to send through I have been discussing with jeremy, I have split them up so they can be discussed in different threads. Here is an initial pass at the Houidini lut loader. I ha

I have been playing with littlecms a little (building profiles for photoshop etc) and was wondering if people have an idea on how they envisioned these fitting into OCIO? There could be reader and wri

Now that we've got a few people actively contributing code, we're going to start formalizing the development process. (Thanks to Malcolm Humphreys for being the guinea-pig in the process). Please refe

I wanted some pkgconfig (http://en.wikipedia.org/wiki/Pkg-config) support to make it easier to build against OCIO. Part of this needed burning the ocio version into the .pc file, so I rejigged things

Looks good to me! I really like the VERSION consolidation and the cmake "configure_file" mojo. Now that I know about that approach, I'll use it for the OCIO_NAMESPACE #define as well... -- Jeremy

Looks good to me! I have a few comments, but these dont need to be addressed yet. * In terms of coding style, you put the return value on a new line, where as I tend to not. I'm actually fine either w

The ExponentTransform (a publicly exposed class for doing power / gamma operations) previously could not serialize itself to xml. This commit adds the feature. Repo: http://github.com/jeremyselan/Open

* added cpack support to replace the tgz_create script. Run 'make package_source' to create 'olio.VERSION.tar.gz' * removed tgz_create script http://github.com/malcolmhumphreys/OpenColorIO/commit/a02d

Are people super into the idea of using xml? We used xml for nearly everything at RSP, over time it became clear that it's a pretty poor choice for a lot of things. One of the developers introduced th

Hi All, Just wanted to throw a quick thought in on C++ LUTs. I've recently been dealing with Arri's Alexa. One of the more unusual aspects of it's Log-C transform is that it changes based on the camer

PyOpenColorIO.so wouldn't compile on linux http://github.com/malcolmhumphreys/OpenColorIO/commit/bb90284fa98161aae4ace74987246ae301ec1822 - Added some const_cast<char*>(..) ie. 'error: invalid convers

- Initial checkin of YAML serialization - Added ext/yaml-cpp-0.2.5.tar.gz with a patch to build it static - Added yaml-cpp to the LICENCE file - CDLTransform should be the only thing depending on tiny

LGTM. This was a compilation warning though, right? (It shouldnt have been an error). -- Jeremy

Folks, I've deleted the OCIO yaml branch. The main trunk now is up to date with all recent commits. -- Jeremy