LHLS(.js): Why Hls.js is standardizing low-latency streaming
summary
Claim: LHLS reduces latency from ~30s to ~2s while keeping existing encoders, CDNs and MSE players. Implementation: Hls.js implements a chunk-transfer pipeline that pulls smaller chunked segments directly from transcoders and buffers them in the client. Scope and compatibility: proposal is a backwards‑compatible superset of HLS draft 81.6 and aims to ship in Hls.js (which already reports 753 million embeds), with test streams and server alignment needed to validate scalability.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:51About Hlsjs
- 1:45Latency
- 1:59Testimonial
- 2:21The problem
- 2:37What LHLS does
- 3:10What is LHLS
- 3:47Barrier to entry
- 4:46Empower developers
- 5:27Low latency segments
- 6:29Open standards
- 7:35Collab
- 8:28Support
- 9:06Proposal
- 10:07How you can help
- 11:09Conclusion
related talks
16mCDN Challenges of HTTP-based Low Latency Live Streaming Delivery
10mA default HLS player for Chrome (and why I hate the robustness principle)
27mPerformance of Low-Latency DASH/CMAF and Low-Latency HLS Systems
19mLow Latency Live from a Different Vantage Point
21mThe challenges of deploying Apple's Low Latency HLS In Real Life
21mWhat's new in HLS
20mDecentralizing Video Streaming
37mThree Roads to Jerusalem