What are the reasons for WebRTC to discard audio packets?

18 May 2024 · 2 min
1:33

A short technical transcript of a YouTube clip discussing why WebRTC may receive but then discard (not play) audio packets. Speakers explain that audio is packetized into 20 ms frames with RTP timestamps so receivers can detect late arrivals caused by network jitter (handled by a jitter buffer) — packets arriving after their playback time are discarded. Other causes include incorrect RTP timestamps from a buggy sender and audio/video lip-sync drift (if video timing advances too far or too slowly, audio may be dropped to maintain real-time sync).

Chapters

More from Tsahi

9:15
youtube.com

After 15 years of WebRTC, here is when I drop peer-to-peer

1mo ago
1:39
youtube.com

Why UDP won the real-time war #programming #webrtc #shorts

1mo ago
1:37
youtube.com

The Difference Between SFU And TURN Servers #WebRTC #RealTimeCommunications

2mo ago
1:43
youtube.com

Why server logs are useless for WebRTC #webrtc #getStats #observability

2mo ago
1:49
youtube.com

How does WebRTC even know a packet was lost?

2mo ago
1:42
youtube.com

WebRTC gives you every tool to watch your calls, then collects nothing

2mo ago
1:40
youtube.com

All green but calls are broken #qoe #dashboards #webrtc

2mo ago
14:03
youtube.com

Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin

2mo ago
1:16
youtube.com

Is your video API vendor ready for AI agents?

3mo ago
1:21
youtube.com

What "$4 per 1000 Minutes" Really Costs You (Video API Pricing)

3mo ago
1:30
youtube.com

How to Read the WebRTC Tools Hub in 90 Seconds

3mo ago
See all content