ID 389480 - Denoise Temporal Processing stays enabled after disconnecting motion input

Follow

Problem summary
When using the Denoise node within Nuke, if "Temporal Processing" is enabled disconnecting the 'Motion' input will not disable the process.
This can cause issues, such as longer render times and unintended graphical errors.
 


Customer reported version
nuke.11.2v4

Customer reported platform
centos7

Steps to reproduce

1) Create a Denoise node
 
2) Create another node ( e.g a Constant ) and attach both the 'Motion' and 'Source' inputs.
 
3) Tick the 'Enable' checkbox within the 'Temporal Processing' dropdown.
 
4) Remove the 'Motion' input from the Denoise node
 
Result: The checkbox will still be ticked and can't be disabled, this appears to run when Terminal rendering.

Expected behaviour
Temporal processing should be disabled automatically if there is no motion input.

Actual behaviour
The temporal processing is enabled after disconnecting the motion input, may cause issues.

Workaround
Reconnect the motion input to any node, untick "Temporal Processing" and disconnect the motion input.
 
OR
 
Execute the following snippet in the Script Editor tab while selecting the node:

nuke.selectedNode().knob('enable_temporal').setValue(0)

Reproduced by support
Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7
Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7
Nuke11.2v1 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v1 - Windows 7 - Mac10.14 - CentOS7

NOTE: GUI rendering in Mac appears to display the issue.

Earliest version tested
- This feature did not exist before this version ( Temporal processing )
 

    We're sorry to hear that

    Please tell us why