Configure Low-Latency DASH (LL-DASH) with chunked transfer and availabilityTimeOffset
domain: dash · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set the MPD type to 'dynamic' and configure a short suggestedPresentationDelay (e.g., 3–4 seconds) in the MPD to push the presentation time close to the live edge
Enable chunked encoding in your packager so each DASH segment is delivered via HTTP chunked transfer encoding as chunks become available, rather than after the full segment is complete
Set availabilityTimeOffset in the SegmentTemplate to indicate how many seconds before nominal availability a chunk is accessible; this allows clients to fetch in-progress segments
Set availabilityTimeComplete='false' on the SegmentTemplate to signal that segments are not fully available at their nominal availability time and clients should use chunked fetch
Verify end-to-end latency with a DASH player supporting LL-DASH (e.g., dash.js with lowLatencyMode enabled) and monitor buffer occupancy to tune suggestedPresentationDelay
Known gotchas
Not all CDNs support HTTP/1.1 chunked transfer encoding passthrough for media segments; a CDN that buffers the full segment before forwarding silently disables LL-DASH even if the origin emits chunks correctly
availabilityTimeOffset must be set consistently across all Representations in an AdaptationSet; inconsistent values cause some renditions to be unavailable at ABR switch points
LL-DASH requires the client clock to be synchronized with the server; large clock skew causes the player to request segments before they exist (404 storm) or to fall behind the live edge
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?