ID 148656 - Merge - Mask/Stencil operation does not work on non-RGBA channels

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
When using the Stencil and Mask Merge node options, if the 'also merge' knob is set to 'all' the other channels will not be masked/stencilled.

This can cause issues downstream, where the user expects other channels to also be masked/stencilled.


From further investigation, this issue does not affect the legacy Merge node's mask/stencil options.


Customer reported version
nuke.11.1v2


Customer reported platform
windows10


Steps to reproduce


1) Open Nuke, create a ColorWheel and Checkerboard node

2) Create a ShuffleCopy node and attach both nodes.


3) Within the ShuffleCopy, create a new channel for the 2nd input:

​

​

3) Create two Merge nodes, set one to 'Mask' and the other to 'Stencil'


4) Create a Roto node and create a RotoShape


5) Attach the ShuffleCopy node to both Merge node's B input:

​

​


6) Within both Merge nodes, set the 'Also Merge' nodes to 'ALL'


7) Switch between the 'RGBA' channel and your added channel.


Result: The RGBA channel will be masked/stencilled, while the other channel will have no change:

​

​


Expected behaviour
When 'Also merge' is set to 'ALL', all the channels should be masked/stencilled.


Actual behaviour
When 'Also merge' is set to 'ALL', only RGBA is affected.


Workaround
The legacy Merge node provides the expected behaviour.


It can be accessed by Node Toolbar -> Other -> All Plugins -> Update to add the legacy Merge to the Tab menu.


Alternatively, you can add the following Python snippet to your .nuke/menu.py location to add a workaround on the toolbar:

merge_workaround = nuke.toolbar( 'Nodes' )
merge_workaround.addMenu("merge_workaround", "Merge.png")

merge_workaround.addCommand("merge_workaround/Stencil", "nuke.createNode('Merge', 'operation stencil')", icon = "MergeOut.png")
merge_workaround.addCommand("merge_workaround/Mask", "nuke.createNode('Merge', 'operation mask')", icon = "MergeIn.png")

​

​


Reproduced by support


This bug has been reproduced in:

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
Nuke10.5v1 - Windows 7
Nuke10.0v1 - Windows 7
Nuke9.0v1 - Windows 7
Nuke8.0v1 - Windows 7 - Mac10.14 - CentOS7


Earliest version tested
- This issue appears to be in all versions of the product

    We're sorry to hear that

    Please tell us why