ID 434757 - Annotations exported from Nuke Studio with retime applied does not correctly interpret OFlow node in Nuke script

Follow

Problem summary
When exporting a retimed clip from Nuke Studio to create a new comp container, if the export preset contains a 'Nuke Annotation File' and the 'Apply Retimes' checkbox is selected, the retime from the clip will create the following error in the Nuke script on load.



This error appears to be in relation to the Annotations Precomp node that is embedded in the exported Nuke script, and the way it handles the OFlow node.

From testing this issue occurs in Nuke 11.3v2 releases and later, and the error message occurs when this script is loaded in either Nuke Studio as a comp container or the Nuke script itself.


Customer reported version
nuke.n/a

Customer reported platform

Steps to reproduce

1) Open a new Nuke Studio session

2) Import footage and create this as a clip in a new sequence, in the timeline.

3) Within the timeline clip, retime the clip to 50% by right-clicking the clip and selecting 'Editorial/Retime'

4) Once retimed, right-click on the clip again, and select 'Effects/Create Comp Special...'

5) Within the 'Create Comp' window, select the 'Basic Nuke Shot with Annotations' export preset, and ensure that the 'Apply Retimes' checkbox is on, then 'Create Comp'

6) When the new layer appears in the timeline, double click to open the Comp container
Result: You will get the above stated error.

Expected behaviour
A retime added to an annotation within Nuke Studio should not cause an error when opened in Nuke.

Actual behaviour
When a retime is added to an annotation within Nuke Studio, the above error occurs within the Nuke script.

Workaround
The most efficient way to resolve this issue from testing was to open the Annotations Precomp and save the script, which removes the error happening again.

Reproduced by support
This bug has been reproduced in:
Nuke 12.1v2 - Windows 10
Nuke 12.1v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.3v2 - Windows 10 - regression

Unable to reproduce bug in:
Nuke 11.3v1 - Windows 10

Earliest version tested
Nuke 11.3v1
- This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why