When IDR Frame Insertion Backfires
summary
Live streams suffer when IDR frame insertion blooms into bursts: a Samsung Galaxy S2 balloon feed triggers scene‑change detection, bursts IDRs, spikes the encoder to a 2 Mbps ceiling and causes retransmits and rebuffering; a separate feed receives 120 scutty 35 markers in 4 seconds, each forcing an IDR and crashing the encoder. Remediation is concrete: disable scene detection or raise min quantization to damp spikes, and add logic to coalesce markers so only one IDR is inserted per burst.
AI-written summary · about
chapters (5)
- 0:00Introduction to IDR frames
- 0:33Common IDR use cases
- 2:12Case study: Ustream balloon
- 6:37Case study: SCTE-35 crashing
- 10:32Lessons and conclusion
related talks
20mYour TV Is Eating Your Frames
22mProviding better video experiences for the next billion users.
21mWanna get rid of UI Jank?
24mDynamic content insertion into live streams across the 3 main streaming formats
17mMetrics Driven Obsession with Viewer Experience
41m8K Codec Low-Latency Livestreaming, and AI Streaming
04mSub-frame Latency
10mHEVC Upload Experiments