Scrub-bar and timeline does not change to VoD as livesim MPD transitions from dynamic to static

[tobbee]

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:
• https://livesim2.dashif.org/livesim2/startrel_-20/stoprel_6/testpic_2s/Manifest.mpd
• Dash.js version: 4.7.2
• Browser name/version: Safari 17.0
• OS name/version: Mac OS Sonoma 14.0

Steps to reproduce

1.Run reference player with the provided link. Turn off loop sequence

Observed behavior

2. The initial MPD is dynamic with location
   with absolute times and an availabilityStartTime 20s ago.
   The total asset should be a live asset of duration 26s after which it becomes a static VoD.
   The last segment loaded should be 12.m4s
3. The player starts at around 12s from the start and downloads segment until there are
   no more (may end at 23.29 which may be a rounding issue in livesim2).
4. The player stops after 13 segments with video showing time 00:00:25:29,
   but the "scrubbar type" still says "live" and the scrubber is not change to go from 0 to duration
5. If loop is turned on, the asset loops, but doesn't follow the location, it seems.

Expected behavior

Since the asset transits from being dynamic (live) to static (VoD), I expect the scrub-bar to do the same.
The timeline should also switch from 0-26.
If looping, it is the static MPD that should be looped.

Related to issue #4271.

[dsilhavy]

Partially fixed in #4314. While the controlbar behaves fine now, the looping still fails. This is probably because we ignore the last MPD update in the current dynamic to static transition workflow.

[dsilhavy]

Moved the second issue as explained above to version 5.1.0 as it probably involves additional changes to the dynamic to static processing workflow of dash.js

As a workaround content can easily be looped by attaching the same MPD URL again (in case the content is available as static MPD)