I am trying to improve an issue with slow startup times on ACES1.2 (with latest git OCIOv1.0) of about 3-5 seconds. The slow startup time is on my viewer (mrViewer), but a similar issue was reported o

Okay, I found out what is wrong. The YAML library is getting compiled with std::cxx11 strings and libOpenColorIO is not. However I don't yet know how to force either of one to compile in the same abi

After installing OpenColorIO v2.0 without any problems, I am now trying to revert the change to OCIO v1.1.1. However, on the linking phase of the utilities, I get a bunch of YAML missing reference sym

Please add mrViewer which is a professional flipbook player, hdri viewer and video/audio playback tool. It supports OCIO input color spaces in images as well as display/view color spaces.

Okay, I found out what magic it is. The R3DSDK has an ImageProcessing struct and I was not setting it. Once I set it to the camera settings, everything started to match. Note that besides the camera s

Okay, here's a crazy one. If I decode the R3D clip as 16 bit, and I set the input color space to Output - Rec.709 and set the view to Rec.709, I get a matching picture to the one you saved out from Nu

Glad to know. Currently, I cannot get the same result with the sRGB/rec709 of ACES. I get a close to good, but darker and more saturated image, as I got with exrs. This is the issue with the RRT+ODT.

Dear Eberhard, I can confirm that the Nuke default one is matching my version completely, but without the middle node that you have in the Nuke script. The RED SDK it seems already sends a half image

It happens with any RED file, but if you want one to try, try the first clip (the one with the guy in the motorcycle) from the sample 3d files: http://downloads.red.com.s3.amazonaws.com/sample-r3d-fil

One thing I noticed is that I get different results in decoding the clips with RED's PixelType_HalfFloat_RGB_Interleaved and PixelType_16Bit_RGB_Interleaved. The 16 Bit clip seems to be in log space,

Hi Eberhard, I tried that with my viewer (setting the ocio colorspace input to Input - RED - REDLog3G10 - REDWideGamutRGB) and set the display/view to ACES->sRGB and the results were all colors like a

Yes, it was a RED sequence, but I was just testing it with scene_linear. What's the IPP2 color pipeline? Is it some Nuke node, some OCIO config transform or the IPP2 function that appears in the RED S

Hi, Eberhard. Yes, that's more likely what I am seeing. Thanks for the detailed explanation. Cheers, Gonzalo

I recently noticed a discrepancy in the sRGB output transform of nuke-default's and ACES' one. Basically, Nuke's seems to have an additional 2.2 gamma transform while ACES does not seem so pronounced.

Is there a target to build only the OpenColorIO tools?

Patrick, thanks for the tip about jom (didn't know it existed). However, my problem was compiling on linux.

I have tried to compile OpenColorIO with the Ninja generator and it fails with: FAILED: ext/Yaml-cpp-prefix/src/Yaml-cpp-stamp/Yaml-cpp-build ext/dist/lib/libyaml-cpp.a cd /media/gga/Datos/code/applic