1739125 - Seeking with video.currentTime can show different frame to Chromium/ffmpeg

Status: RESOLVED DUPLICATE of bug 1735300

(Core :: Audio/Video, defect, P3)

Description

[info]

Attachment: Video frame of currentTime=53.05 shown by Firefox, Chromium and ffmpeg

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

1. Seek a video using currentTime
2. Observe the video frame that is displayed
3. Compare the result with Chromium (95.0.4638.69, Linux) and a frame capture with ffmpeg (ffmpeg -ss 00:00:53.05 -i video.mp4 -vframes 1 -q:v 2 output.jpg)

Example: https://jsfiddle.net/t6wamoue/1/

Actual results:

The shown video frame is sometimes different to the one shown in Chromium or extracted with ffmpeg.

Expected results:

The video frame should be the same in all browsers and ffmpeg.

Comment 1

[Jon Bauman [:jbauman:]]

Hey Alastor, any thoughts on this one?

Comment 2

[Alastor Wu [:alwu]]

This is same as the bug1735300. This file has negative start time (-1.1s), which seems marked ignored, but Firefox doesn't ignore those part and will start from -1.1s. When seeking to 53.05s in Firefox, this actually leads to seek to 51.95s (53.05-1.1), that is why Firefox would show the different video frame from Chrome and FFmpeg.