fyi homebrew/science has been deprecated. Luckily they migrated oiio/ocio into homebrew/core (default repo).

That’s the correct approach. The build steps from the readme are copied below. HP Building on Mac OSX Use the following commands to build these packages on Mac OSX OpenColorIO brew install -vd

We should find a way to fix this cyclic dependency once and for all. -- lg -- Larry Gritz l...@...

To build "ociolutimage", OCIO needs to be linked against OpenImageIO. These two packages have optional dependencies on each other, so build order can be troublesome if you need both packages with full

Just to highligth that ocio is expecting 'Red first' 3D luts.

How does a 3D LUT work? Each numeric row has three entries, which represent R, G, and B output values, often 0.0 to 1.0 (but could be higher or negative for some cases). Each row represents a position

maybe multiply by 63 instead?

I've been searching for weeks and can't find a clear explanation of how .cube files are written. Please help me understand them. I have a .cube file that was generated with 3D Lut Creator, with an

Another option could be to use the installed yaml (instead of the OCIO one) with USE_EXTERNAL_YAML

Hi Jan, According to the gcc documentation (Warning-Options), you could disable the warning with -Wno-deprecated-declarations Patrick.

Hi, I tried to compile OCIO version 1.1.0 on a Debian based distro using g++ 7.3.0: $ cat /etc/debian_version buster/sid $ g++ --version g++ (Debian 7.3.0-11) 7.3.0 I get error messages related to

I tried to create the original ACES 1.0.3 config from the included python folder via the 'create_aces_config' tool on my Mac. To do that, I installed all necessary tools via 'homebrew' (like 'ctl')

Seems to work, thanks. Not quite obvious from the documentation, especially if you only look at the API docs and not the user guide first. Am Montag, 28. Mai 2018 16:39:02 UTC+2 schrieb Sean Cooper:

Not at a computer to verify, but I believe you can just do a getColorspace() call using the user defined or default roles, the query the name of the returned object. Role names are equivalent to color

Just had a look in the Python API and wondered how I could get the referenced colorspace of a named role. Some of the roles are predfined as constants (OCIO.Constants.ROLE_...), but what's with user

Hey, I came to the same conclusion. I had thought the first colorspace was the special ‘reference’ colorspace (pretty sure Jeremy told me that...), but there is nothing in the code enforcing or

I've read the source. I didn't see anything special about the "first" colorspace. Unless someone can show me (either in the code or by an API call example) where it is somehow special, I won't believe

Hi folks- H.P., I also agree with that definition. But - it's also true that if you are converting to or from the 1st colorspace in the config list (aka "Reference" colorspace) we should see the

Yes, I completely agree with that definition. My assertion that 'reference' was related turned out to be something in our own code, not OCIO. ///d@

Cross posting for completeness The document detailing ACES support in various applications, is here (read