Understanding AES67 and Its Benefits

AES67 is a high-performance Audio-over-IP (AoIP) standard ratified by the Audio Engineering Society. It ensures interoperability between different manufacturers’ equipment—from mixing consoles and digital signal processors to amplifiers and monitoring systems. By enabling devices that speak RAVENNA, Dante, Livewire, Q-SYS, or other proprietary protocols to exchange audio streams on a common network, AES67 unlocks flexibility and future-proofing for any venue. Key benefits include the ability to transport dozens or hundreds of uncompressed audio channels over standard Ethernet, low latency (often sub-millisecond), and cable runs up to 100 meters per link without signal degradation. For both small conference rooms and large concert halls, this standard reduces installation complexity and makes upgrades straightforward.

The standard relies on three core technologies: the Precision Time Protocol (PTPv2 per IEEE 1588-2008) for sample-accurate clock synchronization, multicast addressing for efficient delivery of streams to multiple receivers, and Quality of Service (QoS) prioritization to protect audio packets from interference. Understanding these building blocks is essential before planning a deployment.

Preparation and Planning

Assessing the Venue

Start by mapping your venue’s physical layout and acoustical needs. Count the number of audio sources (microphones, playback devices, instruments) and destinations (speakers, recorders, broadcast feeds). Factor in future expansion: adding a few channels now or scaling up for larger events later. For small rooms, 8–16 channels might suffice; large venues can require 64 or more. Also note existing network infrastructure: is there a dedicated IT network, or will you run a separate audio network? The latter is recommended to avoid traffic conflicts.

Selecting Compatible Equipment

Choose devices that support AES67 natively or through firmware upgrades. Popular families include Audinate’s Dante (which includes AES67 mode), RAVENNA-enabled gear from Neumann or RME, Livewire+ from Telos, and Q-SYS from QSC. Many mixing consoles, such as the Allen & Heath dLive or Yamaha CL/QL series, offer AES67 interfaces via expansion cards. Confirm that switches and routers also meet the requirements: fully managed gigabit Ethernet switches with IGMP snooping, QoS (DSCP tagging), and PTP support (Boundary or Transparent Clock capability helps in large networks).

Network Infrastructure Checklist

Switches: Use only managed gigabit switches. Avoid unmanaged switches that cannot prioritize audio. Cabling: Cat6a or Cat7 shielded cable is preferred for larger installations; Cat5e may suffice for smaller setups at shorter distances. Power: Consider PoE+ for microphones and small nodes to simplify cabling. Redundancy: For critical deployments, plan dual-redundant network paths and switches with Rapid Spanning Tree Protocol (RSTP) or Media Redundancy Protocol (MRP).

Step-by-Step Setup Process

Step 1: Network Infrastructure Setup

Deploy your switches in a star topology, connecting all audio devices directly to switch ports. For larger venues, consider a collapsed-core or two-tier design. Enable the following on every switch port that will carry audio:

  • Jumbo frames (if supported) to reduce overhead – 9000 MTU is common.
  • IGMP snooping with an IGMP querier enabled on one switch per VLAN.
  • QoS: Mark AES67 audio packets with DSCP EF (46) for clock traffic and CS4 (32) or AF41 for audio streams, as per AES67 recommendations. The switch should trust and honor these markings.
  • Spanning Tree: Use RSTP (802.1w) for faster convergence; portfast on edge ports connecting audio endpoints to avoid delays.

Separate audio traffic into a dedicated VLAN to isolate it from data traffic, reducing the chance of interference and simplifying QoS management.

Step 2: IP Addressing and Network Services

Assign static IP addresses to all AES67 devices, or use DHCP reservations on the router to ensure addresses never change. Document every device’s IP, MAC, and stream configuration. Enable PTP on all switches: set them as Boundary Clocks (preferred) or Transparent Clocks. Configure PTP domain number (default 0 is common) and announce/ sync intervals (typically 1 second announce, 1/8 second sync). Avoid using NTP for audio clock; PTP provides the necessary microsecond accuracy.

Step 3: Configuring AES67 Devices

Access each device via its web GUI or manufacturer software (e.g., Dante Controller, RAVENNA Manager, Q-SYS Designer). Perform these tasks:

  • Set audio parameters: Sample rate 48 kHz (most common), bit depth 24 or 32. Ensure all devices use identical settings.
  • Enable PTP: Select the PTP profile for AES67 (IEEE 1588-2008 profile). Many devices auto-discover the master, but you may manually designate a preferred master (the most stable device, often a console or a dedicated grandmaster clock).
  • Create streams: Define transmit channels (e.g., “StageBox Out 1-8”) and subscribe (receive) streams from other devices. Most software uses a drag-and-drop or matrix model.
  • Latency management: Set packet time (e.g., 1 ms or 0.125 ms) based on your network’s switch delays. Shorter packet times reduce latency but increase bandwidth. Start with 1 ms for safety.

Step 4: Synchronization and Testing

After all devices are connected and configured, check clock lock. Each device should indicate “Locked to PTP” or similar. Play a test tone from one source and verify clean reception at all destinations – use headphones or a metering plugin. Use Wireshark to capture PTP and audio packets; look for packet loss (less than 0.1% is acceptable), jitter (should be below 250 µs for 1 ms packet time), and clock offset (ideally under 1 µs). Run this test under normal network load (including any non-AES67 traffic) to confirm QoS effectiveness. Adjust DSCP values or switch queuing if problems appear.

Scaling for Larger Venues

Segmentation and Routing

For venues with multiple rooms or zones (e.g., auditorium, lobby, breakout rooms), segment the network into separate VLANs per zone. Use a layer-3 switch or router with multicast routing (e.g., PIM-SM) to interconnect zones while controlling traffic. This prevents a stage-box’s streams from flooding a lobby zone that doesn’t need them. Each VLAN should have its own IGMP querier and PTP boundary clock.

Redundancy and High Availability

Critical systems demand redundant paths. Deploy two independent switches (primary and secondary) with devices connected to both via dual NICs or using a Redundancy Protocol like Dante’s Primary/Secondary or RAVENNA’s seamless protection switching. Use RSTP or MRP to handle link failures. For PTP, implement redundant grandmasters with best master clock algorithm (BMCA) logic – if the primary fails, the backup takes over within seconds. Standard deployments often require no more than 50 ms of signal dropout.

Centralized Management and Monitoring

Use network management software to oversee all AES67 endpoints, switch status, and PTP health. Tools like SNMP (via switches) plus device-specific applications (Dante Controller, Q-SYS Admin) give you real-time views of latency, packet errors, and clock offset. Set up alerts for any stream disconnections or PTP clock loss. For large installs (100+ channels), consider deploying a dedicated PTP grandmaster like the Meinberg LANTIME or EndRun Technologies device to provide a rock-solid time reference across long distances.

Best Practices and Troubleshooting

Best Practices

  • Document everything: IP addresses, VLAN IDs, stream subscriptions, PTP settings, switch port configurations. Keep a copy on-network and offline.
  • Firmware updates: Regularly check for updates from both switch and audio device manufacturers. Interoperability improvements are common.
  • Backup configurations: Save switch startup configs and audio device presets. Practice restoring them after a switch replacement.
  • Train staff: Educate audio engineers and IT personnel on AES67 basics, PTP management, and how to read diagnostic tools. A shared vocabulary avoids finger-pointing during events.
  • Test before events: Run a full system test at least 24 hours before first use, including stress tests with all planned streams active plus any non‑audio network loads.

Common Issues and Resolutions

IssueLikely CauseSolution
No audio or intermittent dropoutsHigh packet loss; IGMP missing; switch port blocked by STPEnable IGMP snooping + querier; set portfast; check cable termination
Audio glitches/artifactsClock drift; PTP misconfiguration; network congestionVerify all devices locked to same PTP master; check QoS; reduce non-audio traffic on same VLAN
High latencyPacket time too large; switch buffer delays; spanning treeDecrease packet time to 0.125 ms if network supports; disable STP on edge ports; use cut-through switching
Streams not visible across VLANsNo multicast routing between VLANs; IGMP lacks querier per VLANEnable PIM-SM or use a layer-3 device that passes multicast; deploy IGMP querier in each VLAN

For deeper diagnostics, use Wireshark with the ptpv2 filter to examine PTP messages. Look for Announce messages from the Grandmaster (GM). If multiple GMs appear, review the BMCA settings on devices – typically the device with the highest clock quality (e.g., an external GPS-disciplined oscillator) should win. Adjust priorities manually if needed.

External Resources

For further reading on AES67 implementation, consult these authoritative sources:

Conclusion

Implementing AES67 audio networking is a systematic process that starts with thorough planning and ends with a versatile, high-performance audio distribution system. Whether you are wiring a small conference room with a dozen channels or a touring venue with hundreds, the same principles apply: invest in managed networking, configure PTP and QoS with care, test rigorously, and document everything. The interoperability that AES67 brings means you are not locked into one eco-system; you can mix and match equipment from different vendors as your needs evolve. By following the step-by-step guide above and adhering to best practices, you will build a reliable, scalable AoIP foundation that delivers crisp, low-latency audio for any event.