Problem summary OCIOCDLTransform node will clamp pixel values greater than 1, when the CDL values are at default.
Customer reported version N/A
Customer reported platform CentOS 7
Steps to reproduce
1) Open Nuke.
2) Go to Edit > Project Settings > Color tab.
3) Set color management to OCIO and OCIO config to aces_1.2.
4) Create a Ramp node.
5) Set the positions for p0 and p1, and set its color knob to value to a value higher than 1. For example:
Ramp { p1 {1738 950} color 10 name Ramp1 selected true xpos 73 ypos -131}
6) Mouse hover the Viewer and notice that the pixel values can be greater than 1.
7) Add a OCIOCDLTransform downstream from the Ramp node.
8) Set the OCIOCDLTransform node's working space knob to "Input - ARRI - V3 LogC (EI160) - Wide Gamut"
9) Mouse hover the Viewer and notice that any pixels values that were greater than 1 will now be clamped.
10) Change any of the slope, offset, power and saturation knobs by any value.
11) Mouse hover the Viewer and notice that the pixel values are no longer clamped.
Expected behaviour The pixel values should not be clamped to 1, when the OCIOCDLTransform node's slope, offset, power and saturation knobs are set to default.
Actual behaviour The pixel values are clamped to 1, when the OCIOCDLTransform node's slope, offset, power and saturation knobs are set to default.
Workaround The issue does not occur if you set the OCIO_OPTIMIZATION_FLAGS=263994307 environment variable on your system.
Reproduced by support This bug has been reproduced in: Nuke 14.0v5 - Windows 10 - Linux CentOS 7 Nuke 13.1v1 - Windows 10 - Linux CentOS 7
Unable to reproduce bug in: Nuke 13.0v10 - Windows 10 - Linux CentOS 7
Earliest version tested Nuke 13.0v10 - Windows 10 - This issue doesn't appear in this version and has regressed