Problem summary
Nuke 11s new Denoise node gives inverted results compared to old Denoise.
Customer reported version
nuke.11.0v2
Customer reported platform
n_a_mac
Steps to reproduce
1) Launch Nuke 11.0v2 and read in some footage and attach the new Denoise 2 node to it.
2) Set the output from Result to Noise and you will get your inverted result.
Workaround
*This result is due to how the new denoiseer works, according to the new documentation it means the current settings are making Denoise work too hard and remove too much of the image, which leads to a soft result. So we will need to make some adjustments to compensate for this.
1) If you set the Noise Model from Modulated to Constant you will get back the original Denoise result you are familiar with from earlier releases of Nuke as well as the old denoise.
However this simply adds additional steps to the Denoise workflow compared to the previous versions of Nuke.
Reproduced by support
This bug has been reproduced in:
Nuke 11.0v3 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke 11.0v2 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke 11.0v1 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Unable to reproduce bug in:
Nuke 10.5v7 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Earliest version tested
Nuke 10.5v7
Expected behaviour
The old Denoise workflow would work as intended with Nuke11's new Denoise node. Actual behaviour
Nuke's denoise workflow has been altered making the user experience slightly different, in some cases users are unable to achieve the desired result
