Problem summary The BurnIn soft effect/node doesn't accept specific custom values (ie. 'input/ctime') in its dropdown knobs, when set via Python. The behaviour seems to happen with both the setValue() and fromScript() functions. This behaviour also seems to be inconsistent with other other EditableEnumeration_Knobs.
Customer reported version Hiero 14.0v6
Customer reported platform Rocky 8
Steps to reproduce
1) Open Nuke.
2) Execute the following code in the Script Editor:
b = nuke.createNode("BurnIn") b['burnIn_topLeft'].setValue('input/ctime')
RESULT: The burnIn_topLeft knob is set to input/filename.
3) However, most values do work, for example:
b = nuke.createNode("BurnIn") b['burnIn_topLeft'].setValue('test')
4) You can also compare this to other EditableEnumeration_Knobs, by executing the following code in the Script Editor:
n = nuke.createNode("NoOp") k = nuke.EditableEnumeration_Knob("test", "test", ["none"]) n.addKnob(k) n["test"].setValue("input/ctime")
RESULT: The new value is added to the EditableEnumeration_Knob. You can keep running the last line, with new values, to keep updating the knob.
Expected behaviour You should be able to set the BurnIn soft effect/node's dropdown knobs to any custom value via Python, like you can with other EditableEnumeration_Knobs.
Actual behaviour Trying to set any of the BurnIn's dropdown knobs to input/ctime via Python it actually gets set to input/filename.
Workaround You can still set it manually via the GUI but no workaround for setting it via Python is known.
Reproduced by support This bug has been reproduced in: Nuke 15.1v2 - Windows 11 - macOS 12 Nuke 12.0v1 - Windows 11 - macOS 12
Earliest version tested Nuke 12.0v1 - This issue appears to be in all tested versions of the product