Redefining Professional Audio Networks: The Case for AES67

For decades, audio engineers and system integrators navigated a world of dedicated point-to-point connections. Analog multicore snakes and digital protocols like MADI and ADAT served their purpose, but they introduced significant constraints in terms of distance, channel count, and routing flexibility. The transition to Audio over IP (AoIP) promised to solve these issues by leveraging standard Ethernet infrastructure. However, this transition initially created a new problem: a fragmentation of proprietary protocols. Dante, Ravenna, AVB (Milan), SoundGrid, WheatNet, and Q-LAN all offered compelling solutions, but they could not easily talk to one another. The industry needed a common language. AES67 emerged as that vital interoperability standard, enabling seamless communication between previously isolated AoIP ecosystems.

Whether you are mixing a Broadway musical, managing a live national broadcast, or deploying a permanent installation in a house of worship, understanding AES67 is essential for building flexible, scalable, and future-proofed audio networks. This guide explores the technical foundation of AES67 and its profound benefits for live sound and broadcast applications, offering practical insights for engineers and IT professionals alike.

What Is AES67? The Interoperability Layer for Professional Audio

AES67 is a standard for audio-over-IP interoperability developed by the Audio Engineering Society (AES). Formally published in 2013, its primary goal is straightforward yet ambitious: to enable high-performance audio streaming over IP networks between devices that might otherwise rely on incompatible native protocols. It is not a full replacement for comprehensive protocols like Dante or Ravenna, which provide rich management, discovery, and configuration features. Instead, AES67 functions as a common transport and synchronization profile.

Think of AES67 as the universal translator of the AoIP world. It allows a Dante-based mixing console to send audio to a Ravenna-based I/O rack, or an AVB-equipped digital signal processor to accept streams from a WheatNet audio network. It ensures that the fundamental requirements of professional audio—high channel counts, pristine quality, ultra-low latency, and robust synchronization—are met across different ecosystems. This capability has made AES67 the de facto interoperability standard for major manufacturers and broadcasters worldwide.

The Technical Pillars of the AES67 Standard

AES67 is technically a "profile" that selects specific parameters from existing IEEE and IETF standards to guarantee interoperability. Here are the four critical components that make AES67 work reliably in demanding production environments.

RTP Transport for Audio Data

AES67 uses the Real-time Transport Protocol (RTP) to encapsulate and deliver uncompressed PCM audio data. RTP is a widely adopted standard for transporting real-time media over IP networks. The standard mandates support for linear PCM audio with sample rates of 48 kHz and 96 kHz, and bit depths of 16 and 24 bits. By using a standardized payload format (L16/L24), any AES67-compliant receiver can decode and play the audio stream from any compliant sender. This ensures that a stream originating from a Dante stage box can be decoded by a Ravenna processor without any transcoding or additional hardware.

PTPv2 for Precision Clock Synchronization

Accurate timing is the backbone of any digital audio system. To achieve sample-accurate alignment between multiple devices across a network, AES67 employs the Precision Time Protocol (PTP), specifically IEEE 1588-2008 (PTPv2). This protocol allows all devices on the network to synchronize to a grandmaster clock with sub-microsecond accuracy. This eliminates clock drift and sample slippage, ensuring that multiple microphones and loudspeakers remain phase-coherent. Phase coherence is non-negotiable in live sound reinforcement and broadcast production—without it, comb filtering and audible artifacts degrade the mix. PTPv2 provides the timing foundation that makes large-scale networked audio possible.

SAP for Basic Session Discovery

While many proprietary protocols carry their own rich discovery mechanisms, AES67 provides a baseline using the Session Announcement Protocol (SAP). SAP allows a device to advertise the existence of an audio stream and its connection parameters (IP address, port, sample rate, etc.) to other devices on the network. While less sophisticated than full node management tools like Dante Controller or Ravenna's web interface, SAP ensures that devices from different manufacturers can at least find and connect to each other's streams without requiring manual IP entry for every channel. For more advanced management, AES67 streams can also be manually configured or managed through the native control software of the respective protocol. In practice, many engineers use SAP for initial discovery and then switch to manual configuration for critical channels.

QoS for Guaranteed Delivery

Standard Ethernet networks are susceptible to congestion caused by data bursts, web traffic, or file transfers. To ensure that real-time audio streams are not disrupted by other network activity, AES67 mandates specific Quality of Service (QoS) markings based on Differentiated Services Code Point (DSCP). Audio data is prioritized over standard data traffic, ensuring deterministic delivery with minimal jitter and packet loss. This reliance on standard IT QoS mechanisms means that AES67 works reliably on well-managed networks. It also means that network administrators must correctly configure switches to trust and honor these markings—a common point of failure in first-time deployments. When properly implemented, QoS guarantees that audio packets arrive on time, every time.

Why AES67 Matters: Bridging the Fragmented AoIP Landscape

Before AES67, the professional audio industry faced a "Tower of Babel" scenario. A studio equipped with a Dante console could not directly record into a Ravenna-based DAW interface. A live sound rental house standardized on AVB might struggle to integrate a client's legacy SoundGrid processing rig. This lack of interoperability created significant friction, increased costs, and limited flexibility. System integrators had to purchase media converters or use analog patch bays, adding expense, latency, and potential failure points.

AES67 solves this problem by providing a lowest common denominator of high-quality audio transport. It is not designed to replace Dante, Ravenna, or AVB. Instead, it allows these protocols to bridge their differences. Most major manufacturers of professional audio networking equipment, including Yamaha, Focusrite, L-Acoustics, Biamp, SSL, and Lawo, include an "AES67 mode" in their devices. When activated, the device can send and receive standard AES67 streams alongside its native protocol. This dual-mode capability is now a standard feature in many network I/O boxes, mixing consoles, and DSP units.

This standardization empowers system integrators and audio engineers to select the best tool for each specific task. You can use the rich management features of Dante for your microphone racks and console, utilize the deterministic scheduling of AVB for your loudspeaker network, and bridge them together via AES67. The result is a best-in-class, hybrid system that avoids the constraints of a single vendor ecosystem while maintaining high performance and reliability. For broadcasters, the adoption of AES67 within the SMPTE ST 2110 suite means that audio interoperability is no longer an option—it is a requirement.

Critical Benefits of AES67 for Live Sound Reinforcement

In the fast-paced world of live sound, reliability, latency, and flexibility are paramount. AES67 delivers on all fronts, making it an indispensable tool for touring professionals, installers, and venue operators. Below are the key advantages that directly impact live production workflows.

True Interoperability in a Multi-Vendor World

A festival or concert featuring many different acts often involves a changeover of equipment between sets. With AES67, a festival can maintain a fixed stage rack and loudspeaker system while allowing each touring engineer to connect their preferred console. Whether the engineer uses a Yamaha CL5 (Dante native), a DiGiCo SD7 (Optocore or MADI, bridged to AES67), or an Avid S6L (Dante native), the stage rack can accept any of these consoles seamlessly if it is AES67-capable. This drastically reduces changeover time and the risk of patching errors.

AES67 enables a touring engineer to walk in with their console, patch it into the house network via a single Cat6 cable, and instantly access all stage inputs and returns, regardless of the brand or native protocol of the house infrastructure.

Beyond festivals, this feature is equally valuable in Broadway theaters and touring musical productions, where equipment is swapped rapidly between matinee and evening performances. By standardizing on AES67 as a common transport, venues future-proof their infrastructure against varying rider requirements.

Uncompromising Low Latency for Live Monitoring

Latency is the enemy of live sound. In-ear monitor systems and live microphones require round-trip latency well under 10 milliseconds, and ideally under 2–3 milliseconds. AES67 is engineered for this. The standard supports extremely low packet times, including 125 microseconds (125 µs) and 250 microseconds. When combined with the low inherent latency of PTP-synchronized networks, AES67 can deliver end-to-end latency that rivals traditional analog snakes or MADI connections.

This allows sound engineers to place microphones on stage, process them at Front of House, and send them to in-ear monitors without any perceivable delay. The audio remains tight and natural, preserving the feel of the performance for the artists on stage. In applications like acoustic jazz concerts or spoken-word theater, where even 5 milliseconds of latency can be disruptive, AES67's ability to operate at sub-millisecond packet intervals is critical. Pairing AES67 endpoints with low-latency switches and careful network design ensures that latency remains imperceptible.

Scalability and Redundancy for Large Deployments

Large-scale live events, such as stadium tours and outdoor festivals, require enormous channel counts and robust redundancy. AES67 networks can scale to hundreds of channels of bidirectional audio over standard Gigabit or 10Gb Ethernet. Furthermore, AES67 supports SMPTE ST 2022-7, which provides hitless seamless protection switching. By sending two identical copies of the audio stream over redundant paths (e.g., Primary and Secondary networks), the system can instantly recover from a switch failure or a cut cable with zero audio dropouts. This level of reliability is crucial for broadcast feeds and headline festival acts where any audio loss is unacceptable.

In practice, system designers often implement redundant AES67 networks using separate VLANs and physical paths. The Primary network carries the main audio, while the Secondary network carries an identical copy. If a switch port fails or a cable is disconnected, the receiving device seamlessly switches to the secondary stream without a glitch. This redundancy is now standard in large-scale installation venues such as sports arenas, convention centers, and houses of worship.

Transformative Advantages for Broadcast and Media Production

The broadcast industry is undergoing a massive transition from SDI-based infrastructure to IP-based production. AES67 is at the very center of this revolution, serving as the mandatory audio standard within the larger SMPTE ST 2110 framework. For broadcast engineers, understanding AES67 is no longer optional—it is a requirement for designing modern production facilities.

AES67 Is the Audio Standard for SMPTE ST 2110

SMPTE ST 2110 is the modern standard for transporting video, audio, and ancillary data over IP networks. The audio component, designated ST 2110-30, is specifically defined as AES67. This means that any facility built around ST 2110 requires AES67 for its audio transport. Broadcasters investing in IP-based routing, production switchers, and graphics systems are simultaneously investing in an AES67 audio backbone.

This convergence allows for seamless integration between the production environment and the wider audio ecosystem. A live sports broadcast truck running ST 2110 can directly receive program audio from an AES67-compliant stadium sound system or communicate with a remote studio equipped with Ravenna or Dante infrastructure. It breaks down the traditional walls between the "audio world" and the "video world," unifying them on a single, coherent IP network. This unification reduces equipment costs, simplifies cabling, and enables more flexible workflows, such as sharing audio metadata across departments.

Optimizing Remote and Distributed Production (REMI)

As broadcasters increasingly adopt Remote Production (REMI) workflows to reduce costs and travel requirements, AES67 provides a robust transport for high-quality audio over wide area networks (WANs). By leveraging standard IP infrastructure, audio from the venue can be encoded, transmitted, and decoded at a central production hub with the same low latency and fidelity as a local connection. AES67's compatibility with standard encryption and tunneling protocols (such as AES67 over Secure RTP or IPsec) ensures that high-value broadcast audio remains secure during transit.

For sports networks covering multiple live events simultaneously, REMI workflows rely on AES67 to carry clean feeds, mix-minus signals, and intercom audio from dozens of venues back to a central control room. The low latency of AES67 (often under 5 milliseconds over dedicated WAN links) allows directors to communicate with camera operators and commentators in real time. This combination of interoperability and low latency makes AES67 the preferred audio transport for next-generation remote production.

Reliability and Flexibility in the Control Room

Broadcast control rooms require absolute reliability and flexible routing. AES67 enables dynamic, patchless routing. Instead of physically re-patching a router, an engineer can route any audio source to any destination from a software control panel. This includes routing microphone feeds from the studio, program audio from the server, intercom signals, and mix-minus feeds. The open standard nature of AES67 also simplifies archiving, allowing broadcasters to easily record multi-track feeds to a DAW or storage server without worrying about proprietary format restrictions.

In large broadcast centers, this flexibility is essential. During a live news broadcast, an engineer might need to quickly route a satellite feed to an IFB system, while simultaneously sending a clean feed to an archive server. AES67 allows all these routes to exist concurrently on the same network. Moreover, because AES67 uses standard RTP streams, integration with media asset management systems is straightforward. Broadcasters can record each channel as a separate WAV file, enabling offline editing and post-production without format conversions.

Implementing AES67: Network Design and Configuration Best Practices

While AES67 simplifies interoperability, it demands a well-engineered network to function correctly. Successfully deploying AES67 requires careful attention to the underlying IT infrastructure. Many high-profile failures at trade shows or early adoption sites have been traced back to improper network configuration rather than issues with the standard itself.

Essential Network Infrastructure for AES67

AES67 is not designed for "plug-and-play" on a consumer-grade switch. It requires a managed network to ensure reliable delivery of time-sensitive audio data. Key requirements include:

  • Managed Switches with IGMP Snooping: Audio streams are multicast traffic. Without IGMP snooping, audio packets are flooded to every port on the network, overwhelming connected devices. IGMP snooping ensures that switches intelligently deliver streams only to the ports that have requested them. Most enterprise-grade switches from manufacturers like Cisco, Arista, and Netgear support IGMP snooping.
  • PTP Boundary or Transparent Clocks: For larger networks spanning multiple switches, PTP accuracy can degrade due to queuing delays. High-quality Ethernet switches equipped with PTP boundary clock or transparent clock capabilities are essential for maintaining the sub-microsecond synchronization required by AES67 across complex topologies. This is particularly important in broadcast facilities where switches are located in different racks or even different rooms.
  • Quality of Service (QoS) Configuration: Switches must be configured to trust and prioritize the DSCP tags set by AES67 devices. Audio traffic (DSCP EF or CS7) must be placed in the highest priority queue to ensure it is delivered ahead of best-effort data traffic. Failure to configure QoS correctly is the single most common cause of audio dropouts in AES67 networks.
  • Sufficient Bandwidth: A single 48 kHz / 24-bit audio channel consumes roughly 1.5 Mbps of bandwidth. While this is minimal, a 128-channel system requires nearly 200 Mbps. Planning for sufficient headroom on your network backbone (typically 1 Gb or 10 Gb) is essential for avoiding congestion. Additionally, consider burst traffic from file transfers on the same network; dedicated VLANs for audio are highly recommended.

Configuring the Endpoints

Most professional audio devices include a dedicated "AES67 mode" or allow you to enable AES67 stream compatibility within their native software. Configuration typically involves selecting a PTP domain (to ensure all devices are synced to the correct master clock) and setting the desired packet interval (e.g., 1 ms for general use, 250 µs for ultra-low latency monitoring). Once the network is properly configured, enabling AES67 on the device is often as simple as choosing the target stream from an SAP list or manually entering the stream's IP address.

For larger systems, consider using a centralized PTP grandmaster clock (such as a dedicated GPS-disciplined oscillator) to provide the most accurate timing reference. Many broadcast facilities use PTP grandmasters that also provide NTP timing for other network services. When integrating AES67 with legacy digital consoles that only support MADI or ADAT, use bridges or converters that can translate between these protocols and AES67 without introducing additional latency.

Common Pitfalls and How to Avoid Them

Even with good planning, first-time AES67 deployments can encounter issues. Here are the most common challenges and their solutions:

  • PTP domain mismatch: All devices must be in the same PTP domain. If one device is set to domain 0 and another to domain 1, they will not synchronize. Always verify the domain setting on every device.
  • Unmanaged switches in the path: Even a single unmanaged switch can break PTP precision and QoS markings. Ensure every switch in the audio path is manageable and configured correctly.
  • Over-subscribed multicast: While IGMP snooping limits stream flooding, multiple streams can still exceed link capacity if multiple devices subscribe to different streams. Use multicast group management tools to balance load.
  • Incorrect clock source: Some devices allow manual selection of clock source. Ensure all devices are locked to the PTP grandmaster, not to an internal clock or another PTP clock that might drift.

To avoid these issues, always test your network with a dedicated analysis tool such as the Dante Controller or a specialized packet analyzer like Wireshark (with appropriate display filters for PTP and RTP). Many manufacturers provide free trial software to verify stream health before going live.

The Future of AES67 in Professional Media Networking

AES67 has firmly established itself as the baseline interoperability standard for professional audio. Its future is intrinsically linked to the broader adoption of IP-based media networks. As SMPTE ST 2110 continues to replace SDI in broadcast and Pro AV, AES67 will remain the bedrock audio transport. The recent adoption of AES67 by the Advanced Media Workflow Association (AMWA) as part of the NMOS (Networked Media Open Specifications) suite further solidifies its role in IP-based studios.

Furthermore, the development of richer profiles built on top of AES67, such as the Milan protocol (which adds deterministic scheduling and plug-and-play configuration over AVB), demonstrates how the industry is building on this solid foundation. Even as new protocols evolve, they almost universally maintain AES67 compatibility to ensure they can participate in the larger networked audio ecosystem. For manufacturers, including AES67 support is no longer a differentiator; it is a baseline requirement for serving the professional market. As bandwidth and processing power increase, we can expect AES67 to support higher sample rates (such as 192 kHz) and more channels without significant changes to the standard itself.

Conclusion

AES67 is more than just a technical standard; it is the key that unlocks the full potential of Audio over IP. For live sound professionals, it offers the freedom to mix and match the best tools for the job without being locked into a single protocol. For broadcasters, it provides the mandatory, reliable audio backbone required for modern IP-based production workflows. By understanding and leveraging AES67, audio professionals can build systems that are more flexible, more scalable, and ultimately more reliable than ever before.

Whether you are designing a permanent installation in a performing arts center, managing a touring audio network for a world tour, or modernizing a broadcast facility for the IP age, AES67 is the essential tool that ensures your audio network can connect with the world. Embrace the standard, invest in proper network infrastructure, and you will benefit from years of trouble‑free interoperability.

For further reading, consult the official AES67 standard document and the SMPTE ST 2110 series. Additionally, the Audinate AES67 white paper provides practical guidance on integrating AES67 with Dante networks.