Hello, I'd honestly say it depends on the time you have and your grasp of what problems you're trying to solve. In truth the larger hill of difficulty is from generating you're own luts and/or

Hi, During my integration of the OCIO library, I have mainly used the configuration files that can be obtained from the OCIO website, mainly nuke and Aces. I was wondering what is the typical use

It took me a bit of time mucking to get the allocation variables set properly. If you set your allocation variables type to lg2, the math for the lower and upper variable is the same as it is in an

Thanks for your answer Troy. I started to play with the latest version with the revamped GPU path. I'll have to wait for the official release to integrate it though. For now, I'll continue to see if I

There's two issues at work, both of which are important. The first is the deeper GPU issue that the ever wise Mr. Hodoul has fixed with the completely reworked GPU code path. That is a massive issue,

I traced it in the getGpuLut3D and what I see is that when it applies the LogToLin, this will clamp all negative values of the Lut1d. The resulting operation is 2^-15 -> 0.0000305. When the Lut1d is

I didn't investigate whether this is the exact same issue but this might be related to the issue you are experiencing. The bug: https://developer.blender.org/T56055 The fix:

Having a realistic timeline for OCIO v2 is quite challenging for now. Patrick.

Thanks for the confirmation Patrick! Also, in latest release, 1.1, I can see the same kind of behaviour. Let's say for the Nuke-default configuration, if I go from linear to SRGB, the resulting 3d LUT

Here is the github issue: #622

HiSimon, Thanks for taking thetime to use/test the master branch, and sorry for the delay to answer. I did someinvestigations, and you found a 'glitch' :-) inthe master branch (i.e. OCIO

Hi, I've been playing around an integration of OCIO using the GPU path (latest code version build 50) and things are going relatively smoothly. There's one problem that I still have though and it's

Thank you Deke Kincaid but i have seen this i am not able to import PyOpenColorIO as OCIO in Pycharm or any other things. If i can import those libraries i can easily do the OCIO configurations. I

Here are the docs & examples: http://opencolorio.org/developers/bindings/PythonAPI.html http://opencolorio.org/developers/usage_examples.html Were you looking for something more specific as your query

Hi; I just want to know how to use OCIO library or Module in a python script externally i am just new to python i know this is a basic one. Can anyone help me out from this issue..

Having CI for Windows Builds would be amazing to have!

Thanks Larry, I realised that too after posting this and managed to build it with 1.8. The ociotools got compiled properly too. Thanks, Sachin

Yeah, I'm sorry, in OIIO master branch (the *next* release, in development), there has been an API change that OCIO has not yet caught up with. That's my fault, it's on my list to fix right away. In

Hi, I'm using a CentOS 7.5 (3.10.0-693.2.2.el7.x86_64) docker instance to build ocio with devtoolset-6 and my build fails with the following

Thumbs firmly up from me as well. FWIW, OCIO was one of the case studies that the VES Tech committee brought to the ASWF discussion as deep dive examples, so the ASWF structure was in a way biased to