On playing particular ISO-BMFF stream with Media Source Extension, playback gets stuck.
Reported by
saushar...@gmail.com,
Dec 20 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Open DASHIF player hosted on http://dashif.org/reference/players/javascript/v1.6.0/samples/dash-if-reference-player/index.html 2. In the stream field, put the content url http://de9b7h88wgj5l.cloudfront.net/static/apurva/browserBug/test.mpd 3. install CORS plugin and enable it. 4. Click on load and observe that playback gets stuck around 10 second while video duration is 22 seconds. And also buffered range is from 0 - 21.6 seconds. What is the expected behavior? playback should not stuck. What went wrong? playback got stuck. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 55.0.2883.87 Channel: stable OS Version: Windows 7 Enterprise ServicePack1, 64 bit OS Flash Version: Shockwave Flash 24.0 r0.186 works fine on firefox.
,
Dec 21 2016
,
Dec 21 2016
,
Dec 21 2016
tl;dr:
sausharm16@: please try with a beta (M56) version of Chrome to confirm this was fixed in M56.
Details:
sausharm16@: What is the CORS plugin referred to in step 3? Is it required? Without it, I obtained what looks like a repro (audio-only media, audio plays then stalls around 10 seconds) on Chrome 55.0.2883.87 (Official Build) (64-bit) on linux.
chrome://media-internals indicates a highly correlated debug message:
00:00:00 928 debug Generated splice of overlap duration 1999us into new buffer at 10814000us.
After stall:
$('video')[0].buffered.length is 1, [0-21.608666]
$('video')[0].currentTime is 10.706304
On current trunk (should also work on M56), **no repro**. chrome://media-internals shows instead:
00:00:02 369 debug Audio buffer splice at PTS=10814000us. Trimmed tail of overlapped buffer (PTS=10794666us) by 1999us.
It looks like this is fixed by chcunningham@'s removal of splice cross-fading (which had problems with media whose timestamps in the container (ISO-BMFF) didn't align just right with the framerate * # of frames decoded.
Assigning to chcunningham@ in case there's any further follow-up necessary on his return.
,
Dec 21 2016
(Suspected to have been fixed by https://codereview.chromium.org/2343543002/)
,
Jan 10 2017
Verified fixed in Canary. sausharm16@gmail.com, yell if you still observe this issue at/after version 56. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mcasas@chromium.org
, Dec 20 2016