ID 330389 - Editing a channel-related knob (after its node is copied to clipboard), will affect the node within the clipboard

Follow

Problem summary
With channel-related knobs, there is a behavioural edge case, where channel selections can be unreliable if the channels in the Nuke script change when copied to the clipboard.

For example, following the reproduction steps, if you create a new channel with 3 layers (e.g red, blue, green), then copy the node to the clipboard, if you edit the channel (e.g add an alpha layer), the changes will be added to the clipboard node.

This behaviour is unexpected, the clipboard node should not contain the changes done after it was initially copied. 

 This should be addressed with more explicit channel knob serialization for consistent and predictable behaviour.

Customer reported version
nuke.n/a

Customer reported platform
n/a

Steps to reproduce

1.  Create a Remove node and a new channel layer foo, containing only red, green, and blue channels. Set the Remove node’s channels knob to this new layer.


2.  Copy the Remove node to the clipboard.


3.  Edit the foo layer to add in a foo.alpha channel.


4.  Paste the previously copied Remove node into the script. 


Result: The pasted node is now also removing foo.alpha, in spite of the fact that its state was different when it was copied to the clipboard.


Workaround
Copied node channels can also be manually disabled in nuke to not use specific channels.

It is also possible to workaround this issue by editing the '.gizmo' file after exporting, so the node’s channels knob is explicitly set to {foo.red foo.green foo.blue none}

Reproduced by support
This bug has been reproduced in:
Nuke11.1v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v4 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v7 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v9 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke8.0v7 - Windows 7 - Mac10.12 - CentOS6.9|
Nuke7.0v10 - Windows 7 - Mac10.12 - CentOS6.9

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

Expected behaviour
Editing a channel after copying the node, should not affect the node within the clipboard.

Actual behaviour
The node within the clipboard is manipulated when the original is edited.

    We're sorry to hear that

    Please tell us why