No problem! Let me know if you have any troubles with the updated version. I should also probably update the ociodisplay program to query the glsl version, and select the best profile

Committed. Thanks! -- Jeremy <malcolmh...@...> wrote:

Oh snap, you have already fixed this. I haven't updated for a few days. Sorry for the list noise. .malcolm

Those who are having trouble with GLSL, are you on the most recent version of OCIO? I made a commit last week (which is in version 0.7.5), where on OSX the const keyword would be omitted for GLSL 1.0

Hi Mark, Thanks for the reply, well that makes sense why it hasn't really been an issue till now. How would you recommend to solve these types of issues? I can see two obvious ways. if/then blocks

There is a const qualifier in GLSL, and it should work on other platforms without issue. The difference may be that OSX only supports GLSL 1.20 currently, which is far behind most of NVidia's and

Is the 'const' qualifier in glsl? I have to change the following to get the glsl shader to compile on OSX. I'm cool to add another if glsl or cg block, just wondering if this could be something

When building some UI menus, I wanted to get a list of defined roles. Config::getRoleNameByIndex() only returned the resolved colorspace name. --snip-- Replaced config->getRoleNameByIndex (which

LGTM LGTM This is a good fix till we add boost/shared_ptr.hpp to ocio or replace it with tr1/memory in OpenColorTypes.h. Right now you need boost on linux to build. .malcolm +1 .malcolm

If I understand correctly, the Context allows you to set a search path including env-variables (e.g $SEQ/$SHOT), so you can define a FileTransform, and it'll look in the shot's directory before the

Oh, good point - I forgot PYTHONPATH also. Mentioned both of these, and few other minor changes: https://github.com/dbr/OpenColorIO/commit/573356952ca30f90b3cb4aafa925b33cbf974f99 Also a

rock and roll these docs are great. The only thing I can see is missing is a section on NUKE_PATH in the environment section. .malcolm

**Version 0.7.5 (Jan 13 2011):** * ociodisplay enhancements * gpu display bugfix (glsl profile 1.0 only) * Makefile enhancements * Nuke installation cleanup * Doc generation using

This makes sense as you get to release. The code gets the most frequent updates and the webpage represents the current used version.

Agreed; now moved into 'apps'. <malcolmh...@...> wrote:

Oh, and an observation: we now essentially have two masters for the docs, the inline documentation, and the webpage version. My inclination is to treat the git version as the master, and then to

Looks good to me. These commits were all on the same topic, so I merged them into a single checkin, "Documentation cleanup". Thanks! -- Jeremy

Added Python versions of most of the C++ usage examples (except the GPU one, as the Processor.getGpuLut3D method isn't exposed). Might not be terribly practical code, but it's a nice demo of the

Good point about the viewers. Thinking about it now, I wouldn't use the viewer-proc registration from the OCIO installation, as it'd be untweakable.. So, perhaps this would be more appropriate as part

Yep this fixed it, and yeah I was just copying large sections of ociodisplay. Ok thats good to know. I've been using what ever the values are in the current spi-vfx profile just to cutout any added