Problem summary
When exporting a shot from Nuke Studio (to work on in Nuke), it is possible to include any other clips that overlap the selected clip in the timeline by selecting the 'Collate Shot Timings' option in the 'Nuke Project File' export options.
When exported, if a collated clip extends past the selected clip (eg. sh020 below), the exported Nuke script will accommodate for this by increasing the duration of the script to match the end frame of this collated clip.
It has discovered that when you attempt to rebuild a new comp layer from this exported Nuke script, there will be an offset in the rebuilt result and blank frames at the end.
Customer reported version
nuke.12.2v4
Customer reported platform
windows10
Steps to reproduce
1) Create a new Nuke Studio project and import two separate clips into two tracks
2) Shorten and duplicate the clip on the lower track, to create an overlap in the top clip between the two lower clips (see image above)
3) Right-click on the top clip and select 'Export'
4) Within the Export menu, select the 'Basic Nuke Shot' and ensure that 'all tracks' is selected as well as the the 'Collate Shot Timings' option (in the Nuke Project File context)
5) Once exported, right-click on the top clip again, and select 'Build Track > from export structure' selecting 'Basic Nuke Shot' for the rebuild.
6) When the new comp layer is generated, right-click on the layer and select 'Render Comp' to render the comp to the timeline. Result: There will be an offset to the comp layer from the original top clip and black at the end of the comp.
Expected behaviour
When a shot is exported with collated clips, when rebuild the original clip should still match the original footage
Actual behaviour
When the clip is rebuild after being exported, there is an offset caused by the new script duration.
Workaround
We would suggest to avoid having overhang between clips when collating is selected in the export settings, as this changes the script duration which leads to the issue.
Reproduced by support
This bug has been reproduced in:
Nuke Studio 12.2v5 - Windows 10 - CentOS 7 - MacOS 10.15.6
Nuke Studio 12.2v1 - Windows 10
Nuke Studio 12.1v1 - Windows 10
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.3v1 - Windows 10
Nuke Studio 11.2v1 - Windows 10
Nuke Studio 11.1v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.5v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10
Nuke Studio 9.0v1 - Windows 10 - CentOS 7 - MacOS
Earliest version tested
Nuke Studio 9.0v1
- This issue appears to be in all versions of the product
