ID 552066 - Nuke Studio/Hiero reads H.264 files with an incorrect frame range

Problem summary
Nuke Studio/Hiero reads H.264 files with an incorrect frame range.
 
Customer reported version
N/A
 
Customer reported platform
 
Steps to reproduce
 
1) Open Hiero/Nuke Studio.
 
2) Import the attached files (File > Import File(s)...).
 
3) Drop the files on to the timeline, and notice that some frames at the end of the shot are displayed in red (missing frames).
 
Expected behaviour
Nuke Studio/Hiero should read the files in with the correct frame range. 
 
Actual behaviour
It appears that Nuke Studio/Hiero is reading the files with additional frame numbers for the origLast knob, which is causing the missing frames.
 
Workaround
Clicking the Rescan button in the clip's Properties should correctly update the frame range. This can also be done via a kClipAdded callback, like with the example code below:

import nukefrom hiero.core import eventsdef rescanClipRange(event):    clip = event.clip    media_src = clip.mediaSource()    if media_src.hasVideo() and media_src.filename().endswith('.mp4'):        event.clip.rescan()events.registerInterest("kClipAdded", rescanClipRange)

 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 14.0v5 - Windows 10 - Linux CentOS 7
Nuke Studio 13.2v1 - Windows 10 
Nuke Studio 13.1v1 - Windows 10
Nuke Studio 13.0v10 - Windows 10
Nuke Studio 13.0v9 - Windows 10
Nuke Studio 13.0v8 - Windows 10
Nuke Studio 13.0v7 - Windows 10
Nuke Studio 13.0v6 - Windows 10
Nuke Studio 13.0v5 - Windows 10
Nuke Studio 13.0v4 - Windows 10
Nuke Studio 13.0v3 - Windows 10 - Linux CentOS 7 - REGRESSION
 
Unable to reproduce bug in:
Nuke Studio 13.0v2 - Windows 10 - Linux CentOS 7
 
Earliest version tested
Nuke Studio 13.0v2
- This issue doesn't appear in this version and has regressed