No segment found at index: XXX. Wait for next loop - issue with live streams using dashjs 2.6.0
Created by: tomraut
Environment
-
The MPD passes the DASH-IF Conformance Tool on http://dashif.org/conformance.html -
The stream has correct Access-Control-Allow-Origin headers (CORS) -
There are no network errors such as 404s in the browser console when trying to play the stream -
The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ -
The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page
- Link to playable MPD file: https://mtvdashliveusp2-a.akamaized.net/live/E1USP/E1USP.isml/E1USP.mpd
- Dash.js version: 2.6.0 (NOTE: same stream works correctly with dashjs 2.5.0)
- Browser name/version: Chrome 60.x
- OS name/version: OSX 10.12.6
Steps to reproduce
- Start playback of the stream.
- Let it roll.
Observed behaviour
Stream plays fine for 1-5 seconds and then freezes.
Console output
When dash debug logging is turned on, following information appears in the browser's console:
[247121] ScheduleController - getNextFragment
[247123] Getting the request for audio time : 1506072349.2
[247125] Index for audio time 1506072349.2 is 448
[247127] SegmentTimeline: 1506072347.1946666 / Infinity
[247129] Getting the next request at index: 449
[247131] No segment found at index: 449. Wait for next loop
[247133] getNextFragment - Playing at the bleeding live edge and frag is not available yet
[247406] ThroughputRule requesting switch to index: 5 type: video Average throughput 41731 kbps
[247410] AbrController (video) stay on 0/5 (buffer: 1.068)At the moment we are using dashjs version 2.5.0 and same stream works correctly with it. I suspect that perhaps https://github.com/Dash-Industry-Forum/dash.js/pull/1991 has something to do with this being broken in dashjs 2.6.0.