Problem summary:
When selecting 'Version Up' in a clip in the Project Bin, then selecting 'Rescan Clip Range', the Original Range fails to update to the correct frames.
Customer reported version:
nuke.10.5v1
Customer reported platform:
centos6
Steps to reproduce:
1) Create a project with v01 and v02 rendered clips where v01 is shorter and trimmed at each end (e.g. v01 is frames 1-100, and v02 is 10-90); example:
2) In a new Nuke Studio/Hiero session, import clip v01 and note the clip range and start frame in the Bin.
3) In the Project Bin select the clip and select Version > Version Up; version v02 loads and the clip length is 100f and the start frame is 1.
4) select the clip and do Clip > Rescan Clip Range.
5) Observe the output of the Original Range in the Properties bin of the clip item.
Workaround:
Import each version separately to show it's correct range and start frame. Alternatively, set the Original Range to the correct frames in the input field for each clip.
Reproduced by support:
Nuke Studio 13.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra
Nuke Studio 12.2v1 - Windows 10
Nuke Studio 12.1v1 - Windows 10
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.1v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10
Nuke Studio 9.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra
Expected behavior:
The clip for v02 would show the correct range and start frame either as a result of 'Version Up' or from the Rescan Clip Range/Rescan button in the Properties bin.
Actual behavior:
The clip for v02 in the Project Bin displays an incorrect Original Range of frames and gives an error until corrected manually.
