Catch-up player starts from beginning when manifest transitions from 'dynamic' to 'static'
Created by: mrp1977
Environment
-
The MPD passes the DASH-IF Conformance Tool on https://conformance.dashif.org/ -
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: See below
- Dash.js version:All
- Browser name/version: All
- OS name/version:All
Steps to reproduce
- Please provide clear steps to reproduce your proble The below will give a time relevant URL which can then be used in the player.
echo "https://live.unified-streaming.com/scte35/scte35.isml/.mpd?vbegin=(((date -u +%s)-240))&vend=(((date -u +%s)+60))"
using vbegin and vend in Unified Streaming software returns a manifest between the stated periods
- If the bug is intermittent, give a rough frequency if possible no
Observed behaviour
Describe what the player is doing that is unexpected or undesired behaviour.
Adding a vbegin in the past and a vend in the future to a livestream URL when the vend reaches wallclock time and the manifest transitions from a 'dynamic' to a 'static' rather than continuing to play the stream the player stalls and then starts from the vbegin time again.
Expected behaviour - Despite manifest transition from dynamic to static content should continue playing until vend.
Manifest changes as per https://dashif.org/docs/DASH-IF-IOP-v4.3.pdf section 4.6 Examples of both static and dynamic manifests are attached.
dynamicmanifest.txt staticmanifest.txt
Console output
Paste the contents of the browser console here.
You may need to enable debug logging in dash.js by calling player.updateSettings({ 'debug': { 'logLevel': dashjs.Debug.LOG_LEVEL_DEBUG }}) if you are using your own page.