ID 469924 - Exporting Clip Length shots with Apply Retimes checked applies retimes when it shouldn't

Follow

Problem summary
Exporting Clip Length shots with Apply Retimes checked applies retimes when it shouldn't


Customer reported version
Nuke Studio 12.2v4


Customer reported platform

CentOS 7


Steps to reproduce


1) Open Nuke Studio and import a image sequence

2) Add the sequence to the timeline

3) Right click the clip > Editorial> Retime...


4) Set the rate to 60% and press OK


5) Right click the clip > Export...


6) In the Export dialog, 

  • Reset the presets, 
  • Select the Transcode Shots DPX, 
  • Change the Handles to Clip Length
  • Press Export


7) Right click the clip > Build Track> From Export Tag then press Build


8) Scrub through the timeline comparing both tracks, they look the same.


9) Right click the original clip > Tags > Clear Tags


9) Right click the original clip > Export...


10) In the Export dialog, Reset the presets, then select the Transcode Shots DPX, change the shot path to something different, check Apply Retimes, then change the Handles to Clip Length and press Export

  • Reset the presets, 
  • Select the Transcode Shots DPX, 
  • Change the shot path to something different like {shot}_002
  • Check Apply Retimes
  • Change the Handles to Clip Length
  • Press Export


11) Right click the original clip > Build Track> From Export Tag then press Build


12) Scrub through the timeline comparing both tracks, they look like different frames 




Expected behaviour
For toggling a greyed out option to make no difference between exports


Actual behaviour
It changed how the clip exported, making it incorrect


Workaround
Don't have Apply Retimes checked when exporting Clip Length Handles


Reproduced by support

This bug has been reproduced in:
Nuke Studio 12.2v5 - Windows 10, Centos 7.8

Nuke Studio 12.2v1 - Windows 10

Nuke Studio 12.0v1 - Windows 10

Nuke Studio 11.0v1 - Windows 10

Nuke Studio 10.0v1 - Windows 10, Centos 7.8


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

    We're sorry to hear that

    Please tell us why