VIDEO
HIGHLIGHT
Log InSign up
Broadcast Audio Over IP Explained
SummaryTranscriptChat

Broadcast Audio Over IP Explained

Introduction to Audio over IP (AoIP)

In this video, Eric from Bartos Media introduces the basics of AoIP or Audio over IP. He covers everything from the protocols to how they're implemented and yet somehow all different but still a little bit the same.

Basics of AoIP

  • Eric mentions that he has not been paid or contacted by any manufacturer he talks about in this video.
  • AoIP is running on a network and requires two things to make it work - an RTP stream and a master clocking source.
  • RTP stands for Real-time Transport Protocol, which is how audio data is transmitted over the network. It's been around since 1996 as RFC 1889 and has proven to be reliable.
  • Different aoip vendors use RTP as the basis of their protocol, but they are not interchangeable due to different ways of implementing the protocol in an aoip system.
  • The codec used along with the clocking mechanism distinguishes all different aoip brands from each other except for AES67.

Clocking Mechanism

  • A clocking source is required in an aoip network to keep all audio spewed into the network in order when decoded on the other side of that network switch.
  • Most newer versions of these protocols support syncing to Precision Time Protocol (PTP), which allows devices to synchronize together to a single master clock.

Basics of Networking

  • A solid managed network switch is essential for an aoip network. Managed switches prioritize audio traffic on your network and allow you to use a protocol called VLANs.
  • Unmanaged network switches may work, but they won't work essentially with managed switches. Business and enterprise applications provide wonderful customer support if you're buying these new.

Conclusion

In conclusion, Eric provides an introduction to the basics of AoIP or Audio over IP. He covers everything from the protocols to how they're implemented and yet somehow all different but still a little bit the same. A clocking source is required in an aoip network to keep all audio spewed into the network in order when decoded on the other side of that network switch. A solid managed network switch is essential for an aoip network as it prioritizes audio traffic on your network and allows you to use a protocol called VLANs.

Introduction to Audio over IP

In this section, the speaker introduces the concept of audio over IP and explains that while additional network components like layer 3 switches or routers can be helpful, they are not necessary for basic audio over IP systems.

Audio Over IP Protocols

  • The speaker discusses Dante as a mainstream audio over IP protocol that has been integrated into many manufacturers' product lines. Dante is a closed protocol but is compatible with AES67, allowing it to send and receive audio to any device that supports AES67 on the network.
  • The speaker explains AES67 as a standard for audio over IP interoperability developed by the Audio Engineering Society. It specifies sample rates, bit depth, and maximum channels per device. There are both compliant and compatible devices and protocols.
  • The speaker notes that Dante is only compatible with AES67 and not compliant due to its clocking mechanism. However, it still demonstrates the value of a standard that allows different vendors and manufacturers to create devices that can talk to each other.
  • The speaker introduces Livewire as an audio over IP protocol developed by Axia Audio. Livewire was designed with broadcast studios in mind and includes features like GPIO signaling source advertisement, control, routing protocols called Livewire Routing Protocol (LWRP), which makes it easier to toggle an on-air light or remote start a CD player.

Conclusion

The speaker provides an overview of two popular audio-over-IP protocols - Dante and Livewire - explaining their compatibility with AES67 standards. They also highlight how these protocols have been designed keeping in mind specific use cases such as broadcast studios.

Audio over IP Protocols

This section provides an overview of the two main audio over IP protocols, Dante and Livewire. It explains how they differ in terms of audio streams and routing protocols.

Dante vs. Livewire

  • Dante has one audio stream per device that is listening, while Livewire has one audio stream per audio channel.
  • In Livewire, the stream is sent off to every single device on the network with multicast, but only devices that are subscribed to that specific channel number or are listening to that specific IP address will be able to receive and listen to that audio.
  • Both protocols can be run in either multicast or unicast mode, but running Livewire in unicast mode changes the fundamental operation of the routing protocol and is only recommended in situations where your network does not have the bandwidth required to support every single multicast stream.
  • Livewire has its own clocking source, but due to its AES67 compliance, you can sync your entire Livewire plant to a PTP v2 master clock.

Audio Drivers

This section discusses the software component of audio over IP networks - an audio driver - which allows you to receive digital audio directly into and out of the network without having to purchase special high-quality hardware.

Audio Drivers

  • Almost every audio over IP system has a large software component that goes along with it, and the biggest part of this software component is an audio driver.
  • You can install this driver on any computer that supports it, allowing you to receive digital audio directly into and out of the network without having to purchase special high-quality audio hardware to convert your audio from your computer to digital or analog back into digital or digital back into analog.

Considerations for Audio over IP

This section provides some final considerations for using audio over IP, including the fact that it is not a one-size-fits-all solution and that each protocol has its own issues.

Final Considerations

  • Digital audio and audio over IP are not a one-size-fits-all solution, and each protocol has its own little issues that might not make it the best solution for your use case.
  • If you're in the market for a digital audio or audio over IP solution, shop around and try out different equipment to make sure you pick the solution that will fit your needs and budget.
  • It may not always be possible from a budget standpoint or even a logistical standpoint to rip out an existing system and replace it with audio over IP, so consider whether the resources to maintain such a system exist in your environment.
Video description

Audio Over IP, the gold standard in today's broadcast studios and live sound systems. My goal with this video is to help you understand the basic concepts involved with AoIP, as well as give you a overview of some of the protocols that are available on the market right now. RFC 3550 RTP: https://tools.ietf.org/html/rfc3550 IEEE 1588-2002 PTP v1: https://standards.ieee.org/standard/1588-2002.html IEEE 1588-2008 PTP v2: https://standards.ieee.org/standard/1588-2008.html 0:00 Intro 0:20 Disclamer 0:34 Welcome 0:55 The Basics (how AoIP works / RTP) 3:13 AoIP Clocking 4:32 Networking Basics 6:24 Dante Overview 7:36 AES67 Overview 10:23 Telos Livewire+ Overview 11:53 Livewire+ Networking (Multicast / Unicast) 14:17 AoIP Software Drivers 14:55 Closing Thoughts ~Social Media~ Twitter: https://twitter.com/erbartos Instagram: https://www.instagram.com/superior_negatives/ ~Music~ Epidemic Sound Audiio ~Film Gear That I Regularly Use~ Primary camera: Blackmagic Pocket Cinema Camera 4k Secondary camera: Panasonic G7 Mic: Rode Videomicro Other mic: Rode NTG1 Main lens: Rokinon 16mm t2.2 Other lens: Laowa 17mm f1.8 Vlog & lens on secondary camera: Panasonic 12-32 F3.5-5.6 Gimbal: Ronin-SC Drone: Mavic Mini Other stuff: https://kit.co/bartos