Table of Contents

Understanding AES67: The Audio-over-IP Interoperability Standard

The rapid digitization of professional audio has placed unprecedented demands on infrastructure. As studios, broadcast facilities, live sound venues, and corporate AV systems migrate from point-to-point analog or digital connections to packet-switched networks, the need for a universal language becomes critical. AES67 was developed by the Audio Engineering Society to address precisely this challenge—providing a standards-based mechanism for different audio-over-IP (AoIP) systems to communicate seamlessly over standard Ethernet networks. Published as AES67-2015 and updated periodically, the standard defines a set of mandatory requirements for transport, synchronization, and encoding, enabling devices from different manufacturers—even those using proprietary protocols like Dante, Ravenna, or Q-Lan—to exchange multichannel audio with deterministic low latency and high fidelity.

At its core, AES67 specifies three key elements: RTP (Real-time Transport Protocol) for audio payload delivery, PTPv2 (Precision Time Protocol, IEEE 1588-2008) for synchronization, and PCM (Pulse Code Modulation) at common sample rates (48 kHz, 96 kHz, and higher) with 16-, 20-, or 24-bit depth. By abstracting the network transport from the application layer, AES67 ensures that any AES67-compliant device, whether a microphone preamp, mixing console, or DSP processor, can be connected to a switch and immediately participate in a shared media environment. This layer of interoperability is what makes AES67 a cornerstone for future-proofing audio investments—organizations can select best-of-breed components without worrying about vendor lock-in.

The standard has gained traction across multiple industries. In broadcasting, AES67 is a key component of the SMPTE ST 2110 suite for professional media over IP networks. In live sound, many digital mixing consoles now offer native AES67 support or adopt Ravenna—a transport layer built entirely on AES67. Installed sound systems in universities, convention centers, and houses of worship leverage AES67 to integrate ceiling speakers, paging microphones, and audio processing across sprawling campuses. Understanding AES67 is therefore not merely a technical exercise; it’s a strategic imperative for anyone procuring audio infrastructure today.

How AES67 Achieves Low-Latency Interoperability

The interoperability magic of AES67 rests on three tightly coordinated mechanisms. First, the standard mandates a maximum packet time of 1 millisecond (1 ms) for audio payloads, which translates to 48 samples per packet at a 48 kHz sample rate. This small packet size keeps end-to-end latency under 2 ms, a critical threshold for live sound and monitoring applications. Second, AES67 requires compliant devices to support the profile defined in IEEE 1588-2008 (PTPv2) for clock synchronization, typically using the default profile for telecom and audio. This allows all devices on the network to share a common time reference with microsecond accuracy, eliminating sample-rate drift between different manufacturers' gear. Third, the standard specifies multicast address assignment and IGMP snooping requirements to ensure that audio streams are delivered only to intended receivers without saturating the network. Together, these mechanisms guarantee that a mix of devices from Audinate, RAVENNA, QSC, Lawo, or any other vendor can sync and deliver audio in real time without degradation or interruption.

Core Benefits of AES67 for Future-Proofing Audio Investments

Unmatched Interoperability Breaks Proprietary Chains

One of the most compelling arguments for adopting AES67 is the freedom it grants from proprietary ecosystems. Traditional AoIP solutions from leading manufacturers often require all devices to be sourced from a single vendor or certified partners. This creates a lock-in effect where expansion or upgrades come with significant cost premiums and limited options. AES67 flips this model: any AES67-compliant device from any manufacturer can coexist on the same network. For example, a studio can pair a Dante-enabled audio interface with a Ravenna-based mixing console through a compliant switch, using AES67 as the bridging protocol. This interoperability extends the life of existing gear—legacy devices can remain in the signal path as long as they support AES67 or can be connected via adapters. Over the lifecycle of a facility (typically 7–15 years for permanent installations), this flexibility translates to substantial capital expenditure savings and reduced risk of premature obsolescence.

Scalability Without Architectural Overhaul

Future-proofing also means planning for growth. AES67 networks are inherently scalable because they operate on standard Ethernet infrastructure. Adding new audio endpoints—whether it’s an additional microphone in a conference room or a remote broadcast truck feed—simply requires connecting to a port on the network switch and configuring the session via a management tool. There is no need to rewire analog multicores, replace patchbays, or install dedicated coax or MADI cables. As bandwidth demands increase, organizations can upgrade individual switch links to higher speeds (e.g., 1 Gbps to 10 Gbps) without replacing the audio endpoints themselves, because AES67’s network requirements are satisfied by common off-the-shelf switches. This linear scalability protects the investment in the audio infrastructure while accommodating expansion in room count, channel counts, or sampling rates.

Flexibility to Adapt to New Workflows and Standards

The audio industry is not static. New codecs like MPEG-H, immersive audio formats like Dolby Atmos, and next-gen broadcast standards (ATSC 3.0) are emerging. AES67’s design as a transparent transport for PCM audio means it can carry any content that is mapped to a PCM sample stream. More importantly, AES67 serves as the baseline for more advanced AoIP profiles. For instance, the SMPTE ST 2110-30 and ST 2110-31 standards for professional media over IP build directly on AES67 for audio transport, adding support for AES3 payload alignment and metadata. Organizations that invest in AES67 today are essentially buying a gateway into the broader realm of IP-based production workflows. As the industry moves toward full IP production (IPMX, NMOS, etc.), AES67 compatibility ensures that audio infrastructure will integrate seamlessly with video and data networks being deployed in modern broadcast and media environments.

Cost-Effectiveness Over the Total Ownership Cycle

While the upfront cost of AES67-compliant hardware can be comparable to proprietary alternatives, the total cost of ownership (TCO) skews heavily in favor of AES67 over multiple years. Lower training overhead is one factor: because AES67 leverages standard networking concepts (Ethernet, IP, UDP, RTP), IT and AV staff can manage the audio network using familiar tools like Wireshark, SNMP, and network switch configs. Another factor is reduced spare parts inventory—one brand of AES67-compliant microphone preamp can be swapped for another in a pinch without reconfiguring the entire system. Additionally, the avoidance of proprietary licensing fees (some AoIP systems require per-node licenses for audio channels) can result in significant savings as channel counts grow. For a 128-channel installation, per-node licensing fees from certain vendors can exceed $15,000 over five years, a cost entirely eliminated with AES67-native equipment. Finally, when upgrading a facility, AES67-compatible devices can be moved between locations or repurposed for different applications, extending their useful life well beyond a single installation.

Built-in Redundancy and Resilience

Future-proof audio infrastructure must also be fault-tolerant. AES67 directly supports redundant audio streams per SMPTE ST 2022-7, also known as hitless seamless protection switching. This standard enables a receiver to accept two identical audio streams from different network paths and seamlessly switch between them in the event of packet loss or a switch failure. Implementing ST 2022-7 requires a network with diverse paths (typically two separate switches or subnets) and endpoints that support dual-stream reception. Many AES67-compliant devices from manufacturers like Lawo, DHD, and Klotz offer this capability as a built-in feature, making it possible to achieve broadcast-grade reliability without a proprietary redundancy scheme. Organizations that architect their AES67 network with ST 2022-7 from the outset gain a level of resilience that protects critical on-air and live event operations against single points of failure.

Case Study: Broadcasting Transition to IP with AES67

Consider a mid-market television station planning to upgrade its audio infrastructure. In the past, the station might have built a dedicated AES/EBU or MADI backbone, tying it to a specific router and console brand. Today, the station opts for AES67-compatible equipment: a console from Manufacturer A, intercom from Manufacturer B, and audio processing gear from Manufacturer C, all connected through a managed Ethernet network. When the station later adopts SMPTE ST 2110 for video transport, the audio infrastructure is already compatible—no additional gateway boxes required. This case exemplifies how AES67 de-risks technology transitions, aligns with emerging standards, and protects the audio portion of a larger capital investment.

Implementation Considerations for AES67 Networks

Network Infrastructure Must Meet Rigorous Requirements

AES67 is not a plug-and-play protocol for unmanaged networks. To achieve the sub-2 ms end-to-end latency and 0.1% packet loss tolerance mandated by the standard, the IP network must be designed with care. This includes using managed switches with IGMP snooping for multicast management, enabling PTP-aware boundary clocks or transparent clocks, and reserving adequate bandwidth (each 48 kHz, 24-bit audio channel consumes approximately 2.4 Mbps of network throughput for RTP overhead). Switches should also support jitter buffering, Quality of Service (QoS) based on DiffServ code points, and proper VLAN segregation to isolate audio traffic from data traffic. Specifically, the recommended DSCP marking for AES67 audio is EF (Expedited Forwarding, value 46), which should be prioritized above other traffic types. Organizations new to AoIP should engage network engineering expertise early, or consider adopting manufacturer-validated network topologies provided by companies like Audinate or RAVENNA. Investing in the network foundation is as crucial as the audio endpoints themselves—skimping on switches can negate all the benefits of AES67.

PTP Timing: The Heart of Synchronization

AES67 relies on Precision Time Protocol (PTPv2) to keep all devices locked to a common clock. In practice, the network must support either boundary clocks (BC) or transparent clocks (TC) to maintain timing accuracy across multiple switch hops. For installations spanning more than a few switches, a dedicated PTP grandmaster clock (e.g., a GPS-locked unit from Meinberg, Siemens, or EndRun) provides the most stable reference. The default PTP domain for AES67 is domain 0, but some devices allow configuration to domain 1 or other values to avoid conflicts with other services. A common pitfall is enabling PTP on ports that also handle heavy data traffic, which introduces timing jitter. Best practice is to use a dedicated VLAN for PTP messages and ensure that all switches in the chain are PTP-aware. Monitoring tools like the open-source ptp4l and pps (pulse per second) diagnostics can verify that offset errors stay below 1 microsecond—well within the AES67 tolerance.

Training and Skill Development for Staff

AES67 adoption often forces a convergence of AV and IT roles. Technical staff must understand concepts such as multicast addressing, PTP synchronization, and network latency measurement. To future-proof an audio infrastructure, organizations should invest in training for engineers and technicians. Resources include AES67 certification programs, vendor-specific AoIP training (e.g., from Audinate, RAVENNA, or Lawo), and courses in standard networking (Cisco CCNA, CompTIA Network+). Cross-training AV personnel in networking fundamentals reduces troubleshooting time and enables more efficient system expansions. Furthermore, as the standard evolves (e.g., AES67-2018 added support for redundant streams per SMPTE ST 2022-7), ongoing education ensures that staff can take full advantage of new features without costly third-party support contracts.

Integration with Legacy Systems and Future Upgrades

Most existing facilities have some form of legacy audio infrastructure—analog patchbays, Dante endpoints, or AES3 digital connections. AES67 integration can be achieved through converters and gateways. For example, a Dante-to-AES67 bridge (like an Audinate DVS virtual sound card or a hardware bridge from Luminex) can bring legacy Dante devices into an AES67 stream. Similarly, AES3 over IP can be accomplished using devices from companies like Digigram or DirectOut. When planning an upgrade path, prioritize endpoints that offer native AES67 support, and use converters only as transitional tools. The long-term goal should be to minimize bridging points, as each conversion introduces latency and potential failure points. A phased approach—upgrading one room or one function at a time—allows the organization to validate AES67 performance before committing fully.

Testing and Validation Before Deployment

Even with certified AES67 compliance, real-world interoperability can be nuanced. Different manufacturers implement the standard with varying degrees of deviance or additional features. For example, some devices support only 48 kHz sample rate, while others support 96 kHz; some require PTPv2 domain 0, while others can operate on domain 1. To avoid costly surprises, organizations should conduct thorough testing in a lab environment before deploying gear in critical production. Tools like the AES67 Analyzer (available from AES) or network analysis tools can verify compatibility. Requesting interoperability matrices from manufacturers and consulting with systems integrators who have hands-on experience with multiple brands is also advisable. Remember that AES67 is a baseline—specific workflows (e.g., low-latency monitoring for live sound) may require additional configuration that goes beyond the standard.

AES67 in the Broader AoIP Ecosystem: Comparisons and Synergies

AES67 vs. Dante vs. Ravenna vs. Q-Lan

Dante, developed by Audinate, is the dominant AoIP protocol in installed sound and recording studio environments. It offers plug-and-play simplicity and proprietary management tools like Dante Controller. However, Dante is a closed standard—only Audinate-licensed chipsets support it. Ravenna, on the other hand, is an open standard built entirely on AES67 and is often used in ALCNetworks tools. Q-Lan, from QSC, adds third-layer control and integrates with Q-SYS processing ecosystem. The key point is that AES67 is not a competitor to these protocols but rather a common language that enables them to interoperate. Many Dante devices now include an AES67 mode activated through the device’s web interface; Ravenna devices are inherently AES67-compatible. Q-SYS also supports AES67 streams through its Core processor. Organizations should not feel forced to choose one protocol universally. Instead, they should select best-in-class equipment and use AES67 as the interoperability bridge between protocol islands. This heterogeneous approach future-proofs the infrastructure because no single vendor’s roadmap can dictate the facility’s capabilities.

The Role of AES67 in SMPTE ST 2110 and IPMX

SMPTE ST 2110 is the standard for professional media over IP networks, covering video (primary), audio, and ancillary data. The audio component (ST 2110-30) is directly based on AES67, adding payload identifier and channel mapping metadata. For broadcasters and media companies moving toward all-IP infrastructure, AES67 compatibility ensures that the audio portion of the ST 2110 stream is fully compliant. Additionally, the AIMS (Alliance for IP Media Solutions) and IPMX (a set of profiles for pro AV over IP) both incorporate AES67 as the mandatory audio transport. This means investment in AES67 today aligns with the trajectory of professional video-over-IP standards. As event venues and corporate AV adopt IPMX for cost-effective IP distribution, AES67 will be the audio backbone. Organizations that already have AES67 infrastructure will have a head start in deploying these emerging standards without forklift upgrades.

Future-Proofing Strategy: A Practical Roadmap

Audit Current Infrastructure and Identify Legacy Constraints

Begin by documenting all current audio endpoints, cabling, routing, and control systems. Highlight points where proprietary protocols create dependencies. For example, if you have a Dante-only console that must stay in place for budget reasons, plan to add an AES67 bridge to enable cross-protocol communication. Similarly, identify any coaxial or analog interconnect that could be replaced by a single Ethernet cable carrying multiple channels. This audit will reveal low-hanging fruit for IP conversion and potential bottlenecks.

Establish a Network Standard That Supports AES67

Work with an AVoIP-savvy integrator to design a network topology that prioritizes low jitter, multicast efficiency, and PTP synchronization. Choose managed switches from vendors with proven AoIP support (Cisco, Arista, Netgear M-series, or Luminex). Implement a dedicated VLAN for AES67 traffic or use a converged network with strict QoS policies. Document the switch configuration as a template for future expansions. Standardizing on a single switch model or family simplifies training and spare parts inventory. Also consider deploying a PTP grandmaster clock (either a GPS-locked device or a software grandmaster) to provide a stable time reference across the facility.

Select AES67-Certified Equipment with Forward Compatibility

When purchasing new audio gear, prioritize certifications from the AES67 Alliance or explicit manufacturer claims of AES67 compliance. Look for support for redundant streams (ST 2022-7 hitless switching) and up to 96 kHz sample rates to future-proof for high-resolution audio. Prefer devices that offer both native AES67 and a proprietary control protocol (e.g., Dante or RAVENNA) so you can decide later which management interface to use. Review the manufacturer’s firmware upgrade policy—devices that allow field-upgradeable firmware extend the device’s useful life as the standard evolves.

Invest in Monitoring and Management Tools

Network monitoring for AoIP is non-negotiable. Deploy tools like Wireshark with the AES67 dissector, or use commercial software like Audinate’s Dante Domain Manager (for mixed environments) or Lawo’s HOME management platform. These tools can alert operators to PTP offset errors, packet loss, or bandwidth contention before they cause audible glitches. Automated scheduling of redundant streams and automatic failover should be tested regularly. Management visibility into the audio network is the control plane that ensures the infrastructure remains future-proof as loads change.

Plan for Phased Migration with Minimal Production Disruption

Divide the facility into zones (e.g., Studio A, Control Room, Master Control, Post-Production). Migrate one zone at a time, using a temporary bridge to maintain interoperability with legacy zones during transition. For critical installations (e.g., live broadcast), have a rollback plan and test the AES67 system extensively during low-traffic periods. Keep legacy cabling and equipment in place as spares until the new system demonstrates stability over several months. This phased approach de-risks the investment and allows the team to gain confidence with the technology gradually.

AES67 and the Future of Immersive Audio

As immersive audio formats like Dolby Atmos and MPEG-H become standard across cinema, broadcast, and streaming, the transport infrastructure must support high-channel-count, low-latency delivery of object-based audio. AES67’s ability to carry any PCM stream makes it an ideal carrier for object audio metadata, which can be embedded in the RTP header extensions or sent as ancillary data. In practice, AES67 is already used in professional Atmos mixing rooms where the renderer (a Dolby DP590 or DP600 series) outputs up to 128 audio channels over IP to power amplifiers. These systems rely on AES67 to maintain deterministic timing between the renderer and the speaker array, ensuring precise localization of sound objects. Looking ahead, the convergence of AES67 with the Audio Definition Model (ADM) and Broadcast Wave Format (BWF) will simplify the exchange of immersive content between facilities. Investing in AES67 today prepares an organization for the immersive audio workflows that will dominate the next decade.

Conclusion: AES67 as the Foundation for Long-Term Audio Value

AES67 is not just another technical standard—it is the bedrock upon which a vendor-neutral, scalable, and adaptable audio infrastructure can be built. By prioritizing interoperability, reducing dependency on proprietary ecosystems, and aligning with emerging media-over-IP standards, AES67 directly addresses the core concerns of organizations investing in audio infrastructure today. The upfront effort to design and deploy an AES67-compliant network pays dividends through lower total cost of ownership, enhanced flexibility to adapt to new workflows, and a clear upgrade path to future IP production environments. As the audio industry converges with IT and video realms, AES67 ensures that your audio investment remains a strategic asset rather than a legacy liability. For any organization serious about future-proofing its audio infrastructure, adopting AES67 is not merely an option—it is a prudent, forward-thinking necessity.

External Resources:
- AES67 Official Standard Document
- Audinate: Understanding AES67 for Dante Users
- RAVENNA Network: Open Standard AoIP Based on AES67
- SMPTE ST 2110 Standards Suite
- Q-SYS AoIP and AES67 Support Overview
- AIMS Alliance for IP Media Solutions