Certainly. Here's CBS Digital's fork of OCIO: https://github.com/CBSDigital/OpenColorIO/tree/master You can see my latest commits. The bulk of the code is in FileFormatCTF.cpp.

Hi Ben, That sounds great! What you've described sounds like you're heading down the right track. If it's possible, could you post the code to a github account? That way we could better collaborate,

Hello all, My name is Ben Doherty, and I'm a developer working for CBS Digital. We’re interested in addiing support in OCIO for The Academy's Color Transform File (CTF) LUTs. This additional

+1 for the common still camera gamuts. Prophoto, Adobe Wide Gamut, and Adobe RGB. There's a smattering of different whitepoints and gammas with those, which can be annoying to deal with.

I'm a bit late to the party, but for what it's worth, Red log (with their various red color primaries I assume?), Canon log, and GoPro "protune" were popular requests for inclusion in the default Nuke

I needed to get git-savvy anyway, so I went ahead and made a pull request for this patch: https://github.com/imageworks/OpenColorIO/pull/381 Cheers, -Mike

On the IDT side, the current Academy repo includes IDTs for the following cameras / configurations Arri Alexa with the following exposure indices: EI800, EI640, EI500, EI400, EI3200, EI320, EI2560,

Hey open source VFX fans, excuse the spam but I wanted to point you to a project I think would be of interest to people on this list. It's MOX, an open source movie format for

Yes, and I suspect we will continue to receive camera native material for a while. VFX houses will adopt ACES more quickly than production houses. Would it be a good idea to include

It's not uncommon to receive external material in camera color spaces and to want to ingest them using the same OCIO-supporting tools that are used for color management internally. That could be

Good suggestion. We'll have to override some of the currently automatically generated transforms. Could you provide some example of when and how you would use the IDTs with OCIO? From a number of

you might want to account for different scalings of the log spaces (full range vs SMPTE levels), although the most useful form for OCIO is obviously the one in which CDL values apply directly. Kevin

I'm looking forward to updates to this config, especially when it includes the existing IDTs. Once comment so far: You don't need a LUT to convert between ACES and ACESproxy; OpenColorIO can do it

Hey guys I'm trying to implement OCIO Looks on a job at the moment. Ideally, I'd like to be able to point to a series of shot specific .cc files on disk, but this falls over when I have shots with no

Hello OCIO developers and users, The Academy is moving towards an official 1.0 release of ACES this fall. As part of that development effort, we are looking at the best way to support ACES through

Hi, I have an issue when trying to create a config from the environment, more specifically when no env variable is set. The configuration that is returned contains one color space named "raw". In my

I don't think so. I used to use the "colorspace" attribute stored on assets at my *previous* job to determine color space and only fall back to the file name if that didn't exist. Naming conventions

I'm going through this right now, and have the horrible problem of trying to educate people to add the right color space to their filename, knowing full well that there is a strong likelyhood that

Thanks Mark. If you wouldn't mind handling the pull request, that'd be helpful. I'm afraid I'm still not fully up to speed on git. -miker

Hi, I'm a bit puzzled by the existence of these two variables, as they seem to do the same thing at first glance. Looking quickly at the code it seems they have different behavior, but I don't quite