A DASH period contains no adaptation sets
A period declares no media, so playback stalls when the timeline reaches it.
What it means
One or more <Period> elements contain no <AdaptationSet>, so they describe a stretch of time with nothing in it.
Why it matters
When playback reaches an empty period the player has nothing to fetch. Behaviour varies from a silent gap to a hard stop. In ad-insertion workflows this is the classic signature of an ad decision that returned nothing but still left its period behind.
How to fix it
- Remove the empty period, or fill it with the content it was meant to hold.
- In server-side ad insertion, make sure the stitcher drops the period when no ad is returned rather than emitting an empty one.
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 "A DASH period contains no adaptation sets" mean?
- One or more <Period> elements contain no <AdaptationSet>, so they describe a stretch of time with nothing in it.
- Why does it matter?
- When playback reaches an empty period the player has nothing to fetch. Behaviour varies from a silent gap to a hard stop. In ad-insertion workflows this is the classic signature of an ad decision that returned nothing but still left its period behind.
- How do I fix it?
- 1. Remove the empty period, or fill it with the content it was meant to hold. 2. In server-side ad insertion, make sure the stitcher drops the period when no ad is returned rather than emitting an empty one.
- How can I detect this automatically?
- Paste your MPEG-DASH streaming URL into StreamTest's free DASH validator. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
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.