CMAF and DASH-IF Live ingest protocol
summary
A DASH‑IF specification defines two live‑ingest interfaces: CMAF ingest (per‑track fragmented MP4 over HTTP POST, one TCP connection per track, long or short posts supported) and DASH/HLS presentation ingest (short POSTs of segments and manifests, unique URI layout to avoid overwrites). It claims low latency, timed metadata via an event‑message metadata track, redundancy through synchronized timestamps and splice signaling using binary SCTE‑35, and provides an open‑source reference implementation and Docker demo that demonstrate feasibility.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:49What is CMAF
- 1:44Why CMAF
- 4:15Why Pushbased
- 5:39Ecosystem
- 6:41Timeline
- 7:35Interfaces
- 8:34CMAF ingest
- 10:59CMAF boxes
- 11:50Network requirements
- 13:40Switching sets
- 16:24Synchronization
- 16:54Fast packaging
- 18:22Track structure
- 18:47Splice conditioning
- 20:36CMAF HLS ingest
- 22:15Summary
- 23:39CMAF reference software
- 24:00CMAF at IBC
- 24:21Thanks
related talks
43mMedia Source Extensions
43mDASH and Media-over-QUIC Transport Face-Off: Performance Showdown at Low Latency
24mDynamic content insertion into live streams across the 3 main streaming formats
19mLow Latency Live from a Different Vantage Point
08mHow to play Dash on your HLS Player
27mPerformance of Low-Latency DASH/CMAF and Low-Latency HLS Systems
46mModern & secure adaptive streaming on the Web
58mModern & secure adaptive streaming on the Web