Understanding AES67: The Interoperability Backbone for Modern Broadcast Audio

Modern broadcast facilities are undergoing a fundamental transformation as they migrate from dedicated, point-to-point audio wiring to packet-based IP networks. At the center of this shift is AES67, a standard developed by the Audio Engineering Society that defines how high-performance audio-over-IP (AoIP) streams can be exchanged between equipment from different manufacturers. Officially titled “AES standard for audio applications of networks – High-performance streaming audio-over-IP interoperability,” AES67 specifies a common set of transport protocols, sample rates, bit depths, and latency profiles that allow a wide range of professional audio devices to communicate directly over standard Ethernet infrastructure.

The standard uses Real-time Transport Protocol (RTP) over UDP/IP, supports sample rates of 48 kHz or 96 kHz with 16 or 24 bits per sample, and defines latency blocks of 1 ms, 2 ms, and 5 ms. Critically, AES67 operates at Layer 3 of the OSI model, meaning the audio streams can be routed across subnets and wide area networks (WANs) using standard IP routing. This contrasts with earlier Layer 2 protocols that were confined to a single broadcast domain. Any device with a Gigabit or 10 GbE interface can participate, making AES67 a truly infrastructure-agnostic solution.

For broadcast engineers, the AoIP landscape includes several popular ecosystems: Dante (Audinate) for its plug-and-play ease, Ravenna (open standard, used by Lawo and Merging), Q-LAN (QSC), and Livewire+ (Telos Alliance). AES67 functions as the common denominator that bridges these systems. A Dante-equipped codec can send audio directly to a Ravenna-based console without a proprietary converter, and a Q-LAN speaker system can receive program audio from a Livewire+ network. This interoperability is the key driver for adoption in large facilities where multi-vendor equipment is the norm.

Strategic Motivations for Adopting AES67 at Scale

Moving from legacy MADI or TDM routing to an AES67-based IP network is more than a technical upgrade; it is a strategic decision that reshapes operational workflows, vendor relationships, and capital expenditure.

Ending Vendor Lock-In Through Open Standards

Historically, broadcast facilities often standardized on a single manufacturer to ensure compatibility between consoles, routers, and peripherals. This created dependency on proprietary backplanes and expensive upgrade paths. AES67 breaks that cycle. A facility can deploy a Calrec console in one control room, a Lawo desk in another, and an SSL system in a third, and all can share audio streams via AES67 without additional bridging hardware. Intercom systems from Riedel and Clear-Com can be integrated natively, and DSP devices from different vendors can be mixed freely. The standard gives engineers the freedom to choose the best tool for each application while maintaining a unified audio transport layer.

Inherent Scalability of IP Networks

Traditional MADI routers have fixed channel counts defined by backplane slots and card capacities. Scaling up requires purchasing an entirely new chassis or linking multiple frames. An AES67-based network, by contrast, scales by adding standard network switches and managing IP addresses. A single 10 GbE link can transport hundreds of uncompressed audio channels, and using multicast, one source can feed unlimited destinations without consuming extra switch port bandwidth. This is ideal for distributing program audio, intercom signals, and studio monitoring across large campuses or multiple buildings. As the facility grows, new switches are simply added to the network, and the routing becomes a matter of IP address configuration.

Cost Reduction Through Commodity Hardware

One of the most compelling financial arguments for AES67 is the hardware cost. A 256×256 MADI router is a specialized, expensive piece of equipment. In an IP world, a 48-port Gigabit or 10 GbE managed switch from vendors like Arista, Cisco, or Juniper is a mass-produced commodity with competitive pricing. Broadcasters can dramatically reduce capital expenditure on routing infrastructure. Operational costs also fall: standard CAT6 cabling and SFP modules are far cheaper than high-density BNC patch panels and multi-core MADI cables. Additionally, troubleshooting an IP network often leverages tools familiar to IT staff, reducing reliance on specialized broadcast engineers for routine maintenance.

Future-Proofing with SMPTE ST 2110 Compliance

AES67 is not an isolated standard; it is the audio component of the SMPTE ST 2110 suite for professional media over IP. Specifically, SMPTE ST 2110-30 defines the transport of uncompressed PCM audio and is a superset of AES67. This means any facility investing in AES67-compatible equipment today is already prepared for a complete transition to ST 2110, which also encompasses video (ST 2110-20) and ancillary data (ST 2110-40). The backward compatibility ensures that the audio infrastructure remains relevant as production environments move toward fully unified IP networks, avoiding costly forklift upgrades later.

Real-World Deployments: How Major Broadcasters Leverage AES67

The theoretical advantages of AES67 have been proven in some of the most demanding broadcast facilities worldwide. The following case studies illustrate how the standard solves real operational challenges.

BBC Radio’s Networked Production Infrastructure

The British Broadcasting Corporation (BBC) has been a pioneer in IP audio, deploying large-scale AES67 networks in its major production centers, including Broadcasting House in London. The facility interconnects Calrec Artemis consoles with Lawo mixing systems, along with contribution codecs, intercom panels, and legacy analog interfaces. By standardizing on AES67 as the transport layer, the BBC engineering team can route audio between any two points in the building using IP addresses rather than physical patch panels. This has drastically reduced changeover time between programs and enabled seamless “follow the talent” workflows across multiple studios. Outside broadcast teams connect mobile units directly into the core network via standard IP links, routing hundreds of channels of audio as if they were in the same equipment room.

NBC Sports and the Olympic Games IP Environment

For large-scale event productions like the Olympic Games, NBC Sports has deployed some of the most advanced IP production systems. In partnership with Imagine Communications, Evertz, and Lawo, NBC’s production trucks and the International Broadcast Centre (IBC) rely on SMPTE ST 2110, with AES67 (ST 2110-30) handling all audio routing. During the games, thousands of tracks of commentary, ambient audio, and program feeds are routed between multi-vendor consoles, routers, and distribution systems. The ability to manage audio purely through IP networking has dramatically simplified signal flow, allowing engineers to reconfigure the entire broadcast network in minutes rather than hours. AES67 ensures that audio from a Lawo commentary unit can be directly ingested by an Evertz routing platform without any intermediate converters, providing the low latency and high reliability required for live sports.

ARD and ZDF: Interoperability Across German Public Broadcasting

Germany’s public broadcasting landscape consists of multiple regional broadcasters (Landesrundfunkanstalten) under the ARD umbrella, alongside national broadcaster ZDF. These entities historically adopted different audio networking technologies from various vendors. When they needed to collaborate on joint news programming, rights-shared sports events, or emergency broadcasts, this heterogeneity created significant challenges. By implementing AES67 as a common interoperability profile, the broadcasters established a nationwide audio transport network. Studios in Munich, Hamburg, Cologne, and Mainz now share audio streams granularly without dedicated circuits or protocol converters. This project demonstrates that AES67 is robust enough for WAN-based audio transport, enabling a more flexible and resilient national broadcasting infrastructure.

European Broadcast Union (EBU) Pilot Projects

The EBU has actively promoted AES67 through pilot projects across multiple member broadcasters. In one initiative, a live music performance was produced using a mix of Calrec, Lawo, and SSL consoles, all interconnected via AES67 over a dedicated IP network. The project validated that multi-vendor interoperability can be achieved without compromising audio quality or latency. The EBU’s technical publications provide detailed guidance on configuration and best practices, helping smaller broadcasters adopt the standard with confidence.

Technical Challenges and Best Practices in AES67 Deployment

Despite its advantages, deploying AES67 at scale requires careful attention to network engineering principles. Transitioning from the deterministic, physical world of SDI to the packet-based world of IP introduces several challenges that must be addressed.

Precision Time Protocol (PTP) and Clock Synchronization

AES67 demands a highly accurate common clock to ensure all devices sample and play out audio at exactly the same rate. It relies on IEEE 1588-2008 Precision Time Protocol (PTP), using profiles such as SMPTE ST 2059-1/2 or AES67-2015. Configuring a PTP network is often the most complex part of an AoIP deployment. Engineers must designate a highly accurate Grandmaster clock (typically GPS-locked), configure Boundary Clocks or Transparent Clocks in network switches to reduce jitter, and manage the PTP domain across multiple subnets. A misconfigured PTP network can cause clock drift, audio dropouts, or complete system failure. Facilities must invest in training staff to manage PTP and understand its critical role in maintaining audio signal integrity.

Network Security and VLAN Segregation

As broadcast networks converge with enterprise IT, security becomes paramount. An unlocked network port in a studio could be used to inject malicious traffic or disrupt audio streams. Proper AES67 network design requires strict VLAN segregation to separate control, audio, and management traffic. IGMP snooping controls multicast traffic flooding, and Access Control Lists (ACLs) limit unauthorized access. Protecting the PTP path from latency spikes requires careful Quality of Service (QoS) marking using Differentiated Services Code Point (DSCP) values. Broadcast engineers must collaborate closely with IT departments to ensure the network is both secure and capable of delivering deterministic performance.

Latency Budgeting and Network Topology

AES67 can achieve low latency (as low as 1 ms block size), but achieving this across a complex network topology requires rigorous design. Every network switch adds a small amount of switching latency; routers add more. Jitter buffers in receiving devices must be sized correctly to absorb network jitter without adding excessive delay. Over a local studio network, 1 ms latency is easily achievable. However, over a WAN linking a remote studio to a central broadcast center, latency must be carefully budgeted. Engineers must select appropriate switch hardware, minimize hop counts, avoid oversubscribing uplinks, and rigorously apply QoS policies to protect audio traffic from bursts of data. A well-designed AES67 network treats latency and jitter as hard constraints, similar to how an SDI engineer treats cable length and equalization.

The Future of AES67: Integration with NMOS and TSN

The adoption of AES67 is accelerating, but the ecosystem continues to evolve. The standard is becoming a foundational piece of a larger, fully automated IP production environment.

The integration of AES67 with the Networked Media Open Specifications (NMOS) is a major development. NMOS specifications such as IS-04 (Discovery) and IS-05 (Connection Management) allow AES67 streams to be automatically discovered and routed without manual IP address configuration. This transforms a network of individual devices into a coherent, routable audio system. For a major broadcast facility, NMOS support means an engineer can route a commentary feed or a program mix from a control room GUI, with the system automatically managing multicast groups and PTP information across the network.

Furthermore, the landscape of audio over IP is moving toward IEEE 802.1 Time-Sensitive Networking (TSN). TSN provides standards for guaranteed packet delivery with bounded latency over Ethernet, which could further simplify QoS management and improve determinism for AES67 streams. As broadcast workflows increasingly adopt cloud-based production and remote integration, AES67’s ability to route audio over standard IP WAN links will become even more strategically valuable. The standard is not static; it is a living profile that adapts to industry needs.

Conclusion: AES67 as the Universal Audio Language for Broadcast

The case for AES67 adoption in major broadcast facilities is built on technical excellence, operational flexibility, and strategic foresight. It solves historic vendor lock-in, scales seamlessly to thousands of channels, and reduces both capital and operational costs by leveraging commodity IP infrastructure. Most importantly, it is the audio standard fully aligned with the future of media production—the SMPTE ST 2110 suite and NMOS control.

For broadcast engineers and technical decision-makers, the question is no longer whether to adopt IP audio, but how quickly they can build the internal expertise to deploy and manage it. Mastery of IP networking, PTP timing, and multicast routing is now a core competency for the modern broadcast engineering team. By investing in AES67 today, facilities are not just upgrading their audio infrastructure; they are building the foundation for the next generation of agile, scalable, and cost-effective broadcast production. For further reading, refer to the AES standards page, SMPTE, and the Advanced Media Workflow Association (NMOS).