Problem summary Users have found render issues when rendering via Terminal mode when using a combination of Denoise and Keylight nodes. From our investigation, this issue appears to be due to Temporal Processing being enabled within the Denoise nodes.
As an example, rendering the attached script in Terminal displays the following graphical problem:
Temporal Processing ON:
Temporal Processing OFF:
From reviewing the behaviour, it appears the script attempts to process but fails due to no motion data. ( Motion data is black )
Disabling the Keylight node or rendering via the GUI appears to provide the correct results.
Customer reported version nuke.11.2v4
Customer reported platform centos7
Steps to reproduce
1) Open the Attached script
2) Render the GUI Write nodes.
3) Read the footage into Nuke and view the results. The footage should look like a basic ramp.
3) Exit Nuke and Terminal render the script
Result: Reading the footage into Nuke will display a distinct white mark.
Expected behaviour The rendered footage should have no graphical glitches.
Actual behaviour Rendering through Terminal mode displays a graphical glitch in the footage.
Workaround As there is no motion data, the Temporal Processing can be disabled. 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:
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 )
