Understanding AES67 and Its Role in Modern Audio Networks

In today's broadcast and audio production environments, the need for seamless integration across multiple vendors is more critical than ever. AES67, an interoperability standard for high-performance audio-over-IP networks, offers a solution to this challenge. Implementing AES67 allows diverse audio equipment from different manufacturers to communicate effectively, creating a unified and flexible audio network. As broadcast facilities, live sound venues, and recording studios continue to transition from traditional point-to-point analog or digital audio connections to IP-based infrastructures, AES67 has emerged as a foundational technology that bridges the gap between proprietary ecosystems.

What is AES67?

AES67 is an open standard developed by the Audio Engineering Society to facilitate interoperability among various audio-over-IP systems. It defines a set of guidelines for streaming audio over IP networks, ensuring compatibility between devices from different vendors. AES67 supports high-quality, low-latency audio transmission, making it ideal for broadcasting, live sound, and other professional audio applications. The standard was first published in 2013 and has since undergone revisions to address evolving network requirements and deployment scenarios.

At its core, AES67 specifies several critical aspects of audio networking: the transport protocol (RTP over UDP/IP), the synchronization mechanism (IEEE 1588 Precision Time Protocol or PTP), the audio format (linear PCM at various sample rates and bit depths), and the session description format (SDP). By standardizing these elements, AES67 enables devices that support it to discover, connect to, and exchange audio streams with minimal configuration overhead. This interoperability extends across major audio-over-IP platforms including Dante, Livewire, RAVENNA, and Q-LAN, making AES67 a universal translator of sorts within the pro audio industry.

It is important to understand that AES67 is not a full networking protocol suite like Dante or RAVENNA. Rather, it is a "layer 2" interoperability mode that defines a common set of parameters that devices using different native protocols can adopt to communicate directly. This distinction means that while AES67-enabled devices can exchange audio streams, they may not support the full feature sets of their proprietary protocols when operating in AES67 mode. For many applications, this trade-off is acceptable given the significant benefit of cross-vendor compatibility.

Key Technical Specifications of AES67

The AES67 standard specifies the following technical parameters that all compliant devices must support:

  • Audio format: Uncompressed linear PCM audio with sample rates of 48 kHz, 96 kHz, or higher, and bit depths of 16, 20, or 24 bits.
  • Transport protocol: Real-time Transport Protocol (RTP) over UDP/IP using unicast or multicast transmission.
  • Synchronization: IEEE 1588-2008 Precision Time Protocol (PTPv2) for clock synchronization with a target accuracy of ±1 microsecond.
  • Packet timing: A packet time of 1 millisecond or less, ensuring low-latency transmission suitable for live applications.
  • Sample rates: Mandatory support for 48 kHz, with optional support for 96 kHz and other rates.

These specifications ensure that AES67 delivers broadcast-grade audio quality with deterministic latency, making it suitable for even the most demanding production environments. The use of PTPv2 for synchronization is particularly important, as it allows devices from different manufacturers to maintain sample-accurate alignment across the network.

Benefits of Implementing AES67

Vendor Interoperability

The primary benefit of AES67 is its ability to bridge proprietary audio-over-IP systems. In a typical broadcast facility, you might find a mixing console that uses Dante for its stage boxes and I/O racks, an intercom system that relies on RAVENNA, and a routing matrix that speaks Livewire. Without AES67, integrating these systems would require expensive format converters or dedicated bridging hardware. With AES67, each device can communicate directly, reducing complexity and cost while improving reliability. This interoperability extends to software-based audio processing tools, virtual mixing consoles, and DAWs that support AES67, enabling hybrid workflows that blend hardware and software resources.

Scalability

Traditional audio infrastructure, such as analog patch bays or MADI-based systems, imposes hard limits on channel counts and routing flexibility. AES67 decouples audio transport from physical connections, allowing you to scale your network as your needs grow. Adding new devices is often as simple as connecting them to the network and configuring the appropriate streams. Because AES67 operates over standard IP networks, you can leverage existing Cisco, Arista, or other managed switch infrastructure to build audio networks of virtually any size. This scalability is especially valuable for large-scale installations such as stadiums, convention centers, and multi-studio broadcast facilities where channel counts can reach into the hundreds or thousands.

Flexibility

AES67 allows you to use your existing IP infrastructure for audio transport, eliminating the need for dedicated audio cabling. This flexibility extends to remote production applications where audio can be routed over wide-area networks, enabling distributed workflows that were previously impractical. As broadcast operations increasingly adopt cloud-based production and remote contribution workflows, AES67 provides a standardized way to transport high-quality audio over internet connections. The ability to mix and match devices from different vendors also gives you the freedom to choose the best tool for each application without being locked into a single ecosystem. For example, you could use a Dante-enabled mixing console for live production while incorporating a RAVENNA-based intercom system for communications, with AES67 serving as the common language between them.

Future-Proofing

The broadcast and pro audio industries are moving steadily toward IP-based infrastructure. SMPTE ST 2110, which builds on AES67 for video transport, is becoming the standard for broadcast facilities worldwide. By implementing AES67 now, you position your facility to integrate with future equipment and standards more easily. Many manufacturers are committed to supporting AES67 in their products, and the standard is maintained by the Audio Engineering Society, ensuring its continued relevance. Additionally, the principles and protocols underlying AES67 align with broader IT networking standards, meaning that as network technology evolves, AES67 deployments can benefit from improvements in switch hardware, QoS mechanisms, and synchronization technologies.

Steps to Implement AES67

Assess Your Current Infrastructure

Before deploying AES67, conduct a thorough assessment of your existing network infrastructure. This involves several key considerations:

Bandwidth capacity: Each AES67 audio stream at 48 kHz with 24-bit depth consumes approximately 1.5 Mbps per channel for a stereo pair. A 64-channel system will require roughly 48 Mbps of dedicated bandwidth. Ensure your network switches and links have sufficient capacity to handle your anticipated channel counts without congestion.

Latency requirements: AES67 is designed to deliver sub-millisecond latency within a local network. However, factors such as switch fabric latency, cable distances, and the number of hops can affect overall latency. For live production applications, aim for end-to-end latency of less than 5 milliseconds. This typically requires a dedicated audio network or a converged network with robust Quality of Service (QoS) configuration.

Network topology: Use a star or leaf-spine topology with managed switches that support IGMP snooping, PTPv2 boundary or transparent clocks, and DiffServ QoS. Avoid daisy-chaining switches in critical audio paths, as this can introduce unnecessary latency and failure points.

Switch selection: Not all managed switches are suitable for AES67. Choose switches that are specifically tested for audio-over-IP applications. Major manufacturers such as Cisco, Netgear, Arista, and Luminex offer switches with documented support for AES67 and PTPv2. Enterprise-grade switches from these vendors typically provide the necessary features, but consumer-grade switches often lack the required QoS and IGMP capabilities.

Select Compatible Devices

When selecting equipment for your AES67 deployment, verify that each device explicitly supports AES67. Many manufacturers offer native AES67 support in their products, while others require firmware updates or add-on modules. Key product categories to consider include:

  • Mixing consoles: Brands such as Yamaha, Allen & Heath, SSL, and Lawo offer AES67 support on many of their digital consoles. For example, Yamaha's consoles with the Dante-MY16-AUD2 card support AES67 via firmware update.
  • Stage boxes and I/O racks: Devices like the Yamaha Rio series, Allen & Heath DX series, and Focusrite RedNet series can be configured to interoperate via AES67.
  • Intercom systems: Riedel, Clear-Com, and RTS offer AES67-compatible intercom solutions that integrate with other audio-over-IP systems.
  • Software solutions: DAWs and virtual mixers such as Reaper, QLab, and Waves SuperRack support AES67 through ASIO drivers or dedicated plugins. This enables software-based processing alongside hardware devices.
  • Network bridges and converters: For legacy devices, consider AES67 bridge units such as the Focusrite RedNet line or the Luminex GigaCore series that provide conversion between analog, digital, and AES67 formats.

Configure Network Settings

Proper network configuration is essential for a stable AES67 deployment. Key configuration steps include:

IP addressing: Assign static IP addresses to all AES67 devices. Use a dedicated subnet for audio traffic to simplify management and troubleshooting. Avoid using DHCP for critical audio devices unless your DHCP server provides persistent address assignments.

Multicast groups: AES67 uses multicast for stream transmission. Configure IGMP snooping on your switches to ensure that audio streams are only forwarded to ports that have requested them. Over-subscription of multicast groups can lead to bandwidth exhaustion, so plan your stream topology carefully.

Quality of Service (QoS): Configure DiffServ to prioritize audio traffic. Assign AES67 traffic to the CS4 (Class Selector 4) or EF (Expedited Forwarding) DSCP values as recommended by the standard. Implement strict priority queuing on switch egress ports. Ensure that other network traffic such as file transfers, web browsing, and administrative traffic does not compete with audio flows for bandwidth.

PTP configuration: IEEE 1588 PTPv2 is critical for synchronization. Designate a grandmaster clock, typically a device with a stable oscillator or GPS reference. Most managed switches can be configured as boundary clocks or transparent clocks, which improves PTP accuracy across larger networks. Proper PTP configuration requires careful attention to the clock class, priority settings, and the type of PTP clock used.

Test Interoperability

After configuration, conduct thorough interoperability tests between devices from different vendors. This involves sending test tones or program audio between pairs of devices and verifying that the audio arrives with correct timing, sample accuracy, and no artifacts. Use tools such as phase correlation meters and null tests to detect any issues. Pay special attention to:

  • Sample rate conversion: While AES67 devices typically operate at 48 kHz, check that sample rate converters are properly configured when mixing devices with different native sample rates.
  • Stream discovery: Verify that devices can discover and connect to AES67 streams from other manufacturers. Some devices may require manual stream configuration via web interfaces or control software.
  • Redundancy: If your deployment uses redundant networks (e.g., ST 2022-7 or similar), test failover scenarios to ensure seamless audio continuity during network interruptions.

Implement Monitoring and Management

AES67 networks require ongoing monitoring to ensure stable operation. Deploy tools that provide visibility into network health, including:

  • Bandwidth utilization: Monitor switch port utilization to ensure that audio traffic stays within capacity limits.
  • PTP synchronization status: Many devices report PTP clock offset and jitter. Monitor these metrics to detect synchronization drift that could cause audio glitches.
  • Packet loss and jitter: Use tools like Wireshark with AES67-specific dissectors or dedicated audio network monitoring software from vendors such as Dante Controller, RAVENNA Manager, or Audinate's Dante Domain Manager.
  • Logging and alerting: Configure SNMP traps on your switches to alert you to link flaps, high error rates, or QoS policing events. Consider using a network monitoring platform such as PRTG, Nagios, or Zabbix with AES67-specific sensors.

Challenges and Solutions

Network Configuration Complexity

AES67 requires a solid understanding of IP networking principles, including multicast routing, QoS mechanisms, and PTP synchronization. Many audio engineers have limited experience with these technologies, leading to configuration errors that cause audio dropouts, excessive latency, or synchronization failures. The solution is to invest in training for your technical staff. Many manufacturers offer training programs and certifications for their audio-over-IP systems. Additionally, consider hiring a network integrator with experience in AES67 and ST 2110 deployments for larger installations. Online resources such as the Audio Engineering Society's AES67 documentation and the IEEE 1588 standard provide detailed technical guidance.

Device Compatibility Issues

While AES67 is an interoperability standard, not all implementations are created equal. Some devices may support AES67 but with limited stream counts, restricted sample rates, or proprietary discovery mechanisms. In other cases, firmware bugs or implementation differences can cause subtle incompatibilities. To address these issues, always verify vendor support for AES67 before purchasing equipment. Keep devices updated with the latest firmware from the manufacturer. When encountering compatibility issues, consult the vendor's support team and refer to the AES67 interoperability test results published by some manufacturers and industry organizations. The AES Technical Committee on Audio over IP maintains resources and interoperability testing documentation.

Latency Management

Low latency is one of the primary advantages of AES67, but achieving consistent sub-millisecond latency requires careful network design. Packetization time, switch forwarding delay, and PTP synchronization accuracy all contribute to end-to-end latency. For most broadcast and live sound applications, a target of 1-3 milliseconds is achievable with properly configured equipment. To manage latency effectively, use switches with low and consistent switching delay, configure PTP boundary clocks to minimize clock jitter, and select devices that support a 1-millisecond packet time. For wide-area or cloud-based AES67 deployments, higher latency may be acceptable, but always test with your specific network path to determine the achievable performance.

Bandwidth Planning

AES67 traffic at 48 kHz with 24-bit depth uses approximately 1.5 Mbps per stereo pair. However, this figure can increase with higher sample rates or redundant streams. In large-scale systems with hundreds of streams, bandwidth consumption can quickly exhaust the capacity of 1 Gbps links. Plan your network to provide adequate headroom for peak traffic. Use link aggregation (LAG) or move to 10 Gbps or 25 Gbps uplinks for spine switches in larger deployments. Always account for multicast replication when streams are received by multiple devices on separate switch ports. The simplest way to project bandwidth needs is to use the formula: total bandwidth = (number of audio channels / 2) × 1.5 Mbps, then double that for safety margin.

Real-World Use Cases

Multi-Vendor Broadcast Facility

A television station in Europe implemented AES67 to integrate a Lawo audio console (Dante-based) with a Riedel intercom system (RAVENNA-based) and a network of Axia Livewire nodes. Previously, each system operated in isolation with separate cabling and format converters. After AES67 deployment, the station achieved seamless audio routing between all three systems, reduced latency by 30%, and eliminated the rack of format converters that had been required for interconnection. The facility now uses a single IT network for both audio and control traffic, managed through a unified monitoring platform.

Live Performance Venue

A major live music venue in the United States needed to integrate a Yamaha CL5 digital console with a set of Allen & Heath ME-1 personal mixers for the monitor system, while also feeding audio to a broadcast truck for live streaming. By enabling AES67 on the Dante-MY16-AUD2 cards in the Yamaha console and the AES67-compatible I/O racks from Allen & Heath, the venue routed all monitor mixes and broadcast feeds over a single network. The broadcast truck received a dedicated AES67 stream that was directly compatible with their ST 2110 infrastructure, eliminating the need for a separate broadcast feed and reducing setup time by 40%.

Distributed Education Campus

A university with multiple campus buildings deployed AES67 to connect lecture capture systems, recording studios, and live event spaces across a campus-wide IP network. By using AES67 bridges to connect legacy analog and MADI equipment, the university created a unified audio infrastructure that supports remote lecture recording, podcast production, and live event streaming. The network now handles over 200 simultaneous audio channels with sub-2-millisecond latency, and the system can be expanded to additional buildings without major infrastructure changes.

The professional audio industry continues to evolve AES67 and related standards. The emergence of SMPTE ST 2110 for broadcast video transport has driven broader adoption of AES67 as the audio layer, and many new broadcast facilities are being designed around ST 2110 from the outset. The Audio Engineering Society is also working on AES72, a standard for audio-over-IP discovery and connection management that will complement AES67 and improve the user experience for configuring multi-vendor networks. The ITU-T J.1426 standard further extends AES67 for contribution-grade audio transport over IP networks, providing even tighter performance guarantees.

Additionally, the rise of cloud production and remote workflows has accelerated interest in AES67 over WAN connections. Technologies such as RIST (Reliable Internet Stream Transport) and SRT (Secure Reliable Transport) are being combined with AES67 to deliver broadcast-quality audio over the public internet. The IETF RFC 8333 on RTP header extensions also provides mechanisms for carrying AES67-specific timing information over wider networks, improving synchronization accuracy across distributed deployments.

Conclusion

Implementing AES67 is a strategic move toward achieving a flexible, scalable, and vendor-neutral audio network. By understanding its standards, benefits, and implementation steps, professionals can create a resilient audio infrastructure that meets the demands of modern broadcast and production environments. AES67 enables seamless multi-vendor integration, reduces the need for proprietary bridging hardware, and provides a clear migration path toward IP-based audio transport. Whether you are designing a new facility or modernizing an existing one, AES67 offers a proven, standards-based approach to audio networking that will serve you well for years to come.

The key to a successful AES67 deployment lies in careful planning, thorough testing, and ongoing monitoring. Invest in proper network infrastructure, train your team, and stay current with firmware and standards updates. By doing so, you will unlock the full potential of IP-based audio networking and position your facility for future growth and innovation. As the broadcast and pro audio industries continue their transition to all-IP infrastructures, AES67 stands as a foundational technology that ensures different systems can work together efficiently, reliably, and at the highest quality.