Thanks for all the feedback, everyone! It has been very helpful. Having tabulated the results, the winner - by a landslide - is documentation! So this will be the (rough) order of development: 1)

Hi Jeremy, shared_ptr is header only and you're already using CMake, so perhaps it'd be worth looking at using CMake's unit testing instead of boost's? This way there's no linking dependencies

Actually, I dont believe there currently is a link dependency to boost. ldd src/core/libOpenColorIO.so : linux-vdso.so.1 => (0x00007fff63afb000) libstdc++.so.6 =>

Hi Jeremy, Ahhh, my bad. In quick reading up on it I'd assumed that they were referring to linking with boost's libraries, rather than the test modules created within the user's code. I did a little

Ok, so I just checked in a bunch of changes to the unit testing (spi github repository). These changes may or may not affect the build error you've gotten. I'll check your error on OSX when I get

Version 0.6.0 (Sept 21 2010): * Start of 0.6, "stable" branch All 0.6.x builds will be ABI compatible (forward only). New features (even experimental ones) will be added to the

I think thats fine, the DEBUG/TEST build would build both and the RELEASE wouldn't. .malcolm

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

Est, A 32x32x32 cube lut is a totally reasonable size, it's what we happen to use internally at Imageworks. Some other popular sizes include 17x17x17 (flame), and 33x33x33 (a few commercial color

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

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,

Oops. This is actually a callback on commits themselves, not pull requests. I'll disable the callback until I get it worked out.

Hi Jeremy, Thank you for your replies. Everything is clear now. I think that the lut size is an implementation detail of the client and a recommended lut size function wouldn't have much use as most

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

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

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

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

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

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

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