Live MPD declares no minimumUpdatePeriod
Players are told the manifest never changes, so they never discover new segments.
What it means
A dynamic MPD normally declares @minimumUpdatePeriod, telling players how often to re-fetch it. It is absent.
Why it matters
Without it, a player fetches the manifest once and works only from the segments listed at that moment. When those run out, playback stops — typically a minute or so in, which makes it look like a network problem rather than a manifest one.
How to fix it
- Add minimumUpdatePeriod to <MPD>, usually around one segment duration, for example PT2S.
- A manifest using SegmentTemplate with $Number$ and a fixed duration can sometimes omit it, but declaring it is safer across players.
Check your own stream
The free DASH validator runs this check on every analysis and links each finding straight back here.
Open the DASH validator →Frequently asked questions
- What does "Live MPD declares no minimumUpdatePeriod" mean?
- A dynamic MPD normally declares @minimumUpdatePeriod, telling players how often to re-fetch it. It is absent.
- Why does it matter?
- Without it, a player fetches the manifest once and works only from the segments listed at that moment. When those run out, playback stops — typically a minute or so in, which makes it look like a network problem rather than a manifest one.
- How do I fix it?
- 1. Add minimumUpdatePeriod to <MPD>, usually around one segment duration, for example PT2S. 2. A manifest using SegmentTemplate with $Number$ and a fixed duration can sometimes omit it, but declaring it is safer across players.
- Can a validator catch this before viewers do?
- Yes. The free DASH MPD validator checks this on every run, together with UTCTiming, clock drift and segment addressing — the live problems that only appear on other people's devices.
- What is the first thing to try?
- Add minimumUpdatePeriod to <MPD>, usually around one segment duration, for example PT2S.
Related DASH checks
- DASH manifest has no UTCTiming elementA live MPD without UTCTiming forces players to trust the device clock, so any skew on the viewer’s machine becomes stalls or missing segments.
- DASH availabilityStartTime is in the futureThe manifest claims the presentation starts later than the current time, so no segment is available yet and playback cannot begin.
- The DASH manifest is not well-formed XMLThe document could not be parsed as XML, so nothing else could be checked.
- The document has no MPD root elementThe XML parsed, but its root is not <MPD>, so it is not a DASH manifest.
- MPD declares no profileWithout @profiles a player cannot tell which DASH feature set the manifest expects.
- MPD declares no minBufferTimePlayers use this required attribute to size the initial buffer before starting playback.