Why is TCP/IP not suitable for sending voice or streaming videos over the internet?

Question

Why is TCP/IP not suitable for sending voice or streaming videos over the internet?

Answer 1

Although TCP may not be used, IP has to be used. The Internet is based on IP (Internet Protocol).



For voice, UDP/IP is the more obvious choice. If a packet gets lost, then the odd syllable may be clipped. However, it is important that packets that do arrive in the correct sequence or uyo ghtmi get sagesmes atth sound keli isth (you might get messages that sound like this). IP does not guarantee that packets are delivered in the order that they are sent. The same is true for live video streaming.



However, for streaming pre-recorded video such as TV catch-up services and film services, then TCP or a similar protocol is required. The sending server will not deliberately transmit packets at the specific playback rate, and there has to be some method of providing flow control. The server will send packets much faster than the video will play, and the receiving device will buffer the data and then pause the data stream until the buffers have partially emptied. This has two advantages - lost packets can be repeated to maintain the video quality and disruptions in the flow of data from the server do not cause the video to stutter. I suspect that pre-recorded video streams use TCP and IP so they can be displayed in a normal web browser.



That's my view. I hope it helps.

Answer 2

Because TCP uses error-correction when it senses a problem. That's good for file transmissions, where the file just sits there and TCP can say, "send those packets again, please." But it's not good for voice or video because the person talking doesn't repeat what he was saying and video doesn't rewind to just before the trouble started. You'd either see a jittery picture or hear a wicked stutter.



In both of these cases the source has moved on -- so error correction isn't needed. That's why UDP can be used for these operations.

Answer 3

Who says it's not?