First is some minor doc changes: https://github.com/imageworks/OpenColorIO/pull/100 Second is a reverse checkbox for the OCIOCDLTransform node, and a "select cccid" button for the OCIOFileTransform (a

https://github.com/imageworks/OpenColorIO/pull/102 OCIOColorSpace node now supports context overrides. Also, a few additional code cleanups. -- Jeremy

https://github.com/imageworks/OpenColorIO/pull/103 Addresses issue #31

The time is ripe to lock off on a stable 0.8 release. (We've actually been avoiding ABI breaks for awhile now, this should be anti-climactic). New features / bug fixes will continue to be welcome in 0

https://github.com/imageworks/OpenColorIO/pull/105 When using the boost_ptr compatibility mode, previously clients would need to know which option was used and to compile with the same #define setting

https://github.com/imageworks/OpenColorIO/pull/106 This adds two examples demonstration an integration between OpenColorIO and Mari (Foundry's texture painting app). This is very much a work in progre

Hey guys, I'm trying to use ociobakelut to bake out a .csp lut. I'm using the latest opencolorio (0.8.0), but getting weird results. It clamps the tops, details in the bright areas are completely gone

Hmmm, Oliver - could you email be your jp_lin2log.lut (directly)? I'd like to re-create this on my end. Dont worry about the Kodak cube lut, I can use one of my own there instead. One thing I notice,

https://github.com/imageworks/OpenColorIO/pull/111 FileFormat registry refactor The registration mechanism is now less fragile, using the 'construct on first use' approach rather than relying on stati

Version 0.8.1 (May 9 2011): * New roles: TEXTURE_PAINT + MATTE_PAINT * Mari API Example (src/mari) * FileFormat registry updated to allow Windows + Debug support * boost_ptr build compatibility option

https://github.com/imageworks/OpenColorIO/pull/112 This exposes a single 4-byte hex number, e.g. 0x01050200 == 1.5.2 Use this for numeric comparisons, e.g. #if OCIO_VERSION_HEX >= ... Note: in the cas

https://github.com/imageworks/OpenColorIO/pull/114 * PyColorSapce supports kwarg initialization * Exposed ClearAllCaches to python -- Jeremy

https://github.com/imageworks/OpenColorIO/pull/117 Added a bunch of windows build fixes. Thanks to the Foundry for providing this hitlist. Biggest change of note is the updated from yaml-r423 to yaml-

FYI, The Foundry has successfully gotten OCIO working on Windows, but it required bumping up to the latest stable yaml-cpp version. So just a heads up, that library version will be changing soon. (alo

Folks, I've been trying to get OCIO compiled for the iPad (think siggraph tech demo), and I've been having a very hard time getting the XCode cmake exporter to generate a working project. I've followe

https://github.com/imageworks/OpenColorIO/pull/116 This addresses oliver's bug where an HDR lin -> Dreamcolor ociobakelut command was clipping the highlights. After this fix, you can get a proper outp

https://github.com/imageworks/OpenColorIO/pull/119 First pass at a iPhone cross compile toolchain. eg cmake -DCMAKE_TOOLCHAIN_FILE=../share/cmake/iPhone-toolchain.cmake .. It compiles but I don't have

Forwarding reply to ocio-dev, not sure if there's another way to send out the zip* https://github.com/imageworks/OpenColorIO/pull/119 -- Jeremy * The zip is only 19K so spamming ocio-dev seems fine in

https://github.com/imageworks/OpenColorIO/pull/122 The lut1d/3d ops would crash if applied to images with nan values. Now, nan values are preserved. Further work needs to be done to unify handling of

Pull Request: https://github.com/imageworks/OpenColorIO/pull/123 Issue: https://github.com/imageworks/OpenColorIO/issues/121 Fixes Error handling in python glue for pyprocessor: processor.applyRGBA(1)