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

Whilst I agree with the reasoning, I think it is better to be clear that there is no hard commitment for the ACES work to be moved under ASWF, there was discussion about this at the ACES next BoF but

I didn't realize how much I wanted a mysterious council of alien overlords until you said we weren't getting one. ;) That all sounds great, Larry. Thanks for the clarification. Within the ASWF

ASWF is not involved in the design or development per se. It's *us* who avoids design by committee, if that's what we want. In the process of being accepted, we (as a community) would need to

My only concerns are around the general benefits of having a single, production-focused sponsor (SPI in this case). As Larry alluded to, there are pros and cons to a single sponsor, the greatest con

Two thumbs up. OCIO is a great candidate for the services and standardization that the AWSF will provide. HP

Thumbs up from me. Another reason I see is that in my mind the Academy's ACES config is now the de facto "reference implementation" for OCIO and it makes sense to have them living closer

I'm all for it. OCIO has become an essential part of the VFX world and making sure its development will continue in a healthy fashion is important, in my opinion. I'm very happy to hear

Hey, everybody. We're thinking about applying to turn OpenColorIO governance over to the Academy Software Foundation (ASWF), and they are very enthusiastically seeking our application. Before we get

Any plans to update ACES config to version 1.1 (https://acescentral.com/t/aces-1-1-now-available/1420) in near future? Thanks

A big thank you from BlueBolt to all involved in the exciting developments announced last week at the BOF. Please could someone with slack workspace admin rights send me an invite for: