Video @Scale Fall 2022 LIVE Q&A #2
summary
Live video shifts toward QUIC-based delivery with experiments reporting warp in production and Meta using Rush for ingest while pushing an IETF draft and WebTransport support; practical choices surface—Pion native Go implementation replaces a heavy webrtc.org build, and a WebRTC encoder bug tied to large keyframes traces to conservative pacing; redundancy uses dual paths with byte-level writes so viewers see no glitches, and latency vs cost is tunable — writing every 10th frame adds ~300ms while every frame costs ~30ms.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:49QUIC high-bandwidth delay links
- 1:33WARP progress and standards
- 2:16Client-side congestion control
- 3:40WebRTC keyframe pacing issues
- 5:03Caffeine Pion vs WebRTC
- 6:47Reliability dual-path strategies
- 9:37Latency cost trade-offs
- 11:03Dual-path sync seamless viewer
- 12:29Rush future ingest protocol
- 14:14FFmpeg bug fixes
- 14:54QUIC adaptive bitrate benefits
- 16:16QUIC codec-agnostic delivery
- 17:40QUIC time metadata lossy handling
- 19:27Rush third-party reliability
- 21:15Media over QUIC latency vs reliability
- 22:39Viewer latency quality trade-offs
- 23:02Closing remarks
related talks
10mRTC @Scale, Future RTC Experiences Session - Live Q&A
17mLive Video Streaming as "tail -f"
34mLightning Talks
25mCacheable live under 200ms glass 2 glass. Is it VC or livestreaming? It is MOQ
50mDemuxed 2023 Lightning Talks
30mThere and back again: reinventing UDP streaming with QUIC
32mWebRTC Update
08h 44mRTC.On Conference 2023