Helloo, I really like this PR: https://github.com/imageworks/OpenColorIO/pull/366 :) Someone knows why it's on hold ? Thanks, Marie

texture3D() is also deprecated in GLSL 1.30, so it should be returning the texture() version for 1.30. An additional enum shouldn't be needed since GLSL is forward-compatible from 1.30 onwards. It's

Hi everyone, I saw that the GpuLanguage enum goes only up to GLSL 1.3, are there any plans to support anything higher? I'm using getGpuShaderText() to get the fragment shader snippets but its still

Merging/hierarchical configs have been discussed in the past, but I suspect will not happen any time soon (it is a difficult problem to solve) The best solution/alternative I am aware of is to

Hi guys, How can I set up my pipeline so I have multiple config file building my color management profile. The idea is to have config at facility level and then have show specific but that would add

Hello, Just to say thanks and let you know that last versions of LittleCMS are able to perform color conversions in unbounded full floating point mode and generates ICC v4.3 profiles. latest LCMS

to answer my own question: It seems I had the wrong idea about how the FileTransform worked. From Configs/nuke-default/make.py: create the colorspace, then appy using oiio.ImageBufAlgo.colorconvert cs

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