libx264 vs h264_qsv encoded media issues with bif files

[Happy2Play 8237]

I recently noticed that anything that I have encoded/re-encoded with h264_qsv will have bif files that do not match the media duration.  So episode bif files will be about 2 minute short and movie 3-5 minutes short.
 
But if this media is encoded with libx264 or h264 the bif files match the duration.
 
An example image of bif ending early and creates seek issue (some discussion in other topic)

 
h264_qsv encode of Lost in Space (2018).S01E05.Transmission.mp4 the bif is missing 2 minutes so it can not seek the last two minute as shown here. (281 images extracted)

• elapsed=00:01:33.69 frame= 281 fps=3.0 q=1.6 Lsize= 2502kB time=00:46:50.00 bitrate= 7.3kbits/s dup=0 drop=1 throttle=off speed= 30x

But that same episode encoded with libx264 or h264 will create a bif file that can seek to the end. (294 images extracted) (13 more frames so the missing 2 minutes)

• elapsed=00:00:03.34 frame= 294 fps= 88 q=1.6 Lsize= 2565kB time=00:49:00.00 bitrate= 7.1kbits/s dup=0 drop=1 throttle=off speed= 879x

 

Anyone else see this behavior or any idea why this would happen? 

Edited July 10, 2019 by Happy2Play

[Luke 36997]

Do media players show the correct runtime for the file?

[Happy2Play 8237]

Do media players show the correct runtime for the file?

 

We have this discussion in dev section but trying to see if anyone else sees this issue also of if it is just me.

 

But duration is correct in all players.

For the example above duration 00:48:59.

[Happy2Play 8237]

I only have a Roku so don't know if this seek issue happens on other clients.  I know I don't see the seek in in the web client just interval images offset.

[Luke 36997]

I just mean in general like windows media player, vlc, etc.

[Happy2Play 8237]

I just mean in general like windows media player, vlc, etc.

 

WMP, VLC, MPC-HC, Win10 Movies & TV all show 48:59 for duration.