Streaming error reference

A variant claims its average bitrate is higher than its peak, which cannot be true and misleads ABR.

Without this tag players must assume segments depend on each other, so seeking and switching are more conservative.

This tag is required on every media playlist, and players use it to size buffers and set the reload interval.

The playlist uses tags that require a higher version than it declares, and compliant players may reject it.

A segment declares an encryption method but no key location, so it cannot be decrypted.

A lower-resolution variant is allocated more bandwidth than a higher-resolution one, so adaptive switching picks the wrong rendition.

Two variants are indistinguishable — same resolution, codec, dynamic range and bitrate — so one is wasted.

Adjacent renditions are too far apart, so switching between them is a visible jump in quality.

The newest segment’s program date-time is far from the current time, meaning the playlist is stale or the clocks disagree.

The playlist holds too little content, so any player that falls slightly behind runs off the end of the window.

With a single variant there is nothing to adapt to, so viewers on poor connections rebuffer instead of dropping quality.

The playlist parsed correctly but lists nothing to play.

A segment is declared missing, so playback will skip that period.

Frequent EXT-X-DISCONTINUITY tags mean the timeline resets constantly, which many players handle poorly.

Without program date-time the stream cannot be mapped to wall-clock time, which breaks DVR seeking and multi-stream alignment.

More than one encryption method appears in a single playlist, which many players do not handle.

A segment claims an earlier wall-clock time than the one before it, which corrupts seeking and subtitle alignment.

A group has no DEFAULT rendition, or more than one, so which track plays at start-up is left to the player.

Without a language tag, players cannot honour the viewer’s language preference.

Inconsistent segment lengths make buffer estimation and ABR switching erratic.

A segment rounds to more than the declared target duration, which violates the HLS specification.

Devices that cannot handle high frame rates need this attribute to rule a rendition out before downloading it.

Without CODECS, players must download a segment before they can tell whether they can play the rendition at all.

Without RESOLUTION a player cannot avoid downloading a rendition larger than the screen can show.

A variant points at an AUDIO or SUBTITLES group that has no matching EXT-X-MEDIA entry, which breaks playback on strict players.

The declared PART-HOLD-BACK is smaller than three times PART-TARGET, so players chase a live edge they cannot reach.

Partial segments are not meaningfully smaller than whole segments, so low latency achieves nothing.

Without blocking reload, players must poll for updates and the latency benefit is lost.

The document does not begin with #EXTM3U, so it is not a playlist at all.

The playlist says it is VOD but never says it has finished, so players keep polling for updates that never come.

A period declares no media, so playback stalls when the timeline reaches it.

Without SegmentTemplate, SegmentList, SegmentBase or BaseURL, players cannot construct segment URLs.

Players cannot assume segments line up across representations, so bitrate switching is not clean.

Representations in one set must be seamlessly switchable, so different codecs belong in separate sets.

Without @lang, players cannot honour the viewer’s language preference.

A ContentProtection element names a scheme we do not recognise, so the required DRM system cannot be confirmed.

The manifest claims the presentation starts later than the current time, so no segment is available yet and playback cannot begin.

A live MPD without UTCTiming forces players to trust the device clock, so any skew on the viewer’s machine becomes stalls or missing segments.

A lower-resolution representation is given more bandwidth than a higher-resolution one, so ABR picks wrongly.

Without a <cenc:pssh> in the manifest, playback depends on init data some players will not look for.

Without this anchor a player cannot work out which segments exist yet.

Players are told the manifest never changes, so they never discover new segments.

Players cannot tell how far back the DVR window reaches, so they may seek to segments that no longer exist.

There is no <Period>, so the manifest describes no content at all.

Players use this required attribute to size the initial buffer before starting playback.

Without @profiles a player cannot tell which DASH feature set the manifest expects.

A static manifest declares minimumUpdatePeriod, which contradicts type="static".

A static manifest must say how long it is, or players cannot build a seek bar.

@bandwidth is required, and adaptive bitrate selection depends entirely on it.

Players have no codec configuration before the first media segment arrives.

Durations too large to be seconds are being read as seconds, so segment timing is wrong by orders of magnitude.

The template cannot resolve to a distinct URL per segment, so playback cannot advance.

Players start too close to the live edge and have no room to absorb a slow segment.

The document could not be parsed as XML, so nothing else could be checked.

The XML parsed, but its root is not <MPD>, so it is not a DASH manifest.

Channels with no name appear blank in the subscriber’s list.

Schemes such as rtmp or udp work in VLC but cannot be played by any web client.

Channels without tvg-logo leave gaps in the channel grid.

Ungrouped channels fall into an unnamed catch-all category.

A channel names a DRM system but gives no licence server, so it cannot be decrypted.

Channels without a tvg-id cannot be matched to any programme guide, so they show no schedule information.

Clients cannot resolve a relative logo path, so the image never loads.

The header is present but there are no channel entries.

Without url-tvg in the header, clients have no guide to load and viewers see no programme information.

Lines that do not parse are skipped, so those channels are silently missing from the playlist.

Without the header line this is not an M3U playlist, and most clients will reject it outright.

Identical names make the channel list ambiguous for viewers.

The same stream appears more than once, usually from a duplicated entry.

Duplicate tvg-ids make several channels display the same programme guide.

The guide falls back to the playlist logo or a placeholder.

The channel appears in the guide with an empty schedule.

Channels are declared but there is no schedule, so viewers see an empty guide.

Without <channel> elements there is nothing for a playlist to match against.

Without <category>, genre filtering and recommendations cannot work.

Without <desc>, guide entries show a title and nothing else.

The guide is larger than the per-run limit, so the figures cover only the programmes we read.

Programmes without a <title> appear as blank rows in the guide.

A programme points at a channel id with no <channel> element, so it appears in no guide.

A programme has a stop time at or before its start, producing a zero-length or negative entry.

A start or stop attribute is not in XMLTV format, so the programme cannot be placed on the timeline.

Two programmes claim the same air time, so the guide shows two things at once.

The XML parsed, but its root is not <tv>, so it is not an XMLTV guide.

The document could not be parsed as XML, so nothing else could be checked.

Duplicate ids make programme assignment ambiguous.

The guide runs out within hours, so viewers lose programme information partway through the day.

Consecutive programmes do not join up, leaving blank stretches in the guide.

Timestamps without an explicit offset are ambiguous, and are the usual cause of a guide that appears shifted by whole hours.

The URL resolves to a private or reserved address, so we will not connect to it from the server. Local mode tests it from your own browser instead.

The address could not be parsed, so no request was attempted.

A monitor must be one of hls, dash, m3u or epg.

Only http and https can be fetched; schemes such as rtmp, rtsp and file cannot.

Your browser refused to read the response because the origin did not send an Access-Control-Allow-Origin header.

The server answered with a 4xx or 5xx status instead of the manifest, so there was nothing to analyze.

The connection failed before a response arrived.

The API received a body it could not accept.

The document exceeded the size limit for a single analysis.

We follow up to three redirects; this URL exceeded that.

Saving needs either an account or a working session cookie.