ID 510112 - Calling mediaSource().startTime() via Python returns an incorrect value for MOVs

Problem summary
Calling mediaSource().startTime() via Python returns an incorrect value for MOVs.
 
Customer reported version
hiero.n/a
 
Customer reported platform
 
Steps to reproduce
1) In Nuke Studio/Hiero, import a .mov file.
2) Drag/drop the imported footage to the Timeline to create a sequence.
3) Select the clip on the Timeline, then open the Script Editor and run the code:

ti = hiero.ui.getTimelineEditor(hiero.ui.activeSequence()).getSelection()[0] print(ti.source().mediaSource().startTime())

4) View the result for the start time of the selected clip.
 
Expected behavior
The start time of the clip should be accurate.
 
Actual behavior
The start time reads as 0 when running mediaSource.startTime() in the Script Editor.
 
Workaround
There is no available workaround at this time.
 
Reproduced by Support in:
Nuke Studio 13.2v1 - Windows 10, CentOS 7
Nuke Studio 13.1v1 - Windows 10
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10
Nuke Studio 9.0v1 - Windows 10, CentOS 7
 
Earliest version tested
Nuke Studio/Hiero 9.0v1 - This issue appears to be in all versions of the product (although the actual metadata for startTime does not appear until 13.0v1)