Problem summary
Using one slider to adjust a color component will affect other color components. (I.e., dragging M in TML, causes T and L to change). Affected color components include hue, saturation, lightness, temperature, magenta, luminance, or value, and in some cases the red, green, and blue components. This behavior occurs both in the color sliders in the Parameters tab and in the color picker dialog when Enable Display Transform is turned on.
When no OCIO configuration is loaded, only the HSL, TML and HSV tabs experience this behavior. In certain OCIO configuration files, like ACES (see attached aces_1.0.3.zip), the RGB tab also experiences this behavior.
In contrast to this, the NUKE color picker dialog and other software usually treat component values of the same representation independent of each other. For example, in NUKE, you can change one component in HSV, which will affect (potentially all of) the RGB components, but not the other components of HSV. Other industry software behaves similarly in isolating color components this way.
This behavior is a design consequence of the approach in presenting LDR widget numbers in a color-managed HDR color picker. However, it is inconsistent with other software applications that work with RGB, HSL, TML, and HSV sliders, and is not user-friendly.
Note that the TML tab was introduced as a replacement for the HSL tab in Katana 4.0v1.
Customer reported version
3.0__3.0v1
Customer reported platform
CentOS 7
Steps to reproduce:
Case 1: Parameters tab:
In the Node Graph tab, create an ImageColor node and set its edit flag.
In the Parameters tab, select the TML tab of the color parameter.
Drag the saturation slider.
Note that the luminance color component values are adjusted when the saturation is changed.
Case 2: Color picker dialog:
In the Node Graph tab, create an ImageColor node and set its edit flag.
In the Parameters tab, double-click the color thumbnail to open the color picker dialog.
In the color picker dialog, select the TML tab.
Ensure Enable Display Transform is turned on.
Drag the saturation slider.
Note that the luminance color component values are adjusted when the temperature and magenta are changed.
Workaround
No known workaround.
Reproduced by support
This bug has been reproduced in:
Katana7.0v4 - Windows 10, Rocky 9
Katana6.5v4 - Windows 10, CentOS 7
Katana6.0v5 - Windows 10, CentOS 7
Katana5.0v7 - Windows 10, CentOS 7
Katana4.5v7 - Windows 10, CentOS 7
Katana4.0v8 - Windows 10, CentOS 7
Katana4.0v1 - Windows 10, CentOS 7
Katana3.6v5 - Windows 10, CentOS 7
Katana3.5v5 - Windows 10, CentOS 7
Katana3.2v6 - Windows 10, CentOS 7
Katana3.1v7 - Windows 10, CentOS 7
Katana3.0v2 - Windows 10, CentOS 7
Katana3.0v1 - Windows 10, CentOS 7
Katana2.6v4 - Windows 10, CentOS 7
Katana2.6v1 - Windows 10, CentOS 7
Katana2.5v7 - Windows 10, CentOS 7
Katana2.5v1 - Windows 10, CentOS 7
Katana2.1v6 - CentOS 7
Katana2.1v1 - CentOS 7
Katana2.0v5 - CentOS 7
Katana2.0v1 - CentOS 7
Katana1.6v3 - CentOS 7
Earliest version tested
This issue appears to be in all versions of the product.
Expected behaviour
Hue, saturation, temperature, magenta, luminance, RGB, or value settings should be isolated from each other in the Parameters tab and in the color picker dialog when Enable Display Transform is turned on.
Actual behaviour
Using one slider in the color picker, or in the color picker dialog when Enable Display Transform is turned on, to adjust a value affects the other sliders as well.