ID 510750 - TrackItem handle Length and handle time Python commands return incorrect values when a TimeWarp soft effect is added to a clip

Problem summary
TrackItem handle Length and handle time Python commands return incorrect values when a TimeWarp soft effect is added to a clip
 
Customer reported version
hiero.12.2v9
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Open Nuke Studio

2) Import some footage and add it to the timeline

3) Trim the head and tail of the clip, so it handles at the front and back of the clip:
 

 
4) Select the clip, and run the following Python code in the Script Editor:
 

selection = hiero.ui.getTimelineEditor(hiero.ui.activeSequence()).selection()[0]print("Original timelineIn: " + str(selection.timelineIn()))print("Original timelineOut: " + str(selection.timelineOut()))print("Original sourceIn: " + str(selection.sourceIn()))print("Original sourceOut: " + str(selection.sourceOut()))print("Original handleInTime: " + str(selection.handleInTime()))print("Original handleOutTime: " + str(selection.handleOutTime()))print("Original handleInLength: " + str(selection.handleInLength()))print("Original handleOutLength: " + str(selection.handleOutLength()))selection.parentTrack().createEffect("TimeWarp", trackItem=selection)print("After Timewarp timelineIn: " + str(selection.timelineIn()))print("After Timewarp timelineOut: " + str(selection.timelineOut()))print("After Timewarp sourceIn: " + str(selection.sourceIn()))print("After Timewarp sourceOut: " + str(selection.sourceOut()))print("After Timewarp handleInTime: " + str(selection.handleInTime()))print("After Timewarp handleOutTime: " + str(selection.handleOutTime()))print("After Timewarp handleInLength: " + str(selection.handleInLength()))print("After Timewarp handleOutLength: " + str(selection.handleOutLength()))

 
Expected behaviour
The handleInTime(), handleOutTime(), handleInLength() and handleOutLength() should return sensible values.
 
Actual behaviour
The return incorrect values after adding a TimeWarp:
 
# Result: 
Original timelineIn: 10 
Original timelineOut: 43 
Original sourceIn: 25.0 
Original sourceOut: 58.0 
Original handleInTime: -15 
Original handleOutTime: 84 
Original handleInLength: 25 
Original handleOutLength: 41 
 
After Timewarp timelineIn: 10 
After Timewarp timelineOut: 43 
After Timewarp sourceIn: 25.0 
After Timewarp sourceOut: 58.0 
After Timewarp handleInTime: 0 
After Timewarp handleOutTime: 9223372036854775806 
After Timewarp handleInLength: 10 
After Timewarp handleOutLength: 9223372036854775763
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.2v2 - Windows 10, CentOS 7, macOS Monterrey
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10
Nuke Studio 9.0v9 - Windows 10 - regression somewhere in 9.0
 
Unable to reproduce bug in:
Nuke Studio 9.0v1 - Windows 10
 
Earliest version tested
Nuke Studio 9.0v1 - This issue doesn't appear in this version and has regressed somewhere in the Nuke Studio 9.0 series