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

Hi Robert, I'm curious... will your changes be rolled into the main OCIO repository? (If not, I should probably make a patch to apply to the main one for the next time we need to update our OCIO

Hey guys Has anyone tried baking out icc profiles recently? I've been trying to bake one out with variations on the following command: ociobakelut --format icc --inputspace acesproxy --outputspace

Ignore this... It was something broken in my brew..

Hey guys "brew install opencolorio" is currently failing for me under MacOSX 10.9.3 Was this working a few weeks back? -Alex 192-168-1-7:~ alex$ brew install opencolorio ==> Downloading

------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------ OpenColorIO COP2 nodes for

Good morning! I have finally developed that OCIO enabled color selectors feature in Krita (some time ago I asked about reversed Display transformations in this list to make this feature). You can read