Non-Standard Codecs With Standard WebRTC
summary
Claims a working path to stream H.264/AAC over standard WebRTC without native codec support by extracting RTP/raw frames on mobile and sending fragmented MP4 over datachannel to MSE in browsers. Implements ExoPlayer piping on Android and VLC RTP ingestion on iOS, and pushes fMP4 over datachannel into Media Source Extensions in the browser. Runs in production for years but increases complexity, adds small latency, risks buffering and loses some WebRTC features like echo cancellation.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:38Peering is Untouched
- 4:43The API based player
- 5:33The Local Player
- 6:36Browsers (MSE and FMP4)
- 7:56Tradeoffs Good side
- 8:47Mobile Tradeoffs
- 9:37Browser Tradeoffs
related talks
22mWebRTC: Connecting Embedded, Mobile and Desktop with the Lowest Latencies
37mWebRTC: From The Ground Up
20mStreaming video in the browser without patents
21mWebRTC A Quick Introduction
31mIn a Perfect World: Why Media Sources Are a Hassle
53mThe State of WebRTC
53mWhat's next for WebRTC?
58mModern & secure adaptive streaming on the Web