Concepts
Live Playback Window
Maintain the moving set of playable live segments that lets players stay near the live edge without depending on media that has not been produced yet.
After this, you will understand
How Live Playback Window helps you see where this idea appears in production systems, what problem forces it, and how to reason about the tradeoffs.
Treat the idea as a definition to memorize.
Real systems force the idea to handle Live Edge, Rolling Manifest, and Segment Window.
Use the concept to decide what the system guarantees, what it risks, and what it costs to operate.
Think before readingWhere would Live Playback Window appear in a real production system, and what failure or bottleneck would it help you reason about?
Reading in progress
This page is saved in your local study history so you can continue later.
Concepts Covered
- Live edge
- Rolling manifests
- Segment windows
- DVR windows
- Playback delay
- Player buffer health
- Manifest freshness
Definition
A live playback window is the moving range of segments that a player is allowed to fetch during a live stream.
In video-on-demand, the manifest can describe the entire movie because the media already exists. In live streaming, the future segments do not exist yet. The manifest can only describe a recent window of produced segments and the current live edge.
old segments <- playable window -> newest safe segment -> live edge -> future
The player keeps refreshing the manifest to learn what new segments have become available.
The Pain That Forces This Concept
A naive live player might try to request "the current second" of the event.
That breaks because production is not perfectly smooth:
- encoders need time to create segments
- packagers need time to publish manifests
- CDN edges need time to fetch new segments
- networks add jitter
- the player needs buffer to survive short delays
If the player stays too close to the live edge, a tiny delay becomes a stall. If it stays too far behind, the stream feels less live and viewers may see spoilers from social feeds, chat, betting apps, or friends watching elsewhere.
The live playback window exists to define the safe zone between "too old" and "not ready yet."
Mental Model
The live stream is a conveyor belt.
New segments appear at one end. Old segments fall off the other end unless the product supports rewind.
segment 101 -> segment 102 -> segment 103 -> segment 104
player safely watches here
live edge here
The player usually does not stand directly on the live edge. It follows at a deliberate delay so playback can absorb short network and packaging hiccups.
How It Works
A rolling manifest might expose:
event_id
manifest_version
earliest_segment_number
latest_segment_number
live_edge_time
target_segment_duration
safe_playback_delay
dvr_window_seconds
During playback:
1. Player fetches the live manifest.
2. Player chooses a starting segment behind the live edge.
3. Player downloads enough segments to build a buffer.
4. Player periodically refreshes the manifest.
5. New segment references appear as the event continues.
6. Old segment references disappear unless DVR is enabled.
If the manifest stops advancing, the player can keep playing only until its buffer runs out.
Tradeoffs
| Choice | Benefit | Cost |
|---|---|---|
| Very low delay | Feels closer to real time | More stalls when jitter appears |
| Larger delay | More stable playback | Viewers are farther behind live action |
| Short segments | Faster updates and adaptation | More requests and manifest churn |
| Longer segments | Lower request overhead | Slower recovery and higher latency |
| DVR window | Viewers can rewind or join late | More storage and manifest complexity |
| No DVR window | Simpler live path | Less flexible viewing experience |
The product should choose a latency target intentionally. A concert, a fight, a football final, and a live auction may all have different tolerance for delay.
Operational Reality
Operators watch:
- manifest update interval
- live edge time
- safe playback delay
- segment publication latency
- player distance from live edge
- buffer health
- manifest fetch errors
- segment-not-found errors
- rebuffer rate after manifest stalls
Failure modes:
- manifest advances before segments are available
- manifest stops advancing while encoders still run
- players refresh manifests in synchronized bursts
- old segments disappear before slow players fetch them
- safe playback delay is too aggressive for weak networks
- CDN caches a stale live manifest too long
Related Topics
What to study next
These links keep the session moving: read prerequisites first, then open the systems, concepts, and patterns that deepen this page.
Prerequisites
Read these first if the mechanics feel unfamiliar.
Used In Systems
System studies where this idea appears in context.
Related Concepts
Core ideas that connect to this topic.