Re: nuke-default's sRGB and ACES 1.1 sRGB

Eberhard Hasche

Hi Gonzalo,
maybe you should consider that something in your pipeline is broken.

I tried your file out and all worked fine. Attached are two Nuke files (one ACES 1.1, the other
Nuke default) with all necessary color conversion nodes.
I rendered out two 1/8th resolution jpg images set to Rec709. The only difference in the color pipeline is that with the nuke-default image,
the picture-rendering part is missing, so it is clamped at 1.o whereas the
aces image is a bit brighter because parts of the luminance above 1.o has been rolled in.



----- Ursprüngliche Mail -----
Von: "Gonzalo Garramuño" <ggarra13@...>
An: "ocio-dev" <ocio-dev@...>
Gesendet: Freitag, 6. Dezember 2019 11:22:37
Betreff: Re: [ocio-dev] nuke-default's sRGB and ACES 1.1 sRGB

On 6/12/19 03:16, Eberhard Hasche wrote:
Hi Gonzalo,


It is interesting. Maybe there is a look buried in the MetaData i. e. a tinting
or some white point problem.
May you give me the link to the RED-file?


It happens with any RED file, but if you want one to try, try the first
clip (the one with the guy in the motorcycle) from the sample 3d files:

When I decompress it as HalfFloat and try the Log* WideGamutRGB, I get a
posterized look.  When I decompress it as 16bit short, I get a better
but too dark image.

Join { to automatically receive all group messages.