Live Video Streaming as "tail -f"
summary
Rush claims a simpler live stack: one subscription HTTP request using HTTP push from CDN, a custom container with 36-byte metadata records per frame that enables per-frame addressing and lossy playback, and server-side ABR at the edge using socket-level signals and HTTP/3 extensions for delivery-timeouts. Startup drops from ~five RTTs to one, ABR switches without client requests, per-frame latency control and WebRTC-like retransmit behavior are implemented, and the system already runs in production at scale for millions of viewers.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:59Traditional Architecture
- 1:35DASHVHLS Playback flow
- 6:37RUSH Live Delivery
- 7:01RUSH Playback flow
- 9:22RUSH-C
- 11:46RUSH ABR
- 14:18RUSH Low Latency
related talks
35mLive Low Latency Video Streaming
24mVideo streaming on the web: Live and recorded video streaming
44mLive Video in a Modern Web Environment
23mVideo @Scale Fall 2022 LIVE Q&A #2
16mCDN Challenges of HTTP-based Low Latency Live Streaming Delivery
41m8K Codec Low-Latency Livestreaming, and AI Streaming
46mHow we deliver 1Tbps of video with our WebRTC peer-to-peer network
19mAdventures in WebRTC-based Content Streaming