Hi Simon & Community, OCIO 1.1.1 is from the branch RB-1.1 and it does not compile in C++11. But the reported error is a new C++11 syntax to initialize vector in a Yaml include file. So, the build can

Hi Paul, Following the work on OCIOv2 we discovered & fixed an issue around the list of active displays & views in the OCIOv1 implementation. Let me first explain a little bit some lines from the nuke

Test

Yes. Python 3 is not supported by OCIOv1.

The cmake flag to set is OCIO_BUILD_JNIGLUE. You can replace "-DOCIO_BUILD_JNIGLUE:BOOL=OFF" by "-DOCIO_BUILD_JNIGLUE:BOOL=ON".

Based on the build settings, vcpkg does not build the Python Bindings.

Congrats to @Yash Agrawal (potential GSoC student) for his first pull request being merged in the OCIO repo. As mentioned a good criteria for students willing to work in the OpenColorIO project is to

Yes. Maya supports OCIO i.e. the synColor engine reads any OCIO config files.

No problem. Asking a question is also a way to learn.

Hi Haggi, The thread disappeared from stackoverflow so I do not have access to all the source code anymore. The default implementation from ociodisplay is tex1 for the image texture (the 2D texture),

Hi, As a first investigation step, did you try using `ociodisplay` directly (i.e. as-is): `set OCIO=C:/daten/coding/imgview/imgView/AE_OCIO/config.ocio` `ociodisplay.exe -v c:/daten/testBilder/bake.jp

> A transform plugin API When looking for the plugin keyword in the former ocio-dev from google group, I found several threads with some around ExpresssionTransform. Is that the same discussion? https

Hi Brendan, The pull request is now alive (refer to 769). To select the 'fast' or 'exact' mode, there is an enumeration 'FinalizationFlags' (in 'include/OpenColorIO/OpenColorTypes.h') used by the meth

Hi Gonzalo, For the Windows platform jom (https://wiki.qt.io/Jom) is perfectly working. I faced the same problem without having enough time to dig in. Patrick