Live Video Web Player Low-Latency Integration Spec

Role: Principal Web Video Solutions Architect

Context

• Protocol: {{streaming_protocol}}
• DRM Ecosystem: {{drm_provider}}
• Latency Target: {{target_latency_ms}}
• Client Support: {{target_browsers}}
• Telemetry: {{analytics_sink}}
• Core Engine: {{player_framework}}

Task

Draft a comprehensive web video player integration specification that defines buffer heuristics, DRM certificate exchange, and automated failover pipelines to deliver uninterrupted live entertainment playback.

Method

1. Define the Media Source Extensions (MSE) and Encrypted Media Extensions (EME) initialization sequence tailored to {{player_framework}}.
2. Detail the token acquisition and key license exchange workflow for {{drm_provider}} across {{target_browsers}}.
3. Specify adaptive bitrate (ABR) switching algorithms calibrated specifically to maintain {{target_latency_ms}} under volatile network conditions.
4. Design buffer starvation recovery, playback stall handling, and audio-video drift synchronisation rules.
5. Outline the deterministic failover tree from {{streaming_protocol}} primary streams to backup redundant endpoints.
6. Formulate Quality of Experience (QoE) metric emissions (TTFB, startup time, rebuffering ratio) routed to {{analytics_sink}}.
7. Document error codes, retry policies, and graceful fallback UI states for playback failures.

Constraints

• MUST define concrete buffer forward/backward limits in fractional seconds.
• MUST NOT leave DRM key renewal intervals unspecified.
• Include explicit cross-browser edge cases for MediaKeySession lifecycles.
• Adhere to zero external DOM dependencies outside the core framework.

Output format

Provide a technical specification structured under these mandatory headers:

1. Pipeline Architecture Diagram (text-based flow)
2. DRM and Key Management Lifecycle
3. Low-Latency Buffer & ABR Rules (exact numerical tables)
4. Redundancy & Failover State Machine
5. Telemetry & QoE Schema (JSON structure) Target total length: 900-1400 words.

Self-review

• Confirm that every browser listed in {{target_browsers}} has MSE/EME compatibility accounted for.
• Verify that latency constraints match {{target_latency_ms}}.
• Ensure DRM retry logic covers network timeouts and licensing revocation.