Problem summary
When creating new layers within Nuke, if the user creates the new layer with their channels named as their abbreviations ( e.g test.R instead of test.red ), Nuke will create the expected channel name ( in this case test.red ), yet will keep the original channel when reading in an exported EXR.
This can cause quite a few problems, as there are now double the channels within the custom layers.
This issue only occurs with EXR files.
Customer reported version
nuke.n/a
Customer reported platform
Steps to reproduce
1) Open Nuke, Create a Colorwheel and a Shuffle node.
2) Within the Shuffle node, create a new layer:
3) Name the channels by their abbreviations ( test.R, test.G, test.B, test.A ):
Your Shuffle node should look like the following:
Your channels within your Viewer should look like the following:
Notice all the test channels are in the main area.
4) Create a Write Node under the Shuffle, set the export to EXR and channels to ALL:
5) Render the EXR image ( one frame is enough )
6) Read in the rendered EXR image
Result: The EXR will come into the Viewer not looking correct when compared to the original:
There will be double the amount of channels in the Viewer, all out of order:
The Shuffle node will be modified with all the channels, causing issues:
Expected behaviour
Nuke should use the "test.R, test.G, test.B, test.A" channels provided or modify and remove them.
Actual behaviour
The expected channels are creating, causing double the amount of channels.
Workaround
Use the expected channel names: " test.red, test.blue, test.green, test.alpha"
Reproduced by support
This bug has been reproduced in:
Nuke11.3v3- Windows 7 - Mac10.13 - CentOS7
Nuke11.3v1- Windows 7 - Mac10.13 - 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.13 - CentOS7
Earliest version tested
- This issue appears to be in all versions of the product
