MPD Anchors (#t) broken in 2.6 for live streams
Created by: davemevans
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://vm2.dashif.org/livesim/testpic_2s/Manifest.mpd
- Dash.js version: 2.6.x
- Browser name/version: Chrome 61
- OS name/version: Win7
Steps to reproduce
Add a #t=<seconds since start of period> anchor to end of of dynamic manifest URL and load.
I built two simple examples which include an MPD anchor set roughly two minutes behind the live edge. The 2.5.0 example works correctly and the stream starts at the anchor time. The 2.6.0 example does not work correctly, starting at the live edge.
Observed behaviour
Player starts at live edge rather than at time specified by anchor.
Note that static MPDs appear to play correctly (eg http://rdmedia.bbc.co.uk/dash/ondemand/testcard/1/client_manifest-events.mpd#t=30)
It looks like https://github.com/Dash-Industry-Forum/dash.js/pull/2194 ought to make this work, but it's not doing the trick in this case.