ID 520618 - Adding a Shuffle node as an Additional Node to a Nuke Studio export makes the export fail to render

Follow

Problem summary
Adding a Shuffle node as an Additional Node to a Nuke Studio export makes the export fail to render
 
It adds xpos and ypos outside of any curly braces {}, causing the Nuke script to be invalid
 
Customer reported version
 
Customer reported platform
windows10
 
Steps to reproduce
 
1) Open Nuke Studio

2) Import the attached multilayerExample.exr file and add it to a timeline

3) Select the shot on the timeline, right click> Export...
 
4) Select the Transcode Shots DPX default preset, then in the Transcode Images content, enable Additional Nodes and press Edit
 
5) Press + to add an extra node, then paste the below Shuffle node:
 

add_layer {layer1 layer1.red layer1.green layer1.blue layer1.alpha}Shuffle2 { fromInput1 {{0} B} in1 layer1 fromInput2 {{0} B} mappings "4 layer1.red 0 0 rgba.red 0 0 layer1.green 0 1 rgba.green 0 1 layer1.blue 0 2 rgba.blue 0 2 layer1.alpha 0 3 rgba.alpha 0 3" name Shuffle1 selected true xpos 263 ypos 44}
 
6) Press OK, then Export, the export will fail nd in the error log say:
 
Task 'TranscodeExporter' reported errors: b'M:/temp/046/006/multilayerExample/multilayerExample.nk:\nxpos: Unknown command\nypos: Unknown command'

 
* If you remove add_layer {layer1 layer1.red layer1.green layer1.blue layer1.alpha} from the Additional Nodes, then Nuke Studio will export, however the render is black as the layer is not correctly defined. 
 
Expected behaviour
For frames to be rendered, with the layer1 channel shuffled into RGB
 
Actual behaviour
It errors during export
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.2v4 - Windows 10, CentOS 7
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 10.5v8 - Windows 10, CentOS 7 - *regression 
 
Unable to reproduce bug in:
Nuke Studio 10.0v6 - Windows 10, CentOS 7
 
Earliest version tested
Nuke Studio 10.0v6 - This issue doesn't appear in this version and has regressed between 10.5v8 and 10.0v6
 

    We're sorry to hear that

    Please tell us why