Hi guys, I do understand the limitations of the use of env vars to point to shot grades, but dont know how to deal with it (even 4 years later) in case of flipbooking with RV. Do you have any

thanks a lot for this! Am Montag, 21. Oktober 2013 17:15:40 UTC+2 schrieb Marie Fétiveau:

Hi Mark - just to confirm that the fix works (as expected) just fine.

Hi Jose You are using a 3d lut which is not reversible. Only 1d luts are reversible. Is this a lut that you created? On Fri, Jul 25, 2014 at 3:47 PM, Jose Enriquez <jenr...@...> wrote:

Hello everyone, I have a problem creating a lut from nuke to hiero, in hiero I receive this error; LogCrec709 inverse; 1 OpenColor IO Error: 3D Lusts can only e applied in the foward

I can't check that immediately, but when I have got the time to check it out I shall report back. Thanks for the help Mark. - Simon.

Hi, Just following up. This issue should now be resolved. I have patched OCIOYaml.cpp, and pushed those changes to master. If you are able, could you confirm that this solves your issue? Cheers, Mark

Ah right, now I see where the problem is! Thanks for the breakdown, I've opened an issue on the github bug tracker, and I'll look to patching this

Hi Mark, I'm using Visual Studio 2012, 64-bit compilation in debug. If you view the disassembly of OCIOYaml.cpp in the load function (or set a breakpoint in ~basic_string) you can see where it's

"This applies only to non-linear input colorspaces" => not non-linear, all colorspaces except Linear. Den onsdagen den 23:e juli 2014 kl. 09:07:28 UTC+2 skrev mikae...@...:

Not really - it happens outside Nuke using the ocio GPU support: OCIO::DisplayTransform::create() displayTransform->setInputColorSpace( "sRGB" ) displayTransform->setDisplay( "display"

Hi Simon, Not sure I see where a bug could be hiding. The scoping around those blocks seems fine to me. setActiveDisplays(), though taking a const char * as an argument, never actually stores it

Hi Mikael, Just trying to see if I'm understanding your issue correctly. When using the OCIO Display node inside of Nuke (with the OCIO environment variable pointing to the nuke-default/config.ocio

I'm testing out some code and I've noticed a crash issue when a config (such as ACES, from the ICIO website) contain multiple active displays or views. Basically, the code in ICIOYaml.cpp that takes

I'm doing automated slap-comps to check render output in sRGB/Cineon and scene-linear, if I use the nuke profile and "None" as the view for the default display the profile returns "raw". It should be

You could also try a "pared down" version. ;-). I love autocorrect.

Wow, I was only expecting to find ociobakelut.exe from the link Marie provided, but as far as I can see there are exes of all of the OCIO command line tools. Very nice and thanks a lot, seems to work

Jeremy. Just a suggestion but you may want to consider a branch structure similar to the one described here. http://nvie.com/posts/a-successful-git-branching-model/ We use a paired down version of

Up until now we've been running OpenColorIO with myself as the "Benevolent Dictator". This has seemed appropriate for the early stages of OCIO's life where development was fairly dynamic and we had a

For those of you attending SIGGRAPH 2014 in Vancouver, we will be once again holding an event for developers and users of VFX-specific open source projects. It's a great chance to meet in person with