Problem summary:
Certain Nuke scripts can use incorrect colorspaces when rendered in Terminal mode
Customer reported version:
Nuke 14.1v4
Customer reported platform:
Rocky 9
Steps to reproduce:
1) Download the attached files and place them in the same directory: acescg.exr and test_file.nk
2) Render the test_file.nk in Terminal mode, like with the following command: "C:\Program Files\Nuke14.1v4\Nuke14.1.exe" --safe -x path/to/the/test_file.nk
3) Launch Nuke and use File > Open Comp... to open the test_file.nk
4) Observe how the EXRs rendered in step two are significantly darker and use an incorrect colorspace:
Expected behavior:
Nuke scripts rendered via the command line should produce results that match the GUI.
Actual behavior:
When certain files are rendered in Terminal mode, some Read nodes may not use the correct colorspace.
Additionally, if the test_file.nk script is opened in Nuke without using File > Open Comp... (by using a command like "C:\Program Files\Nuke14.1v4\Nuke14.1.exe" --safe path/to/the/test_file.nk) the Read node's Input Transform will be "linear" until an update occurs, like mousing over the Viewer or opening the Read node's Properties and pressing the Reload button:
Workaround:
Manually setting the Read1 node's colorspace/Input Transform knob to scene_linear (ACES - ACEScg) instead of default (scene_linear) makes the Terminal mode render produce the correct results.
Reproduced by Support in:
Nuke 16.0v2 - Windows 11
Nuke 14.1v1 - Windows 11
Nuke 14.0v4 - Windows 11
Unable to reproduce bug in:
Nuke 14.0v3 - Windows 11
Earliest version tested:
Nuke 14.0v3 - This issue doesn't appear in this version and has regressed
