I'm wondering if companies are starting to put GPUs in their render farm machines. I have some GPU-accelerated code and looking at what it might take to convert it to pure CPU - and if that is even

Good work Richard! The ExternalProject stuff was added in 2.8, and I imagine quite a lot of other useful stuff was added since 2.6..

No problem. I've moved on to other things for the moment and haven't spent any more time on it. I'm mostly working on Linux at the moment so this isn't blocking me from doing anything else, but I'll

Sorry for the delay, have you been able to make any progress on this? Is it still holding you up? -- Jeremy

Well I figured out why 2.8 is needed: CMake Error at docs/CMakeLists.txt:7 (ExternalProject_Add): Unknown CMake command "ExternalProject_Add". -- Configuring incomplete, errors occurred! Looks

Awesome, congrats! We really appreciate all the work that went into this. :) When we do future dot releases, is there anything we need to do to keep Fedora up to date? Anyone know the CMake

I wanted to let everyone know that OCIO has been accepted into Fedora. I've already got packages working their way through the build system. Thanks to everyone for helping me deal with all the Fedora

I have a reviewer for getting OCIO in Fedora and he raised a question I don't really know the answer to. It appears that the cmake configuration assumes SSE support even on i686 which includes

Pull-request'd: https://github.com/imageworks/OpenColorIO/pull/271

https://github.com/imageworks/OpenColorIO/pull/270

Does anyone have instructions for building OpenColorIO on windows? I've been struggling with this over the last day or so -- neither the nmake nor Visual Studio generators seem to entirely work. I

Yup - that's basically what I've done. This code here gets me what I need right now - https://github.com/cjwills/OpenColorIO/commit/06d930b9646590546711cced1828c040cada64aa - I'll finish it up

The --look arg would only make sense with the existing-config options (e.g "--inputspace lg10 --outputspace srgb8 --look di"), so it should be pretty straight forward - just need to make sure the

https://github.com/imageworks/OpenColorIO/pull/267

Sounds good. So let's update the default. -- Jeremy

I'll take a stab, since I need it this week ;)

That's an accidental omission. "ociobakelut --look" totally makes sense. It's not super straightforward to add, unfortunately as ociobakelut currently creates a new temporary color configuration for

I have a bunch of look transforms set up that I would like to bake into luts. ociobakelut doesn't seem to know anything about looks currently so is there another way to do this? Or would it be

I like It spelled out OpenColorIO. How about an additional env var: OCIO_CONFIGS, which can be set to a ;-separated list of paths. The default would be the ones you've been talking about. Have paths

Right. I've already got the <common appdata> thing going per your suggestion. I'd like to hear other people's opinions on the others. If this list gets expansive, maybe some official code should be