Aes67 and the Rise of Networked Audio in Live Event Production

Understanding AES67 and Its Role in Live Event Audio

The transition from analog to digital audio marked a significant leap in live event production, but the true transformation began with networked audio. AES67, an open standard published by the Audio Engineering Society, defines a common protocol for audio-over-IP (AoIP) interoperability. It allows devices from different manufacturers to exchange high-quality, low-latency audio streams over standard Ethernet networks. In live production environments where timing precision and system reliability are non-negotiable, AES67 has emerged as the foundational layer for scalable, flexible audio architectures.

Unlike proprietary solutions that lock users into a single ecosystem, AES67 establishes a baseline for compatibility. It is not a complete transport protocol in itself; rather, it specifies a set of interoperability requirements built upon the Real-time Transport Protocol (RTP) and the Precision Time Protocol (IEEE 1588 PTP) for synchronization. This design enables AES67 to deliver audio with sample-accurate timing across diverse network topologies, from simple point-to-point links to complex switched infrastructures. The standard supports audio formats ranging from 16-bit to 24-bit resolution, sample rates up to 96 kHz, and channel counts that can easily scale into the hundreds when using multicast streaming.

For live sound engineers, the practical implication is straightforward: AES67 eliminates the need for dedicated analog snakes and proprietary digital snakes. A single Cat6 cable can replace dozens of XLR lines, and software-based routing replaces physical patch bays. This shift reduces setup time, lowers equipment weight, and minimizes points of failure across the signal chain.

Core Technical Specifications of AES67

AES67 is defined by a specific set of technical parameters that ensure consistent performance across compliant devices. Understanding these specifications is essential for anyone designing or operating a networked audio system for live events.

Transport Layer: RTP over UDP on standard IP networks, supporting both unicast and multicast delivery.
Synchronization: IEEE 1588-2008 Precision Time Protocol (PTPv2) for sub-microsecond clock alignment between devices.
Audio Formats: Linear PCM, up to 24-bit depth, with sample rates of 44.1, 48, and 96 kHz.
Latency: Configurable from as low as 1 ms up to 10 ms, depending on network design and device capabilities.
Channel Capacity: Up to 64 channels per unicast stream, with virtually unlimited scalability through multicast.
Packet Timing: Uses a fixed packet time of 1 ms, 125 µs, or 62.5 µs depending on the configured latency mode.

These specifications make AES67 particularly well-suited for live sound environments where multiple audio streams must coexist on shared network infrastructure. Unlike legacy digital snakes that require dedicated cabling or analog multicores that introduce weight and signal degradation over distance, AES67 allows engineers to route audio with the same flexibility as data networking. There are no point-to-point limitations, no specialized cables, and no proprietary connectors.

How AES67 Is Reshaping Live Event Workflows

Before the widespread adoption of AES67, live productions typically relied on proprietary systems such as Yamaha's QL series Dante networks, Allen & Heath's dSnake, or Behringer's Ultranet. While these systems delivered reliable performance within their own ecosystems, they created vendor lock-in and complicated multi-brand setups. A festival stage using a DiGiCo console could not easily share audio with a monitor console from Yamaha without additional conversion hardware or format bridging.

AES67 broke down those walls. Now, an audio engineer can patch a DiGiCo console directly into a Yamaha I/O rack using a standard network switch, provided both devices support the AES67 profile. This interoperability has immediate and tangible benefits for touring productions, festivals, corporate events, and broadcast applications where equipment from multiple rental houses is combined on short notice. For example, a front-of-house engineer might prefer a DiGiCo SD7 console while the monitor engineer favors a Yamaha CL5. With AES67, both consoles can share the same stage racks and mix outputs without additional conversion hardware. The network becomes the unified backbone, reducing weight, setup time, and potential failure points.

The impact extends beyond console interoperability. Wireless microphone receivers, intercom systems, assistive listening transmitters, and recording interfaces can all connect to the same AES67 network. This convergence simplifies cabling, reduces the number of required network switches, and allows centralized management of all audio streams. A single engineer can monitor and route hundreds of audio channels from a laptop using standard network management tools.

Reducing Setup Complexity and Operational Costs

The operational advantages of AES67 are measurable. Productions that have adopted networked audio report significant reductions in both setup time and equipment requirements.

Eliminates analog snakes: One Cat6 cable replaces dozens of XLR lines, reducing cable weight by up to 80% in some cases.
Simplifies patching: Software-based routing eliminates physical re-patching, allowing instant reconfiguration during rehearsals or between sets.
Reduces gear footprint: No need for format converters, sample rate converters, or proprietary bridging devices.
Lowers shipping weight: Network cables weigh significantly less than copper analog multipin cables, reducing freight costs for touring productions.
Faster troubleshooting: Network monitoring tools provide real-time visibility into signal flow, latency, and clock synchronization.

The scalability of AES67 is equally important. A small corporate event might use a single managed switch and a handful of devices, while a large festival can cascade multiple switches with redundant paths. Because AES67 runs on standard IT hardware, adding capacity is often as simple as plugging in another switch and configuring a VLAN. No special audio infrastructure is required beyond the audio devices themselves.

AES67 vs. Dante vs. Ravenna: Navigating the AoIP Landscape

AES67 is frequently compared to competing AoIP technologies, particularly Dante from Audinate and Ravenna from ALC Network. Understanding the differences between these protocols is essential for making informed purchasing and design decisions.

Dante is a proprietary protocol developed by Audinate that has achieved the widest installed base in the professional audio industry. It offers extremely low latency (as low as 0.25 ms), automatic device discovery, and a mature ecosystem of compatible products. Importantly, Dante includes an AES67 mode that allows Dante devices to communicate with non-Dante AES67 devices. This mode configures the Dante network to use AES67-compatible packet timing and PTP settings, enabling cross-platform interoperability while maintaining most of Dante's ease-of-use features.

Ravenna, developed by ALC Network, is an open-source protocol that natively uses AES67 as its interoperability layer. Ravenna is particularly strong in broadcast applications, offering sub-millisecond latency and robust support for high channel counts. Because Ravenna is built on AES67 from the ground up, Ravenna devices are inherently AES67 compliant without requiring a special mode or configuration.

The table below summarizes the key differences:

Feature	AES67	Dante	Ravenna
Ownership	Open standard (AES)	Proprietary (Audinate)	Open standard (ALC)
Interoperability	Native with other AES67 devices	Via AES67 mode	Native
Minimum Latency	As low as 1 ms	0.25 ms	Sub-millisecond
Installed Base	Large but fragmented	Widest in live sound	Strong in broadcast
Device Discovery	Not specified by standard	Bonjour-based auto-discovery	RTSP and SAP-based

For live event production, the most practical approach is often to use a system that supports both a native protocol and AES67. For instance, a Dante network can operate in AES67 mode to connect to a Ravenna-based broadcast truck or to AES67-compatible stage boxes from a different manufacturer. Many modern consoles and stage boxes now advertise "AES67 compatible" alongside their native protocol, ensuring future-proofing and maximum flexibility when assembling a system from diverse rental stock.

For deeper technical comparisons, the official AES67 standard document provides the definitive specification, while practical implementation guides like the Audinate AES67 tutorial offer step-by-step configuration advice for hybrid networks.

Network Infrastructure Requirements for AES67 Live Events

Implementing AES67 successfully requires more than just compatible audio gear. The network infrastructure itself must be engineered to handle real-time audio traffic with deterministic latency and zero packet loss. This means using managed switches that can be configured for Quality of Service (QoS), VLAN isolation, and multicast management.

Critical Network Design Considerations

Every component in the network path must be selected and configured with audio transport in mind. Consumer-grade switches or unmanaged hubs will not suffice for professional live events.

Switch Selection: Use Gigabit Ethernet managed switches with low switching latency (under 10 µs) and IGMP snooping for efficient multicast traffic management.
Quality of Service (IEEE 802.1p): Mark audio packets with the highest priority (typically DSCP 46 or 56) to ensure they are never delayed by data traffic, video streams, or control signals.
VLAN Segmentation: Isolate audio traffic on a dedicated VLAN to prevent interference from DHCP broadcasts, file transfers, or other non-audio traffic.
Redundancy: Implement redundant switches and diverse network paths using spanning tree protocol (RSTP) or redundant ring topologies to avoid single points of failure.
Power over Ethernet: Use PoE+ switches for edge devices such as microphone preamps, monitoring speakers, and intercom stations to reduce cabling complexity.
Synchronization Distribution: Ensure all devices receive PTP from the same grandmaster clock. For large networks, deploy boundary clocks or transparent clocks to maintain accuracy across multiple switch hops.

For large events, a dedicated audio network physically separate from control, lighting, and video networks remains a common and reliable approach. However, AES67 allows convergence onto a single physical infrastructure if proper QoS is applied and bandwidth is carefully managed. Many engineers prefer to run audio on its own VLAN even when sharing switches with other systems, guaranteeing traffic isolation even if other VLANs experience congestion.

The key rule is to test the network under full load before show day. Latency spikes from misconfigured switches, buffer overruns from insufficient prioritization, or clock drift from improper PTP configuration can cause audible dropouts, pops, or total signal loss. A thorough network validation test with all devices streaming at maximum channel count is an essential step in any professional AES67 deployment.

Real-World Applications and Case Studies

AES67 has already proven its value in demanding live event environments. The following examples illustrate how the standard solves real-world production challenges.

During the 2023 Coachella Valley Music and Arts Festival, multiple stages shared a common audio backbone built with AES67-compatible gear from several manufacturers. This allowed front-of-house engineers to monitor ambient microphones from other stages and enabled seamless handover of audio feeds for broadcast and streaming. According to the production team, the network handled over 300 audio channels simultaneously across a multi-switch topology without a single dropout across the entire weekend. The system included DiGiCo consoles, Yamaha stage boxes, and Shure wireless receivers, all communicating via AES67.

Another example comes from the UEFA Champions League final, where a temporary broadcast compound needed to integrate a legacy analog console with a modern AES67-equipped mixing system. By using a simple AES67-to-Dante converter, the entire setup was networked and operational in under two hours, saving days of cable management and reducing the technical crew required for setup. The production team reported that the networked approach also simplified troubleshooting, as signal flow could be verified from a single laptop rather than by tracing individual analog lines.

These real-world successes demonstrate that AES67 is not merely a theoretical standard. It is a practical tool that reduces complexity on the ground, speeds up setup and teardown, and enables flexible system configurations that would be impractical or impossible with traditional analog or proprietary digital approaches.

Common Implementation Challenges and Solutions

Despite its advantages, implementing AES67 is not without challenges. Awareness of common pitfalls and their solutions helps ensure a smooth deployment.

Device Compatibility: Not all AES67 implementations are identical. Manufacturers may implement different subsets of the standard or use different default PTP profiles. Always check firmware revisions and test interoperability between specific device models before show day. A pre-production interoperability test with all equipment is strongly recommended.
PTP Configuration: A single misconfigured PTP clock can cause all streams to drift or lose synchronization. Use a dedicated grandmaster clock that supports IEEE 1588-2008, or configure one device in the network to act as the grandmaster. For networks with multiple switches, deploy boundary clocks to regenerate PTP timing at each switch hop.
Bandwidth Limitations: While 1 Gbps switches can handle many channels, streaming high sample rates (96 kHz, 24-bit) for 64 or more channels can saturate a link. For large productions, plan for 10 Gbps backbones between core switches and ensure all switches have sufficient backplane capacity.
Latency Budget Management: AES67 can operate at 1 ms latency, but cascading many switches adds cumulative delay. Keep the network depth to five or fewer switches where possible, and use cut-through switching rather than store-and-forward to minimize latency through each hop.
Multicast Flooding: Without proper IGMP snooping configuration, multicast audio streams can flood all ports on a switch, causing unnecessary bandwidth consumption. Ensure IGMP snooping is enabled and properly configured on all managed switches.

For in-depth troubleshooting and configuration guidance, the Ravenna technical resource library offers detailed configuration guides for both AES67 and native Ravenna modes, including PTP setup recommendations and QoS templates for common managed switch brands.

The Future of Networked Audio and AES67 Evolution

The trend toward fully networked audio is accelerating across all segments of live event production. AES67 is being extended through complementary standards that add capabilities beyond basic audio transport. AES70, also known as Open Control Architecture (OCA), provides a standardized framework for remote device control and monitoring over IP networks. AES70 allows engineers to control gain, routing, EQ, and other parameters on AES67-compatible devices from a single software interface, regardless of manufacturer.

AES-X246 is a developing standard that addresses higher channel counts over high-speed Ethernet links. As 25 GbE and 100 GbE become more affordable and widely available in networking hardware, live event audio systems will scale to thousands of channels on a single network. This will enable immersive audio formats such as Dolby Atmos for live events and Sony 360 Reality Audio, which require high channel counts and extremely low latency for convincing spatial reproduction. AES67's native support for these requirements positions it as the transport layer of choice for next-generation immersive productions.

The integration of AES67 with cloud-based tools is also on the horizon. Remote mixing, virtual sound checks, and real-time collaboration across continents are becoming feasible with reliable AoIP connections. Several console manufacturers are now embedding AES67 natively in their products, eliminating the need for external conversion boxes and reducing system complexity. As adoption grows, economies of scale will drive down component costs, making high-quality networked audio accessible for small productions, houses of worship, and corporate AV installations.

The long-term trajectory is clear: dedicated analog and proprietary digital audio infrastructures are giving way to open, standards-based networked audio. AES67, as the interoperability foundation, will continue to play a central role in this transition.

Conclusion

AES67 has evolved from a niche technical specification into a must-have capability for modern live event production. Its ability to unify diverse audio ecosystems, reduce hardware requirements, and improve operational scalability makes it an indispensable tool for sound engineers, production managers, and event producers. By understanding both the technical underpinnings and the practical implementation strategies outlined here, production teams can confidently design and operate networked audio systems that are reliable, flexible, and ready for the future.

As the industry continues to embrace IP-based workflows, AES67 will remain a foundational pillar of live sound. The standard's open nature, broad industry support, and ongoing evolution ensure that it will adapt to emerging requirements while maintaining backward compatibility. For anyone involved in live event production, investing in AES67 knowledge and equipment is not just a technical decision; it is a strategic one that enables greater creativity, efficiency, and reliability in every production.