In this guide
A boundary changes contextSeparate a signalled event from a playback failureUseful evidence around a boundaryAn HLS discontinuity marks a boundary where the interpretation of the following media needs special care. EXT-X-DISCONTINUITY can signal changes involving timestamp sequences, file formats or track characteristics under the protocol’s rules. It is a timeline instruction, not a message that the viewer’s internet connection disconnected.
A valid presentation can contain discontinuities. The important question is whether the publisher signals the change correctly and whether the client handles the transition.
A boundary changes context
Media timestamps are not simply the order in which files arrived. A player uses timestamps to align and present samples. If a new section restarts its timestamp sequence, treating it as an uninterrupted continuation can misplace media. A discontinuity tells the client that the boundary needs appropriate handling.
An original hypothetical example joins two independently produced clips into one channel timeline. The second clip begins its internal timestamps near zero. A publishing system must express that transition correctly; giving the second clip a different filename does not by itself communicate the timeline change.
Separate a signalled event from a playback failure
A discontinuity tag can appear during a programme transition, an insertion or another media change. Its presence alone is not an error. A freeze precisely at that location is useful evidence because it narrows the investigation to the surrounding media, timestamp handling and possibly format initialization.
For multi-rendition presentations, the relationships between boundaries matter. EXT-X-DISCONTINUITY-SEQUENCE helps identify discontinuity numbering when earlier boundaries leave a live playlist. It should not be confused with EXT-X-MEDIA-SEQUENCE, which numbers media segments.
| Item | Role |
|---|---|
| EXT-X-DISCONTINUITY | Marks a media interpretation boundary |
| Discontinuity sequence | Tracks boundary numbering across playlist windows |
| Media sequence | Numbers media segments |
| New filename | Locates a resource; not a substitute for timing metadata |
Useful evidence around a boundary
Keep the segment immediately before the transition, the first following segment, relevant initialization references and the player’s exact error. If requests succeed but rendering fails at the same boundary repeatedly, transport speed alone is an incomplete explanation. Do not remove boundary tags to make a local playlist look simpler; that changes the instructions the original client received.