Closed
Bug 1292056
Opened 9 years ago
Closed 9 years ago
MSE base profile and main profile - big gap between 2 segments - not reproduced on Chrome
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: itay.kinnrot, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Steps to reproduce:
Make sure CORS header plugin is enabled and on, use this link:
http://dailymotion.github.io/hls.js/demo/?src=http%3A%2F%2Flbd.kaltura.com%2Fitay%2Findex.m3u8&enableStreaming=true&autoRecoverError=true&enableWorker=true&levelCapping=-1&defaultAudioCodec=undefined
Actual results:
The stream includes 2 ts files - one which includes base profile h264 and the 2nd one main profile - you can see there is 0.4s gap between them on the video source buffer
if you'll open the same link on any other browser - this gap is not there.
Expected results:
the stream should be smooth
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
Summary: media source extension base profile and main profile - big gap between 2 segments - not reproduced on chrome → MSE base profile and main profile - big gap between 2 segments - not reproduced on Chrome
|
||
Comment 1•9 years ago
|
||
the gap is there, but both Chrome and Edge incorrectly calculate their buffered range and are in the process in fixing their bug on this matter. Once they finally do, you'll see the gap everywhere.
Edge will skip gap over 1s long.
We only allow up to 125m large gap
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•