ID 459683 - Applying a BurnIn to a retimed clip, then exporting the shot, results in the BurnIn being incorrect in the exported script

Problem summary
Applying a BurnIn to a retimed clip, then exporting the shot, results in the BurnIn being incorrect in the exported script.

Customer reported version
Nuke Studio 12.1v2

Customer reported platform
CentOS 7

Steps to reproduce

1) Open Nuke Studio and import a clip into your project.

2) Drag the clip into the Timeline to add it to a Sequence.

3) Apply a Retime on the clip (right click > Editorial > Retime...). 

4) In the dialog that appears, enter a value of 200 in the Rate (%) field and press OK.

5) Apply a BurnIn to the Retimed clip (right click > Effects > Burn-In).

6) In the BurnIn control panel, select input/frame from one of the dropdown menus.

7) Export the clip (right click > Export).

8) In the Export dialog, select Process as shots and the Basic Nuke Shot preset. Ensure that the Apply Retimes option is checked, and click Export.

9) Open the exported .nk script in the Node Graph and view the result. Notice that the input/frame value does not match the value of the corresponding frame in the Timeline Viewer.
The following image shows the difference between the Timeline Viewer (left) and the Comp Viewer (right). The input/frame value is displayed on the top left of each Viewer:

​​

​

Expected behaviour
The BurnIn inside the .nk script should match the BurnIn values from the Timeline. 
Swapping the order of the OFlow and BurnIn nodes in the .nk script seems to produce the expected result:

​​

Actual behaviour
The Retime is not applied to the BurnIn inside the .nk script. This seems to be because the OFlow is applied before the BurnIn node:

​

Workaround
In your Export settings, first check Apply Retimes, and uncheck Include Effects.
Then check Additional Nodes and press the Edit button. In the dialog that appears, add a BurnIn node, like so:

​  

When the script is exported, the BurnIn node should then be applied before the OFlow.

Reproduced by support
This bug has been reproduced in:
Nuke Studio 12.2v3 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 7
Nuke Studio 12.0v1 - Windows 10

Nuke Studio 11.0v1 - Windows 10

Nuke Studio 10.0v1 - Windows 10

Nuke Studio 9.0v1 - Windows 10 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke Studio 9.0v1
- This issue appears to be in all versions of the product