ID 347836 - Applying an OCIO config to the viewer process or using the Timeline Viewer versus the OCIOColorSpace node gives a different result, when comparing the separate RGB channels

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
Applying an OCIO config to the viewer process or the Timeline viewer versus the OCIOColorSpace node gives a different result, when comparing the seperate RGB channels.
The below image shows the red channel of each image when the Colorspace has been set.

​
​

Customer reported version
Nuke 11.1v3

Steps to reproduce

1) Open Nuke 

2) Create a ColorBars node (Image > ColorBars) and attach it to the viewer.

3) Open Project Setting (Edit > Project Settings) and open the Color Tab. Set the 'color management' option to OCIO and the 'OCIO config' option to aces_1.0.3

4) Open a second session of Nuke. This will allow for a side-by-side comparison later.

5) Repeat steps 2 & 3 in the second session of Nuke

6) In between the ColorBars and the Viewer, create a OCIOColorSpace node (Color > OCIO > OCIOColorSpace).

7) On the OCIO Colorspace node, set the 'out' option to 'Output - sRGB'.

8) Set the Viewer Process in the Viewer to 'Raw (ACES)'.

9) If you now compare the individual RGB channels (Press R, G, or B respectively with the mouse over the Viewer) in the two Nuke sessions, the colors should be slightly different. The below screenshots show this difference.

Red channel:

​

Green channel:

​

Blue channel:

 
*If you render the Colorbars and Read them into Nuke Studio/Hiero, then you get the same results as using the OCIODisplay node:

​

Reproduced by support
This bug has been reproduced in:
Nuke 11.1v3 - Windows 10 - OSX El Capitan - Linux CentOS 7
Nuke 11.1v1 - Windows 10 
Nuke 11.0v4 - Windows 10 
Nuke 11.0v1 - Windows 10 
Nuke 10.5v7 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v6 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v9 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v7 - Windows 10
Nuke 8.0v1 - Windows 10
Nuke 7.0v10 - Windows 10 - OSX El Capitan - Linux CentOS 7

Earliest version tested
Nuke 7.0v10 - Windows 10
- This issue appears to be in all versions of the product

Expected behaviour
Applying an OCIO config to the viewer process and using the OCIOColorSpace node should produce the same end result, when comparing the seperate RGB channels.

Actual behaviour
Applying an OCIO config to the viewer process and using the OCIOColorSpace node does not produce the same end result, when comparing the seperate RGB channels.
 

    We're sorry to hear that

    Please tell us why