Ok, so I'm able to fully reproduce your error when using static linking with a simple test case. g++ main.cpp -Ibuild/dist/include -ostatictest build/dist/lib/libOpenColorIO.aI created a main.cpp,

Sorry, i'll try to look into this. Is anyone out there successfully statically building against OCIO? -- Jeremy

Just checking in to see if anyone has some magic voodoo for this - thanks Piotr

So would I/we. George - BlueBolt

So if you look in the aces configuration, you'll see there are two .ocio files. config.ocio and config_1_0_3.ocio. config_1_0_3 explicitly specifies tetrahedral interpolation for the rrt 3dluts.

I was experimenting with the ACES configuration the other day. I applied the RRT to a grey ramp and saw some subtle color artifacts, which could be verified by boosting the saturation. I tried

Ack. I tried editing it in github since it's a minor change but when I submit it I get a github 404 not found. I'll submit something straight from git when I get a chance and I'll add EPEL when it

Hi Jeremy, Sorry for the delay in getting this info back to you. This is what our build people say: We're actually building verison 1.0.6. This was a clean build, and we're not using ocio

Sounds great. Can you send me the real distro list? Im happy to add it. Or you can edit the docs rst file, and submit a pull request.

Since ocio is now in Fedora and is on it's way in EPEL for EL 6, I was thinking it may be nice to put another subsection on the install page for distro's that have packaged OCIO. Thought? Richard

This will be my last pull request for a while, promise! https://github.com/imageworks/OpenColorIO/pull/274 Added an interpolation menu when loading a LUT directly, per

Pull request here: https://github.com/imageworks/OpenColorIO/pull/273 The After Effects plug-in currently is built with Xcode and Visual Studio projects. When they were move to their new homes

Awesome! :) -- Jeremy

Yup... I finally got a build (including PPC64) for EL 6! Here's what I had to do to get it to work (some of it obvious!): - change the CMAKE_REQUIRED_VERSION to 2.6 - Remove

Yes indeed! But the Windows build process is less than ideal, so I thought I'd do a gut-check first! :-)

Have you considered MESA GPU emulation for the CPU code path? I believe there are' unnamed' graphics packages out there that use a pure GPU codepath locally, and provide minimal CPU rendering support

Thanks for the pointer. It's an effect we've developed that has a very natural OpenGL-based implementation. To get it to run entirely on the CPU we'd basically need a CPU implementation of OGL - or a

Got a sizable pull request to add the AE plug-in: https://github.com/imageworks/OpenColorIO/pull/272 Here's what I wrote in the comments: Have the After Effects plug-in ready to integrate. It has

Can you provide any additional details on the type of code you're considering porting? At SPI we still do the vast majority of our 'farm' rendering on the CPU. But the artist desktops are fully GPU'd,

Ugh! Sorry to hear you've having trouble with static linking. Can you post the shell command you're using to build OCIO with? (At SPI we happen to only use OCIO in a dynamically linked context so we