Closed testeur-990 closed 1 week ago
Do you see this behavior only on SmartTVs? I checked with the nightly build on MacOS Chrome and it worked fine. Also check the log outputs for Refresh manifest in
and paste them here, please.
Hello @dsilhavy ,on our side, we were able to reproduce this issue on both Smart TVs and browsers (you can easily reproduce it on Windows Chrome using you test stream). We have just found a fix for it (the mpd refresh was not handled correctly after a pause and resume in the onPlaybackStarted function). I will close this ticket.
Thank you
@testeur-990 Was this a fix you did in dash.js directly. Or in your app?
Environment
Steps to reproduce
1- Open http://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html 2-Play https://livesim2.dashif.org/livesim2/mup_30/testpic_2s/Manifest.mpd 3-Pause the stream for a significant period (with your test stream, 1 minute will be enough). 4- Resume the stream. 5- Observe the MPD refresh timings.
Observed behavior
After resuming, the manifest refresh takes around 80-90 seconds instead of 30 seconds. This causes issues with our stream, where we have minimumUpdatePeriod="PT500S". The player refreshes the MPD after a longer period (12-13 minutes) instead of the expected 8.x minutes. This delay leads to errors and freezing when the MPD is not refreshed within the expected timeframe.
Console output
Expected behavior
After resuming, the MPD should be refreshed based on the period defined by minimumUpdatePeriod. (500s In our stream and 30s in your streams