Understanding Audio-over-IP Protocols and Their Roles

Audio-over-IP (AoIP) transmits uncompressed, multi-channel audio over standard Ethernet networks, replacing bulky analog snakes and digital multicore cables. In live concerts, the choice of protocol determines latency, channel count, and interoperability. The three dominant standards are Dante, Ravenna, and AES67, each offering distinct advantages in live sound environments.

Dante by Audinate is the most widely adopted AoIP protocol in professional audio. It provides automatic device discovery, sub-1 millisecond latency, and simplified routing via Dante Controller software. Dante supports both unicast and multicast traffic and scales to hundreds of channels on a Gigabit network. For concerts, Dante is favored for its plug-and-play setup and broad manufacturer support—from Yamaha mixers to Shure wireless systems.

RAVENNA is an open, manufacturer-independent protocol built on standard IT infrastructure. It offers high channel density (up to 128 channels per stream at 96 kHz) and robust synchronization via Precision Time Protocol (PTP). RAVENNA is often used in broadcast and large-scale concert systems where integration with professional video over IP (SMPTE ST 2110) is required. Its ability to operate over both unicast and multicast makes it flexible for mixed-use networks.

AES67 is an interoperability standard that allows devices from different manufacturers to exchange audio streams over IP. It defines a common transport layer (RTP) and clock synchronization (PTPv2), enabling Dante, RAVENNA, and other proprietary systems to coexist. In a live concert scenario, using AES67 as a common bridge can integrate consoles from different brands or connect on-stage I/O to the front-of-house position without dedicated cabling. However, AES67 does not include automatic discovery, so careful configuration is required.

For the highest performance and future-proofing, consider Milan—a deterministic profile built on the IEEE 802.1 Audio Video Bridging (AVB) standard. Milan guarantees bounded latency, zero packet loss, and is plug-and-play, but it requires compatible switches and endpoints. While less common in rental inventory today, Milan is gaining traction in fixed installations and festival touring rigs where reliability is paramount.

Designing a Robust Network Infrastructure for Live Sound

AoIP’s success depends entirely on the network fabric. A poor switch choice or misconfiguration will cripple the entire audio system. For live concerts, follow these infrastructure principles.

Network Topology

Use a star topology rather than daisy-chaining. Each AoIP device (stage box, console, wireless receiver) connects via a dedicated Ethernet cable to a central switch. This minimizes hop count and simplifies troubleshooting. For larger systems, consider a two-tier model: a stage-side switch for all on-stage equipment and a front-of-house switch, connected by fiber or redundant copper trunks. Avoid creating loops unless using a managed protocol like Spanning Tree.

Switch Selection and Configuration

Choose managed Gigabit switches with low latency (typically <5 µs per hop). Required features include:

  • IGMP snooping – Prevents multicast traffic from flooding all ports, essential for channel reduction.
  • Jumbo frames – Enable 9000-byte frames to reduce CPU load on endpoints, but only if all devices support them.
  • Energy Efficient Ethernet (EEE) – Disable it. EEE introduces latency jitter by powering down ports during idle periods.
  • Flow control – Disable it. AoIP relies on precise timing, and flow control can cause buffer overruns.

For large-scale concerts (10+ switches or long distances), use fiber uplinks. Fiber is immune to electromagnetic interference and supports distances beyond 100 meters. Two dedicated network segments—a primary and a secondary—are recommended for active redundancy.

Redundancy Strategies

Many AoIP protocols offer built-in redundancy. Dante supports Primary and Secondary ports, automatically switching without glitches. RAVENNA can use SMPTE ST 2022-7 hitless merging. At the network level, implement Rapid Spanning Tree Protocol (RSTP) or Media Redundancy Protocol (MRP) for loop protection. Always test failover times before show day; sub-10 millisecond convergence is achievable with modern switches.

Optimizing Network Configuration for Low Latency

Live concerts demand latency under 1 ms for wedge monitoring and IEM systems. Achieving this requires meticulous network tuning.

Quality of Service (QoS) and DSCP Marking

Voice and audio traffic must be given priority over data. Configure Differentiated Services Code Point (DSCP) markings according to the protocol guidelines:

  • Dante recommends DSCP 46 (EF) for audio data, DSCP 34 (AF41) for clock synchronization.
  • RAVENNA uses DSCP 46 for audio streams, DSCP 56 (CS7) for PTP sync.
  • AES67 follows SMPTE ST 2022-2 with DSCP 46 for audio.

Apply these markings on each endpoint and create QoS policies on every switch. Use strict priority queues to ensure audio packets are never delayed by best-effort traffic. In mixed environments (e.g., a concert with video or lighting over the same network), dedicate a separate VLAN for audio to reduce CPU load on switches.

Clock Synchronization: Precision Time Protocol (PTP)

All AoIP protocols rely on a master clock to keep sample clocks synchronized across devices. PTPv2 (IEEE 1588) provides sub-microsecond accuracy. Configure a stable grandmaster clock—often a dedicated PTP server or a device with a built-in, oven-controlled oscillator. Use the clock domain recommended by the protocol (e.g., domain 0 for Dante, domain 127 for RAVENNA/AES67). On the network, enable PTP-aware boundary clocks or transparent clocks on switches to correct residence time. Ensure all switches pass PTP frames (multicast MAC 01-1B-19-00-00-00).

Buffer Size Management

In the device settings, the buffer (or latency) slider directly affects stability. Lower buffers (e.g., 0.25 ms, 0.5 ms) reduce delay but increase the chance of dropouts. A good starting point for live sound is 1 ms for Dante and 2 ms for RAVENNA/AES67. If experiencing audio glitches, incrementally increase buffers until stable, then test at full show load. For recording or broadcast feeds where latency is less critical, 4–8 ms buffers are acceptable.

Enhancing Audio Quality and Reliability

Cabling and Connectors

Use shielded Cat6a or Cat7 Ethernet cables for all runs inside the concert environment. Shielded twisted-pair (STP) cable reduces crosstalk and EMI from lighting dimmer racks and power distros. For permanent installations, consider solid-core cable, and for touring, flexible stranded cable with ruggedized connectors (e.g., Neutrik EtherCON or Amphenol RJ45). Fibre-optic Ethernet (using media converters or native SFP ports) is mandatory for runs over 100 meters or when running alongside high-current power lines.

Reducing Electromagnetic Interference

Audio-over-IP is digital, but high-power interference can still corrupt packets. Keep network cables at least 1 meter away from AC mains, dimmer packs, and motor control cables. Use ferrite chokes on power and signal cables where necessary. In extreme environments (e.g., EDM festivals with large video walls), switch from copper to fiber to eliminate ground loops and induced noise.

Firmware and Software Updates

Keep all AoIP endpoints and network switches on the latest firmware. Manufacturers regularly fix bugs, improve PTP stability, and add interoperability features. Before any tour or festival, update Dante Controller, RAVENNA device configurations, and switch firmware in a controlled bench test. Maintain backup copies of all device configuration files and network switch settings.

Monitoring and Troubleshooting AoIP Systems

Proactive monitoring prevents show-stopping failures. Install real-time monitoring tools to track packet loss, jitter, and clock offset.

Tools for Network Health

  • Dante Controller – Displays latency, clock status, and device health. Use the Network View to verify link speeds and port status.
  • Wireshark – Capture RTP streams and PTP packets. Filter for DSCP markings and analyze packet timing (jitter) using the RTP statistics feature.
  • Switch SNMP – Poll per-port statistics (errors, discards) via tools like PRTG or LibreNMS.
  • Ravenna Virtual Sound Card or similar software can show stream connectivity and PTP offset.

Run through a full-system check before every performance: ping all devices, verify clock master selection, and send test tones at full channel count. Log any anomalies, such as occasional dropouts that only occur with lighting cues.

Common Issues and Resolutions

  • Audio dropouts or pops – Check for high packet loss (over 0.1%). Likely causes: switch congestion, faulty cable, or insufficient QoS. Reduce channel counts or upgrade uplink speed.
  • High latency variation (jitter) – Ensure PTP synchronization is stable. Use a dedicated grandmaster and enable boundary clocks on switches. Disable EEE and flow control.
  • Subnet mismatch – All AoIP devices must be on the same subnet or use mDNS across subnets (Dante supports Dante Domain Manager). Static IPs reduce discovery issues.
  • Switch port flapping – Often caused by Auto-MDIX incompatibility; manually set speed and duplex.

Best Practices for Large-Scale Concert Deployments

The following workflow reduces risk during setup:

  1. Design network topology offline, including port assignments and VLANs.
  2. Pre-configure switches with QoS, IGMP snooping, and PTP settings before installing.
  3. Test a small reference link (console → stage box) at full channel count to establish baseline latency.
  4. Deploy redundant networks (primary and secondary) and test failover under load.
  5. Use a dedicated clock generator (e.g., Dante's built-in grandmaster or an external AES67 sync source) to maintain stability across multiple venues.
  6. Keep spare switches, cables, and media converters on site.

For festivals with multiple stages, centralize AoIP management using Dante Domain Manager or RAVENNA’s RMQ tool to monitor all streams from one console.

Conclusion

Optimizing AoIP for live concerts requires a systematic approach to network design, configuration, and ongoing monitoring. By selecting the appropriate protocol, deploying managed switches with proper QoS and PTP, and using high-quality shielded cabling, sound engineers can achieve sub-millisecond latency and rock-solid reliability. Implement the strategies outlined above—especially redundancy and clock synchronization—to ensure every performance delivers clear, uninterrupted audio. As AoIP standards continue to evolve, staying current with firmware updates and emerging protocols like Milan will keep your system future-proof.

For further reading, consult the official Audinate Dante documentation (Audinate Learn), the RAVENNA network guidelines (RAVENNA), and the AES67 standard specifications (AES67-2018).