Hi everyone, Recently I've tried using the ociotoicc utility with a lut on the command line. When I try to load the icc file into photoshop, I receive: "Could not load the RGB working space because th

https://github.com/imageworks/OpenColorIO/pull/187 This is mostly about the JNI Java interface, you need to run cmake with (-D OCIO_BUILD_JNIGLUE=TRUE) for the binding to be built. Their is no install

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

Hi All, Wish I could have figured this out myself (I had no issues building pre-1.0 source on my MacBook Air Snow Leopard laptop, but I'm having issues building the latest 1.0 source now. I'm not doin

Marie, Thanks for catching this! The currently shipping IIF configuration is based on an older specification (I forget the exact version, but it's around 8 months old), so my hope is the versions will

https://github.com/imageworks/OpenColorIO/pull/178 Added options for specifying simple color corrections (such as saturation, offsets, etc) in addition to normal lut commands. Also allow for specifica

https://github.com/imageworks/OpenColorIO/pull/177 Previously, flame and lustre 3dl export was hard-coded to size 17 shaper luts, even when the cubelut was a different size (33x33x33 for lustre, for e

Version 1.0.1 (Oct 31 2011): * Luts with incorrect extensions are properly loaded * ocio2icc / ociobakelut get --lut option (no longer requires ocio config) * DisplayTransform looks do not apply to 'd

https://github.com/imageworks/OpenColorIO/pull/174 DisplayTransform looks are no longer automatically applied to 'data' ('data' being normals, pts, etc). By design, colorspaces tagged as data do not h

Adds --lut option, which lets you create a baked output lut, even in the absence of an input configuration. Example: ociobakelut --lut filmlut.3dl --lut calibration.3dl --format flame lg_to_srgb.3dl h

https://github.com/imageworks/OpenColorIO/pull/172 Luts with incorrect file extensions are now correctly loaded. This was always the intent, but there was a bug in the implementation, where were doing

The IIF color configuration has been updated to match the ut11 Reference Rendering Transform (RRT). - Alex can probably better speak to the differences, but the major visual difference in this RRT (co

Does anyone have any experience with Maya Viewport 2.0 color management? We'd like to get the Maya / OCIO integration ball rolling, and wondered who here has experience in that area. -- Jeremy

Hello! Unfortunately, Joseph Slomka has decided to move on from Imageworks so we're looking for a new color scientist (details below). Please email me off-list if you have any referrals or specific qu

I'd like to encourage folks to utilize the ocio-dev as a resource for job postings. The ocio-dev list is rather focused, so it seems nice to be able to take advantage of it when a company is looking t

Sorry, cmake is brand new to me and I figured it would be quicker to ask... What would be the proper way to tell cmake to build the nuke plugins linking to the versions of libraries (libstdc++ etc) in

Could anybody say a little about what ColorSpace::setAllocation() and ColorSpace::setAllocationVars() do? I'm starting to get up and running writing my own luts into the spi1d format for converting fr

Hello all ! I'm having a look at IIF config.ocio and I was wondering how you build the aceslg2_to_Rec709.cube LUT for the rrt_odt_r709 colorspace. I'm asking because when I compare an OCIOColorspace n

Friends, We've just officially released version 1.0, now available for download here: http://github.com/imageworks/OpenColorIO/zipball/v1.0.0 http://github.com/imageworks/OpenColorIO/tarball/v1.0.0 I

https://github.com/imageworks/OpenColorIO/pull/165 Oh no! Today, in the normal course of production work (debugging why our editorial deliverables didn't match on-set reference), we discovered that OC