Understanding the Basics of Aes67 Audio-Over-Ip Protocols for Modern Studios

The Rise of Audio-over-IP and the Role of AES67

Modern studios are rapidly transitioning from traditional point-to-point analog or digital audio connections to networked Audio-over-IP (AoIP) infrastructures. This shift allows for greater flexibility, reduced cabling, and the ability to route hundreds of channels over a single Ethernet cable. Among the many AoIP standards, AES67 has emerged as a critical interoperability layer that ensures devices from different manufacturers can communicate reliably. Understanding AES67 is no longer optional for audio engineers and system integrators—it is a foundational skill for building scalable, future-proof studio environments.

AES67, formally known as AES67-2018 (the current revision), is an open standard developed by the Audio Engineering Society. It was first published in 2013 and updated in 2018 to clarify timing and redundancy profiles. The standard specifies a set of constraints for transporting high-quality, low-latency digital audio over IP networks using RTP (Real-time Transport Protocol). Its primary goal is to guarantee interoperability between different AoIP ecosystems, such as Dante, Ravenna, and Q-LAN.

Because AES67 is not a complete “system” like Dante (which includes proprietary discovery and control), it focuses solely on the transport and synchronization layer. This narrow scope is its greatest strength: any device that supports AES67 can send and receive audio to any other AES67-compliant device without needing a common control protocol. Studios can mix and match gear from various vendors while retaining deterministic timing and audio quality.

Core Features of AES67

Interoperability & Open Standard

The defining feature of AES67 is its ability to bridge proprietary AoIP networks. For example, a mixing console using Ravenna and a loudspeaker processor using Dante can exchange audio if both support AES67. This openness prevents vendor lock-in and gives engineers the freedom to choose best-in-class devices for each task.

High-Quality Uncompressed Audio

AES67 supports uncompressed linear PCM audio at sample rates up to 96 kHz and bit depths up to 32 bits (though 24-bit is most common). It uses payload types such as L24 (24-bit linear PCM) and AM824 (which carries 24-bit audio in 32-bit containers with additional metadata). The standard does not natively support compressed codecs like MP3 or AAC, ensuring pristine quality for critical listening and broadcast applications.

Low Latency and Precision Timing

Latency in AES67 networks is tightly controlled. The standard recommends a maximum end-to-end latency of 2 milliseconds for a single hop, though practical implementations often achieve sub-millisecond performance when using PTP (Precision Time Protocol, IEEE 1588-2008) for synchronization. PTP provides a distributed clock with microsecond accuracy, ensuring all devices sample and play audio in perfect phase.

Synchronization with Precision Time Protocol

AES67 mandates the use of PTPv2 (IEEE 1588-2008) with a default profile that matches the SMPTE ST 2059-1 profile used in broadcast. This allows AES67 streams to coexist with video-over-IP (SMPTE ST 2110) streams on the same network, a significant advantage for production facilities that handle both audio and video. The protocol supports both grandmaster clock redundancy and boundary clock modes for large-scale networks.

Scalability and Network Efficiency

Audio streams are transported via IP multicast, meaning a single stream can be received by many devices without duplicating bandwidth. AES67 defines how streams are announced using SAP (Session Announcement Protocol) so that receivers can automatically discover available flows. Properly configured switches with IGMP snooping allow the network to scale to hundreds of simultaneous audio channels without overwhelming the infrastructure.

Quality of Service (QoS) Requirements

To maintain deterministic performance, AES67 requires network switches that support QoS marking (DSCP EF for audio traffic) and congestion avoidance. The standard specifies minimum bandwidth and jitter tolerance levels, encouraging the use of managed switches rather than consumer-grade equipment. This ensures that even during heavy network load, audio packets arrive on time.

How AES67 Works in Modern Studio Environments

Network Topology and Equipment

A typical AES67 installation uses a dedicated Gigabit Ethernet network (or VLAN) for audio traffic. Endpoints—such as digital mixing consoles, microphone preamps, monitor controllers, and speaker systems—connect via standard Ethernet ports. A network switch with IGMP snooping, PTP-aware hardware timestamping, and robust QoS configuration is essential.

Audio flows are established using a few simple steps:

Announcement: A source device sends SAP packets describing its available streams (format, sample rate, channel count, IP address, etc.).
Subscription: A receiver device joins the multicast group for the desired stream, and the switch directs the traffic only to that receiver.
Synchronization: All devices run PTP to align their sample clocks. The grandmaster clock can be an external reference (GPS, Word Clock, or a dedicated PTP server) or one of the network devices.
Streaming: Audio data is packetized into RTP packets (typically 1 ms of audio per packet) and transmitted with precise timing. The receiver buffers a few packets to absorb jitter before playing out.

Channel Counts and Bandwidth

Each AES67 stereo channel (two audio channels) at 48 kHz/24-bit consumes approximately 3.2 Mbps of network bandwidth after RTP/IP overhead. A 64-channel stream uses about 100 Mbps, fitting comfortably on a 1 Gbps link. Studios can aggregate multiple streams, and with multicast, a 200-channel show might only use 600 Mbps total network bandwidth, leaving room for control data and other services.

Real-World Example: A Broadcast Studio Integration

Consider a radio studio where a Wheatstone console (using Ravenna) needs to send program audio to a Lawo (Dante-based) intercom system. Without AES67, a specialized bridge would be required. With both units supporting AES67, the engineer simply creates an AES67 sender on the console and a receiver on the intercom, sets the sample rate to the common 48 kHz, and the stream is operational. PTP synchronization is handled automatically by the network grandmaster clock. This example shows how AES67 eliminates proprietary boundaries.

Advantages of Using AES67 in Studios

Flexibility & Vendor Neutrality: Mix and match equipment from any manufacturer that supports AES67. Upgrade individual components without overhauling the entire network.
Cost-Effective Infrastructure: Standard Ethernet cabling (Cat5e or Cat6) is much cheaper than multi-pair analog snakes or MADI fiber. No need for proprietary interface cards or breakout boxes.
Future-Proofing: AES67 aligns with broadcast standards (ST 2110) and is being adopted by the pro audio industry as the de facto interoperability layer. It positions studios for IP-native workflows, including remote production and cloud integration.
Reliability and Redundancy: The 2018 revision of AES67 added support for redundant streams (RSTP-based), allowing automatic failover without audio glitches. Combined with redundant PTP grandmasters, the system can survive network failures.
Simplified Troubleshooting: Because AES67 uses standard IP protocols (RTP, SAP, PTP), IT professionals can use common network analysis tools like Wireshark to diagnose issues. This reduces reliance on proprietary diagnostic software.

Challenges and Considerations for Implementation

Network Planning Is Critical

While AES67 offers immense flexibility, it demands careful network design. Not all Ethernet switches are suitable. Consumer switches lack IGMP snooping and may flood multicast traffic throughout the network, causing congestion. Moreover, switches must support PTP transparent clocking (or boundary clock) to maintain synchronization accuracy across multiple hops. Always test your switches for AES67 compatibility; many enterprise switches from Cisco, Netgear, and Extreme Networks work well when properly configured.

Bandwidth and Jitter Margins

Bandwidth calculation must include overhead for RTP, UDP, IP, and Ethernet headers. The standard recommends a jitter buffer of at least 4 ms for normal networks, but if the network has excessive latency or packet delay variation, buffer sizes may need to increase, adding latency. Poorly managed networks can introduce audio dropouts or clicks.

Compatibility Nuances

AES67 implementations from different vendors sometimes have subtle differences. For instance, some devices may only support a single stream or a limited set of sample rates. The standard allows for optional features like redundant streams, but not all devices implement them. It’s essential to verify interoperability before purchase—many manufacturers provide AES67 certification matrices.

Security Concerns

Because AES67 relies on IP networks, it is exposed to the same risks as any networked system: unauthorized access, denial of service, and packet sniffing. Best practices include isolating the audio network on a separate VLAN, disabling unused protocols, and using 802.1X authentication for port security. AES67 itself does not specify encryption; if confidentiality is required, implement IPsec or rely on physical security.

Time Synchronization Setup

PTP configuration is the most common stumbling block. The grandmaster clock must be correctly identified, and all devices must be slaved to the same domain (default domain 0 for AES67). Boundary clocks and transparent clocks must be properly configured in switches to avoid clock drift over long cabling runs. Use a dedicated grandmaster clock with GPS reference if absolute time alignment is needed across multiple buildings.

Comparison to Other AoIP Protocols

Understanding where AES67 fits among other protocols helps engineers make informed choices.

Protocol	Discovery & Control	Sync	Interoperability	Typical Use
AES67	SAP (limited)	PTPv2	High (open)	Interconnection layer
Dante	Proprietary	PTPv2 (modified)	Limited unless AES67 activated	Pro audio, live sound
Ravenna	RTSP/SAP	PTPv2	High (open)	Broadcast, installed sound
AVB (IEEE 802.1)	IEEE 1722	IEEE 802.1AS	Moderate (requires AVB switches)	Automotive, pro audio

Dante products can often be switched to AES67 mode for interoperability, but at the cost of losing some proprietary features like automatic device discovery and latency monitoring. Ravenna is fully based on AES67 and adds its own control layer (RTSP). AES67 is not a substitute for these systems; it is the common language they can all speak.

Future-Proofing with AES67 and ST 2110

The broadcast industry has standardized on SMPTE ST 2110 for video-over-IP, which uses AES67 as its audio transport (PTP and clocking are shared). For broadcast facilities that plan to migrate to IP video, adopting AES67 audio now ensures a smooth transition. Many manufacturers already offer products that support both AES67 and ST 2110-30 (audio). This convergence means that audio engineers who master AES67 will be well-prepared for the IP-based broadcast studios of the future.

Additionally, AES67 is gaining traction in non-broadcast sectors: recording studios use it for monitor control, themed entertainment venues for immersive audio distribution, and houses of worship for large-scale mixing networks. Its open nature encourages third-party software tools for routing, monitoring, and recording.

Conclusion

AES67 is more than just a technical specification—it is the foundation for interoperable, high-performance audio networking. For modern studios, embracing AES67 means less cabling, lower costs, and the freedom to choose the best equipment from any manufacturer. While implementation requires careful network planning and a solid understanding of PTP and multicast principles, the benefits far outweigh the learning curve.

As IP audio continues to dominate, engineers who invest time in understanding AES67 will be better equipped to design resilient, scalable systems. Whether you are setting up a small recording rig or a multi-building broadcast facility, AES67 provides the reliability and future-proofing needed for professional audio production.

Further reading: For official documentation, visit the AES Standards page. Practical configuration guides can be found on Audinate’s AES67 resource hub and DiGiCo’s AES67 overview. For a deep dive into PTP timing, refer to Endrun Technologies’ PTP guide and the SMPTE ST 2110 standards.