Please help! I am trying to load in a file, resize it, apply a .cube LUT then write it out. I have the following so far, but I'm falling over between the oiio > ocio parts (one using an oiio.ImgBuf

Hello, I decided to implement the custom transform idea I posted earlier and send a pull request: https://github.com/imageworks/OpenColorIO/pull/390 The implementation is quite short and simple, it

You need to print and later parse 8 digits to uniquely capture a float. For those craving more information: https://randomascii.wordpress.com/2012/03/08/float-precisionfrom-zero-to-100-digits-2/ ///d@

Thanks for digging into this, and my apologies for missing the obvious limit of float precision. I was running into an issues where the limited precision is combined with high-intensity values to

There is also a bug in yaml-cpp which prevents this in src/emitterstate.cpp it needs fixing to read: bool EmitterState::SetFloatPrecision(int value, FMT_SCOPE scope) { if(value < 0 ||

There are cases in the code where the precision of the formatting is used to generate Cache Ids, changing the precision here would change the behavior there are also cases with luts where certain

<kevin.j....@...> wrote: looking through the code the matrix is stored as single precision float and the bindings to python also assume as such, the image processing also works as float, storing

sounds like limits of float precision to me. that would mean being 'double' clean through the code, Kevin

Hello, Is there a way to configure the precision used for floating-point values stored in a config? I have a Python script that generates a config based on a bunch of inputs, including a number of

Hi Steve, These all seem like fair points. I'll take a look at this tomorrow and update the config. The questions around the linear range covered by ACEScc may need a bit more investigation. HP

Hi HP, I'm looking into rolling an internal project's OCIO configuration forward to use as much of your ACES 1.0 config as possible. I've run into a couple of issues and wanted to run them by

Hi, I recently found that it would be quite useful to have a CustomTransform that allows to add own Transforms without changing the actual OCIO code. My idea for this would be to have a

Congrats to everyone who worked on this. It is a huge achievement and you have made a great improvement to the industry. I can't wait to play with all of it, and test it on the first project that

Hello, The ACES 1.0 Developer Release is officially available! Full product information can be found on the revamped website, http://www.oscars.org/aces. To give you a preview, the ACES 1.0 release

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