Understanding the Basics of AES67 Audio-over-IP Standards and Its Benefits for Modern Broadcasts

In the rapidly evolving world of broadcast technology, audio-over-IP (AoIP) standards have become essential for seamless and flexible audio distribution. Among these standards, AES67 stands out as a widely adopted protocol that ensures interoperability across different systems and manufacturers. Understanding AES67 is crucial for modern broadcasters aiming to enhance their audio workflows, reduce complexity, and future-proof their infrastructure. This article provides a deep dive into AES67, its core principles, benefits, and practical considerations for deployment.

What Is AES67?

AES67 is an open standard developed by the Audio Engineering Society (AES) to facilitate interoperability between various audio-over-IP networks. Officially known as AES67-2018 (with periodic updates), it provides a common framework that allows different manufacturers' equipment to communicate seamlessly, ensuring flexibility and scalability in broadcast setups. Unlike proprietary AoIP solutions, AES67 does not lock users into a single ecosystem. It defines a set of mandatory and optional requirements for transporting high-quality digital audio over standard IP networks, covering everything from sample rates and bit depths to synchronization and clocking.

The standard was first published in 2013 and has since become the backbone for many AoIP implementations, including those used in radio, television, live sound reinforcement, and intercom systems. It builds upon existing technologies such as Real-time Transport Protocol (RTP), Precision Time Protocol (PTPv2, IEEE 1588-2008), and Session Description Protocol (SDP), ensuring that AES67 devices can be integrated into any standards-compliant network.

Core Features of AES67

AES67 is not a complete AoIP stack but rather a profile that specifies how to achieve interoperability. The key features are designed to guarantee high-quality, low-latency audio streaming across diverse hardware.

  • High-Quality, Low-Latency Audio Streaming: AES67 supports up to 24-bit audio with sample rates of 48 kHz or 96 kHz, using uncompressed linear PCM encoding. Latency is configurable but typically ranges from 1 millisecond to 100 milliseconds, allowing broadcasters to optimize for real-time applications like live production or post-production.
  • Standard IP Networking Protocols: AES67 mandates the use of RTP over UDP for audio transport, ensuring real-time delivery. It also requires support for multicast IP addressing, which efficiently distributes audio streams to multiple receivers without overloading the network.
  • Synchronization with Precision Time Protocol (PTP): Synchronization is critical in any AoIP system. AES67 uses IEEE 1588-2008 (PTPv2) to achieve sub-microsecond clock alignment across all devices. This allows multiple streams to be mixed or processed without phase errors or drift. Mastering the PTP domain (grandmaster clock) is typically handled by an audio console or dedicated clock generator.
  • Interoperability with Other AoIP Standards: AES67 is designed to bridge different proprietary ecosystems. It is compatible with RAVENNA, Dante, Livewire, and Q-LAN. Many manufacturers offer AES67 mode in their Ethernet audio devices, allowing them to communicate across platforms. For example, a Dante-enabled microphone can stream to an AES67-compatible mixing console using the standard, albeit with some configuration steps.
  • Quality of Service (QoS) and Network Considerations: The standard recommends using DiffServ (Differentiated Services Code Point) to prioritize audio traffic over data, ensuring reliable delivery even on congested networks. AES67 also defines maximum packet sizes and redundancy options (e.g., ST 2022-7 seamless protection switching) for critical applications.

Benefits of AES67 in Modern Broadcasting

Adopting AES67 brings tangible advantages to broadcast operations, from small studios to global media hubs.

  • Interoperability: The primary benefit is that AES67 enables equipment from different manufacturers to work together without complex gateways or format converters. A broadcast facility can combine a RAVENNA audio server, a Dante microphone array, and an AES67-compatible video encoder, all sharing the same network. This reduces vendor lock-in and opens up more equipment choices.
  • Flexibility: AoIP networks based on AES67 can be easily expanded or reconfigured by adding or moving devices, as opposed to point-to-point analog or MADI connections. Broadcasters can scale from a single room to a multi-site facility using the same underlying infrastructure.
  • Cost-Effectiveness: AES67 uses standard Ethernet switches, cabling (Cat5e or Cat6), and IT gear. Specialized audio snakes, patch bays, and analog-to-digital converters become unnecessary. This lowers capital expenditure and simplifies maintenance.
  • Scalability: With multicast routing, AES67 can support hundreds or thousands of audio channels over a single network. For large-scale events like sports broadcasts or music festivals, this scalability is indispensable.
  • Reliability: AES67 incorporates robust synchronization and redundancy mechanisms. PTP ensures that all devices sample at the exact same rate, preventing clicks or dropouts. ST 2022-7 redundancy allows seamless failover between two network paths. Many broadcasters also use managed switches with Spanning Tree Protocol for cable fault recovery.
  • Future-Proofing: As broadcast moves toward IP-based workflows (SMPTE ST 2110 for video, AES67 for audio), the standard aligns with broader industry trends. Adopting AES67 today prepares organizations for next-generation all-IP studios.

Implementing AES67 in Your Broadcast Workflow

Moving from traditional audio wiring to AES67 requires careful planning and testing, but the process is straightforward for teams familiar with IT networking.

Network Infrastructure

The foundation of any AoIP system is a well-designed Ethernet network. Use managed Gigabit or 10 Gigabit switches that support IGMP snooping, PTP (Boundary Clock or Transparent Clock), and QoS. Avoid consumer-grade switches, as they lack the performance and reliability needed for live audio. For redundancy, deploy two separate switch fabrics (A and B) and connect all AES67 devices to both, enabling seamless failover per the ST 2022-7 standard.

Device Configuration

Each AES67 device must be configured with a shared PTP domain number (typically 0 or 127) and a common sample rate (48 kHz is most common). Set the audio format to L16 or L24, and ensure multicast addresses are properly assigned. Most modern AoIP devices have a web interface or software controller for setup. For example, Dante Controller can configure AES67 mode on Dante-enabled devices, while RAVENNA devices use a built-in discovery protocol.

Clock Master Selection

Designate one device as the PTP grandmaster clock (often a mixing console or dedicated grandmaster). All other devices will synchronize to it. Use a device with high stability (e.g., GPS-locked or TCXO) to avoid jitter. Ensure that the network switch can act as a PTP boundary clock to reduce cumulative delay in large networks.

Testing and Verification

Before going live, test each stream path for latency, audio quality, and synchronization. Use tools like AES67 Audio Analyzer or PTPd to check clock offset. Perform a "smoke test" by routing a known signal (e.g., 1 kHz tone) through the chain and verifying it at the output. Also test failover by unplugging one network cable and ensuring the audio continues uninterrupted.

Staff Training

IT and audio engineers must understand IP networking basics: VLANs, IP addressing, multicast, QoS, and PTP. Many equipment vendors offer training programs (e.g., Audinate's Dante Certification). Investing in training reduces troubleshooting time and builds confidence in the system.

AES67 vs. Other Audio-over-IP Standards

While AES67 is an interoperability standard, it is often compared to full proprietary systems.

  • Dante (Audinate): Dante is a complete AoIP ecosystem with built-in discovery, routing, and redundancy. It is widely used in live sound, recording, and installed sound. Dante devices can be switched to AES67 mode, but native AES67 does not offer Dante's advanced features like automatic clocking and plug-and-play setup. For many broadcasters, using Dante with AES67 compatibility is a practical choice.
  • RAVENNA (ALC NetworX): RAVENNA is a more broadcast-oriented AoIP solution that already shares many underlying protocols with AES67 (RTP, PTP). In fact, AES67 was originally derived from the RAVENNA standard. RAVENNA offers additional redundancy and low-latency profiles, and many RAVENNA devices are AES67 certified out of the box.
  • Livewire (Telos Alliance): Livewire is another broadcast-specific AoIP system, popular in radio. Telos has made its Livewire+ products AES67-compatible, allowing integration with other standards.
  • SMPTE ST 2110-30: For video-centric broadcast environments, AES67 is the audio component of the larger SMPTE ST 2110 standard. ST 2110-30 defines the same audio transport as AES67, ensuring that video and audio share the same network. Understanding AES67 is a prerequisite for building a full ST 2110 studio.

Real-World Use Cases

Radio Broadcast Studios

A large radio network replaced its analog mixing consoles and MADI patch bays with a single Cat6 network connecting all studios, codecs, and processing gear. Using AES67, they mixed RAVENNA-based consoles with Dante-connected microphones and Livewire intercoms. The result was a 40% reduction in cabling, easier reconfiguration for temporary events, and improved redundancy.

Live Sports Production

At a major sports venue, AES67 was deployed to handle audio for a multi-camera truck. Audio from the venue's microphones (Dante) was routed via AES67 to the mixing console (RAVENNA) and simultaneously to a broadcast encoder (ST 2110-30). The system handled 128 channels with less than 2 ms latency, enabling real-time monitor mixes for talent.

House of Worship

A large church migrated from analog to digital using AES67-compatible amplifiers, speakers, and mixing consoles from different manufacturers. The network allowed them to add new audio sources (e.g., streaming audio, wireless mics) without rewiring. Volunteers were able to reconfigure the system using a simple software interface.

Challenges and Considerations

Despite its benefits, AES67 implementation can have a learning curve. Common pitfalls include:

  • Incorrect PTP configuration: Mismatched PTP domains or mixed grandmaster types can cause sync errors. Always use a dedicated grandmaster and ensure switches are PTP-aware.
  • Bandwidth and multicast management: Each 48 kHz/24-bit stereo AES67 stream consumes about 4 Mbps. For large deployments, ensure your switch backplane can handle the total traffic and configure IGMP snooping to avoid flooding.
  • Firewall and VLAN settings: AES67 uses specific UDP ports (e.g., RTP on 5004, PTP on 319-320). Network security policies must allow these protocols. Use dedicated VLANs for audio to separate it from IT data traffic.
  • Latency and jitter buffers: While low latency is possible, some devices may require larger jitter buffers, adding delay. Test each device's recommended latency setting.

Conclusion

AES67 has revolutionized audio-over-IP broadcasting by promoting interoperability and flexibility. Its adoption enables broadcasters to build scalable, reliable, and cost-effective audio networks that meet the demands of modern media production. As technology continues to advance, understanding and leveraging AES67 will remain a key skill for broadcast professionals. Whether you are upgrading a single studio or building a global broadcast infrastructure, AES67 provides a proven, future-proof path to IP audio.

For further reading, consult the official AES67 standard document and the Wikipedia article on AES67. For practical implementation guides, the Audinate AES67 guide offers detailed setup instructions. To learn about PTP synchronization, the IEEE 1588 primer is helpful, and a comprehensive overview of AoIP standards can be found in this AV network article.