Problem summary:
A "Bad value" error occurs when Nuke is in Terminal mode and a Viewer's monitorOutPixelFormat knob has been set to "half"
Customer reported version:
Nuke 15.1v3
Customer reported platform:
N/A
Steps to reproduce:
1) Launch Nuke and double click the default
Viewer node in the Node Graph to open its Properties.
2) In the
MonitorOut tab, change the
Pixel Format from "8 bit" to
"half"
3) Navigate to
File > Save Comp As, then save the Nuke script and close Nuke.
4) Launch Nuke in Terminal mode with the
-t flag and open the saved file, like with the following command:
"C:/Program Files/Nuke15.1v4/Nuke15.1.exe" C:/path/to/the/test_script.nk
5) Observe the error that appears:
ERROR: Bad value for monitorOutPixelFormat : half
Expected behavior:
Opening a Nuke script in Terminal mode should not produce errors when none occur if Nuke is launched with the GUI.
Actual behavior:
If a Viewer's
monitorOutPixelFormat knob has been set to "half", a "Bad value for monitorOutPixelFormat" error will occur whenever the file is opened in Terminal mode.
Attempting to access the
monitorOutPixelFormat knob's current value like with the following code will produce the expected results in the GUI, but return
4294967295 in Terminal mode:
v = nuke.toNode("Viewer1")k = v["monitorOutPixelFormat"]print(k.value())print(k.getValue())
Workaround:
Besides ensuring the
monitorOutPixelFormat knobs on all Viewers are set to "8 bit" before opening the file in Terminal mode, there is no known workaround at this time.
Reproduced by Support in:
Nuke 15.1v4 - Windows 10, macOS 14 Sonoma
Nuke 14.1v1 - Windows 10
Nuke 14.0v1 - Windows 10
Nuke 13.2v1 - Windows 10
Earliest version tested:
Nuke 13.2v1 - This feature (the Viewer's
monitorOutPixelFormat knob) did not exist before this version