The Evolution of Audio over IP Protocols: A Comprehensive Overview for Modern Audio Networks

The world of audio networking has experienced significant advancements over the past few decades. The evolution of Audio over Internet Protocol (AoIP) protocols has played a crucial role in transforming how audio data is transmitted, managed, and integrated into modern communication systems. From early proprietary solutions to today’s open standards, AoIP has moved from niche professional use to a backbone technology in broadcasting, live sound, corporate AV, and even consumer streaming. Understanding this evolution helps engineers, system designers, and IT professionals make informed decisions about network architecture, equipment selection, and system scalability.

What Are AoIP Protocols?

AoIP protocols are standards that enable the transmission of high-quality audio signals over IP networks. Unlike traditional analog or digital audio interfaces—such as AES/EBU, MADI, or analog XLR—AoIP allows for flexible, scalable, and cost-effective audio distribution across various devices and locations. By leveraging standard Ethernet hardware and network infrastructure, AoIP systems can carry dozens, hundreds, or even thousands of audio channels over a single cable, with remote control and monitoring capabilities built in.

Key characteristics of AoIP protocols include:

  • Low latency: Typically in the range of 1–10 milliseconds, depending on network design and protocol.
  • Precision timing: Using IEEE 1588 Precision Time Protocol (PTP) for sample-accurate synchronization across devices.
  • Quality of Service (QoS): Prioritization of audio packets to minimize jitter and packet loss.
  • Interoperability: Standards like AES67 and ST 2110-30 allow different manufacturers’ equipment to work together.
  • Redundancy: Support for redundant network paths and automatic failover for critical applications.

The Evolution of AoIP Protocols

The development of AoIP protocols has been driven by the need for better reliability, lower latency, and greater interoperability. Early protocols like EtherSound and CobraNet laid the groundwork, but they faced limitations such as proprietary formats and scalability issues. EtherSound, introduced by Digigram in the early 2000s, offered 128 channels at 48 kHz with sub-millisecond latency, but required dedicated hardware and lacked inter-manufacturer support. CobraNet, developed by Peak Audio (later acquired by Cirrus Logic), became popular in installed sound systems but was limited to 48 kHz sample rates and had a maximum channel count that constrained larger deployments.

In response, industry leaders collaborated to create open standards that could work across different systems. The Audio Video Bridging (AVB) standards, developed by IEEE (primarily 802.1BA, 802.1Qat, and 802.1AS), provided a foundation for real-time audio transmission with precise timing and synchronization. AVB brought benefits like guaranteed bandwidth reservation (Stream Reservation Protocol) and network-wide clock distribution, but adoption was slow due to the need for specialized AVB-enabled switches and endpoints.

Another major milestone was the creation of AES67 by the Audio Engineering Society. Released in 2013, AES67 is not a complete protocol but a standard for interoperability between existing AoIP systems—most notably Dante, Ravenna, and Livewire. It defines a common set of transport, timing, and media stream parameters, enabling devices from different ecosystems to exchange audio. AES67 has become a critical glue in modern audio networks, allowing hybrid systems that blend multiple protocols.

Alongside these developments, the SMPTE ST 2110 suite of standards emerged for professional broadcast environments. ST 2110 separates video, audio, and ancillary data into independent streams, using RTP (Real-Time Transport Protocol) over IP. Its audio component, ST 2110-30, is based on AES67 but adds specific requirements for broadcast workflows, such as support for higher channel counts and multiviewer monitoring.

Key Modern AoIP Protocols

  • Dante: Developed by Audinate, Dante is a widely adopted protocol known for its ease of use, scalability, and robust network management features. It uses a combination of PTPv2 for clocking, UDP for transport, and a proprietary control layer. Dante offers automatic device discovery, zero-configuration setup, and flexible routing via software. It supports sample rates up to 192 kHz and redundant networks. Dante is pervasive in live sound, recording, broadcasting, and installed AV systems.
  • Ravenna: Developed by ALC NetworX (now part of Lawo), Ravenna is an open standard emphasizing interoperability and network transparency. It is based on RTP and PTPv2 and is designed to work over standard IT infrastructure without requiring specialized switches. Ravenna is often used in broadcasting, broadcast consoles, and professional audio environments, particularly in Europe. Its openness allows integration with AES67 and ST 2110.
  • Livewire: Developed by Telos Alliance, Livewire is a protocol designed for broadcast radio and television. It also uses RTP and PTPv2 and offers tight integration with Axia consoles and Telos phone systems. Livewire supports AES67 interoperability and is a key component of IP-based broadcast plants.
  • AVB/TSN: The successor to AVB, Time-Sensitive Networking (TSN) is a set of IEEE standards (802.1Qbv, 802.1Qbu, etc.) that enhance deterministic performance. TSN is used in automotive, industrial, and professional audio networks where ultra-low latency and precise scheduling are required. Products using AVB/TSN include certain editions of Focusrite RedNet and some Meyer Sound products.
  • ST 2110-30: While technically an AoIP standard under the SMPTE umbrella, ST 2110-30 is the audio component of the ST 2110 suite. It uses AES67 as its baseline but specifies additional constraints for broadcasters, such as redundant streams, alignment with video frames, and support for 16-, 24-, and 32-bit audio.
  • NXDN/Other Proprietary Systems: Some manufacturers maintain proprietary protocols for specific ecosystems (e.g., Yamaha’s TWINLANe, BSS’s Soundweb London). These often offer unique features but limit interoperability, leading users to prefer open standards.

The Role of AES67 and ST 2110 in Interoperability

AES67 has become the linchpin for multi-vendor AoIP networks. By defining a common media clock (48 kHz, 44.1 kHz, and their multiples), a common transport (RTP over IP with specific payload types), and a common discovery mechanism (SAP or mDNS), AES67 allows Dante, Ravenna, and Livewire devices to co-exist on the same network and exchange audio. This is critical in facilities that have equipment from different generations or vendors.

ST 2110 takes this further by adding full broadcast workflows. In a live production environment, audio streams must be aligned with video frames (typically at 29.97 or 25 fps) and must support high dynamic range and wide color gamut. ST 2110-30 ensures that audio timing is precisely mapped to video timing using the RTP timestamp offset and the PTP grandmaster clock. Many broadcasters worldwide, including the BBC, NBC, and NHK, are transitioning to IP-based production using ST 2110, with AoIP as a foundational layer.

Impact on Modern Audio Networks

These advancements have revolutionized audio networks in various settings, including live sound, broadcasting, recording studios, and corporate AV systems. They enable:

  • Flexible routing of audio signals: Any audio source can be routed to any destination via software, eliminating the need for physical patching.
  • Remote management and control: Networked devices can be monitored, configured, and updated from a central location or via the cloud.
  • Reduced cabling and infrastructure costs: A single Cat6 or fiber cable can replace dozens of analog or digital audio cables, lowering material and labor costs.
  • Enhanced scalability for growing systems: Adding a new device is often as simple as connecting to the network and configuring via software.
  • Improved redundancy: Dual redundant networks (e.g., primary and secondary Dante networks) can automatically switch on link failure, ensuring uninterrupted audio during critical events like live broadcasts or performances.

The shift to AoIP has also changed system design approaches. Audio engineers now need to understand basic networking concepts like IP addressing, VLANs, QoS, and switch configuration. This convergence has created a new hybrid role—audio networking specialist—and has spurred training programs from manufacturers and professional organizations.

Challenges and Considerations

Despite the benefits, deploying AoIP systems presents challenges. Latency and jitter must be managed through proper network design; using unmanaged switches or congested links can degrade performance. Security is an increasing concern, as IP networks are susceptible to cyberattacks. Best practices include network segmentation (using VLANs), enabling IGMP snooping for multicast traffic, and implementing firewall rules that restrict exposure to the broadcast control network.

Another challenge is the variety of discovery and connection management protocols. Dante uses its own discovery method (mDNS), while Ravenna and AES67 rely on SAP/RTCP. This can lead to configuration headaches in mixed environments. Interoperability works best when all devices support the same AES67 profile, but some implementations still have quirks. Testing and using a unified network management tool (like Audinate’s Dante Controller or Lawo’s Ravenna Explorer) can alleviate these issues.

The future of AoIP protocols focuses on increasing network security, improving latency performance, and integrating with other digital systems like IP-based video and control networks. Innovations such as software-defined networking (SDN) are expected to further optimize audio data management by dynamically allocating bandwidth and prioritizing streams. Additionally, the adoption of 10GbE and 25GbE networks will allow higher channel counts (256+ at 96 kHz) and lower latency.

Security enhancements are also on the horizon. AES67 and ST 2110 are being evaluated for integration with encrypted transport (e.g., SRTP) and authentication mechanisms (802.1X). Manufacturers are adding role-based access control to their device firmware to prevent unauthorized stream manipulation.

Another trend is the convergence of AoIP with general-purpose IP streaming. The use of WebRTC and similar protocols for low-latency audio over IP for remote production is growing, especially in the wake of the pandemic. While these are not standard AoIP protocols in the professional sense, they influence how audio is transmitted over the internet. The line between local network AoIP and cloud-based audio processing is blurring, as seen in the rise of remote broadcast solutions.

Finally, the push toward all-IP infrastructures in broadcast and live events continues. The AES67 and ST 2110 standards are evolving to support higher channel counts, 96 kHz and beyond, and seamless integration with IPMX (the proAV adaptation of ST 2110). We can expect more intelligent network management tools that use machine learning to predict network congestion and automatically reroute audio streams, ensuring uninterrupted delivery. The work of the AES SC-02-12 committee and the Video Services Forum will shape these developments.

Practical Considerations for System Design

When planning an AoIP network, consider the following guidelines:

  • Switch selection: Use managed Gigabit switches that support IGMP snooping, PTP transparent clocking (boundary clock for larger networks), and QoS with DiffServ marking. For AVB/TSN, switches must be AVB-aware or TSN-compliant.
  • Network topology: Layer 3 routing is possible but can introduce latency; for most professional audio applications, a single VLAN with Layer 2 switching is sufficient. For larger installations, use multiple VLANs and route between them via a PTP-aware router.
  • Redundancy: Implement redundant networks using separate switches and cabling for primary and secondary paths. Devices that support seamless redundancy (e.g., Dante dual-homed devices) will switch with zero audio dropout.
  • Cabling: Cat5e is adequate for 100 Mbps audio networks; for 1 GbE and higher, use Cat6 or Cat6a shielded cable. Fiber (SFP modules) is recommended for long runs (over 100 meters) or areas with high electromagnetic interference.
  • Clock master: Designate a PTP grandmaster clock. In mixed-protocol networks, ensure the grandmaster supports the required profile (e.g., AES67 profile for Dante and Ravenna compatibility).

For more detailed guidance, refer to Audinate’s network design whitepapers and the Ravenna technical documentation.

Conclusion

The evolution of AoIP protocols from niche proprietary systems to open, interoperable standards has fundamentally changed how audio is transported in professional environments. Today, engineers can choose from a variety of proven solutions—Dante for simplicity, Ravenna for open flexibility, ST 2110 for broadcast rigor—and mix them with confidence thanks to AES67. As network speeds increase and security demands grow, AoIP protocols will continue to adapt, supporting higher channel counts, lower latency, and tighter integration with IT and broadcast systems. Understanding this landscape is essential for anyone involved in the design, commissioning, or maintenance of modern audio networks. The era of copper multicore is fading; the future is IP.