Why a live call can sound better with missing data
A voice or video call arrives as a stream of small bundles called packets. Each carries a slice of audio or image data, plus information that helps the receiver put slices in order. Packets can be delayed, lost, or arrive out of sequence as traffic moves through networks.
For a file download, a missing piece is worth recovering: the receiver can wait for a resend because the file is not useful until it is complete. A conversation has a different constraint. Sound and video are useful only when they arrive close to the moment they were made. If a packet turns up after the playback system has moved on, inserting it would mean stalling the call for information that is already out of date.
The deadline matters more than completeness
Call software therefore gives each packet a short window in which it can still help. If a packet is missing, the receiver may briefly wait or request another copy when it can arrive in time. Otherwise, it moves on. For audio, it can smooth over a tiny gap by extending nearby sounds or estimating what was likely there; video may show a brief visual glitch until a fresh frame arrives.
This is a deliberate tradeoff, not a rule for all internet traffic. Systems that transfer files generally prioritize getting every piece right, even if that takes longer. Live applications prioritize keeping the stream moving, while using buffering, error correction, and congestion controls to reduce interruptions where possible.
The result is that a call can remain nearly conversational even when the network is imperfect. A tiny flaw on screen may be less disruptive than a pause that makes both people wait for a moment that has already passed.
