IP audio: The new audio format


        Radio on FacebookJoin us on Facebook

By now, “IP audio” is a well-known term, widely written about and, I suspect, many have a pretty good understanding of how it works. The concept of having all the audio and control combined in a simple data packet is appealing on a number of levels, such as reduced studio and facility cabling, ease of originating programming outside the facility, fewer components required and also operating wirelessly over Wi-fi, broadband modem, etc. for quick deployment or permanent STL system. In addition, IP audio can also be sent to a single location or broadcast to many.

The ability to transport audio and video over Ethernet/Internet has been around for years, so how is IP audio different? The simple answer is that there are similarities in terms of how the data is transported, but that's where it stops. Let's start at the beginning with the evolution of IP audio.

Of course, no discussion “audio contribution over IP,” would be complete without a quick review of the protocol that makes transmission possible (that would be the IP part). Internet Protocol consists of a specialized data packet. The data, to be transmitted to a specific destination, is encapsulated in the IP packet. The packet can be viewed as the train that carries a payload, in this case the encoded audio and control data. The engine of the train is called the header, which contains specific information such as: where the train is leaving from, where it is going, in what parts of the train the data is enclosed and how to handle that data once it arrives.

The IP packet alone doesn't have an enormous amount of intelligence; it is just a means to transport data. There are other protocols combined with IP to steer the packets to their intended destination, essentially the engineer of the train. The two common protocols used for this purpose are TCP (Transport Control Protocol) and UDP (Universal Datagram Protocol.) The major difference in these protocols is how they communicate back to the originating network interface. When an IP packet is sent under TCP, confirmation of proper delivery is sent to the sender. If a packet does not arrive, it asks the sender to resend until it has been completed; this is also known as a reliable or connection-oriented transport method. IP under UDP control simply broadcasts the data and assumes it has arrived properly. If a packet fails, it is necessary for the system on the receiving end to have the proper means to handle those errors; for this reason, UDP is called an unreliable or connectionless transport scheme.

A better IP audio method

For the transport of IP audio, one may first think that TCP transport would be the only sensible option, but in reality, what we really want is UDP. Why? Assume we are sending the streaming content (audio or video) over a busy network (Ethernet, Internet, etc.). Under TCP control, many of the packets will need to be resent; while this is going on, most of the other packets are making it through. What happens is that now the packets are showing up in a different order than they were originally sent. That will cause a multitude of problems including significant delays (or latency) between the source and destination codecs.

While IP audio systems are gaining acceptance, many have proprietary protocols that prevent interoperation at this time.

While IP audio systems are gaining acceptance, many have proprietary protocols that prevent interoperation at this time.

The fact is that UDP is the common control protocol used for streaming content, including IP audio. The algorithms in the codec handle any errors and provide the necessary means to make the streaming content meet the intended quality criteria.

Here is where it gets interesting. To overcome some of the challenges presented by sending data using UDP, manufacturers have proprietary protocols that permit a higher level of error control between their encoder and decoder. This may mean that units from different manufacturers might not work together.



Acceptable Use Policy
blog comments powered by Disqus

[an error occurred while processing this directive]

Today in Radio History

Milestones From Radio's Past

The history of radio broadcasting extends beyond the work of a few famous inventors.

EAS Information More on EAS

NWS XML/Atom Feed for CAP Messages

The feed provides feeds for all US states and territories.

Wallpaper Calendar

Radio 2014 Calendar Wallpaper

Need a calendar for your computer desktop? Use one of ours.

The Wire

A virtual press conference

Information from manufacturers and associations about industry news, products, technology and business announcements.

Join Us Facebook Twitter YouTube LinkedIn
Radio magazine cover

Current Issue

KBEM-FM: Revitalizing a Station, Reviving a School

Minneapolis Public Schools upgrades their aging equipment with new Audio over IP technology

Browse Back Issues

[an error occurred while processing this directive]