ID 234851 - Soft Effects Timewarp in a transcode, will export incorrectly, if hotkeys Shift+Cmd+E are used to bring up the export dialogue using a custom preset

Follow

Problem summary

Soft Effects Timewarp exports incorrectly, if hotkeys Shift+Cmd+E 
are used to bring up the export dialogue, which is using a custom preset.
Timewarp node will be in the wrong place in the nuke script

 

Customer reported version
10.0v2

 

Customer reported platform

Windows8.1

 

Steps to reproduce

Un-zip retime_issue.zip
 
1) Open project retime_issue.hrox and do Clips> Reconnect Media
2) Rt-click Sequence in Project Bin and  from pulldown menu, choose Export
3) Drag custom preset,  test_transcode_JPEG.xml , into 'Using Project export preset' 
3) In export dialogue, choose the custom preset
5) Export 
6) In Compositing Workspace, File>Open Comp (from 'Keep Nuke Script') and AOK
 
NOTE: Soft Effects are correct, i.e. Text nodes and Timewarp are in the correct place, after Append Clip node
for the appropriate Clips
 

 

7) Go back to Timeline and select all Clips in Timeline
8) Hit hotkeys Shift+Cmd+E  to bring up export dialogue
9) Export using the same preset as before 
10) Open the nuke script and see that the Timewarp and Text nodes
are in the wrong place.

 

Workaround
Unknown

 

Reproduced by support
9.0v1-10.0v4

MacOS 10.10.2

 

Expected behaviour

Nuke Scripts with Soft Effects Timewarp should be the same, whether the Sequence
transcode export was initiated by using Project Bin>Sequence>Export pulldown menu
or by using hotkeys Shift+Cmd+E

 

Actual behaviour

When using the same custom preset, nuke scripts generated by a Sequence
transcode export with custom preset are different. The nodes for Soft Effects>Timewarp 
differently in the transcode script and the nuke script is incorrect.
 

1.
NOTE:  The difference in nuke script generated by a transcode export using
a custom preset, the bug was NOT reproduced when using, for example, the default
Photo - JPEG MOV preset. 
2.
NOTE: The BUG requires that a custom preset be used and in the reported case, the format
was Content> File Type jpeg sequential frames and Retime Method Frame
3.
If there are any problems reproducing this BUG, the customer has provided
a very good screen recording which captures the steps-to-reproduce. It is also contained in the zip archive,
FoundryRetimeTicket.mp4

    We're sorry to hear that

    Please tell us why