Actually, I'm still having the same error. The error occurs with the following: set(OCIO_VERSION_MAJOR 1) ..which sets set(SOVERSION ${OCIO_VERSION_MAJOR} ...) If that number is changed back to 0,

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

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

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

Thanks for the reply ! Ok, I didn't know that. I'll have a look, it's interesting ! I see in the table that 3dl are ok... But I'm using Nuke 6.2v4... And I also have a shift with RV. Has RV a pb with

The Vectorfield node is a bit buggy - even if you write out a no-op lut (CMS test pattern->GenerateLUT) you get a luminance shift with several

Could try with a clean build directory - I seem to recall having the same error when I just ran git pull and rerun "cmake .... && make build"

I've built OCIO successfully on a clean install of snow leopard. Was this a clean installation or an upgrade (for the OS install)? -- Jeremy

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

Great :) That's much much better. Thanks a lot ! I still have some small differencies comparing OCIOColorspaceNode and my two TuttleCTL nodes. But I need to compare with CTLRender just to be sure it's

I just rolled out a new iif profile, with updated 3dluts. You'll note that inside the iif profile (in the lutimages subdir) are the lattice images used to bake the rrt / odt into 3d luts. So

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

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

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

Good to know, thanks! -- Jeremy

I used the LD_PRELOAD hack to get around it - actually this is just a manifestation of the more general nuke plugins linking to other libraries linking issue and I'm not sure changing the rpath is the

Was hoping someone else would field this question... Have you been able to figure it out yet? What platform are you on? I'm not much of a cmake expert, unfortunately. Are you familiar with readelf

FYI - I've updated the website with the previous response to the question. (In the upcoming weeks I'll be adding even more info / examples about creating color

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