Why Network Audits Matter for Audio Protocol Performance

In professional audio environments—whether live sound, broadcast, or installed systems—reliable network performance is non-negotiable. Audio-over-IP protocols like Dante, AES67, Ravenna, and AVB demand strict network conditions to deliver pristine audio without dropouts, clicks, or latency artifacts. A single misconfigured switch, excessive jitter, or packet loss can degrade an entire production. Regular, thorough network audits help you identify weaknesses before they cause problems. They also ensure that new devices and protocols are compatible with existing infrastructure. This guide walks through every stage of a network audit focused on audio protocol compatibility and performance, from preparation through ongoing monitoring.

Understanding Audio Protocols and Their Network Requirements

Each audio-over-IP protocol has unique demands. Knowing these is the first step in any audit. Here are the most common:

  1. Dante (Audinate): Uses IEEE 1588 Precision Time Protocol (PTP) for clock synchronization. Requires low latency (typically under 1 ms per hop), low jitter (ideally below 1 µs), and minimal packet loss. Dante networks often use multicast for multiple receivers and require IGMP snooping to manage flows efficiently.
  2. AES67 (Audio Engineering Society standard): Interoperable standard that sits on the same layer as Dante and Ravenna. It specifies maximum latency of 1 ms and requires PTP (IEEE 1588-2008) for timing. AES67 works at 48 kHz or 96 kHz sample rates.
  3. Ravenna (ALC NetworX): Also uses PTP for synchronization and can operate at higher sample rates up to 192 kHz. It is often used in broadcast and live mixing. Ravenna networks benefit from separate control and audio VLANs to isolate traffic.
  4. AVB (Audio Video Bridging): An IEEE 802.1 standard that guarantees bandwidth and latency through stream reservation. Requires AVB-capable switches and endpoints.

During an audit, you must know which protocols are in use, their sample rates, bit depths, channel counts, and whether traffic is unicast or multicast. This information determines which metrics to prioritize.

Preparing for the Network Audit

A systematic approach prevents oversights. Begin with inventory and documentation:

  • Device Inventory: List every device that sends or receives audio (mixing consoles, stage boxes, DSPs, computers, converters). Record their IP addresses, MAC addresses, and firmware versions.
  • Network Topology: Obtain or create updated diagrams showing switches, routers, cabling (CAT5e, CAT6, fiber), and physical port connections. Note where redundant links exist (e.g., using Spanning Tree or redundant ring topologies).
  • Configuration Files: Collect switch configs, including VLAN assignments, QoS settings, IGMP snooping status, PTP configuration, and any multicast filtering.
  • Tool Readiness: Prepare hardware and software tools: a laptop with Wireshark or a dedicated audio network analyzer (like Dante Controller or Audinate’s Dante Virtual Soundcard), a packet capture adapter (e.g., Endace or nettl), and possibly a precision clock test generator (e.g., a device that generates PTP packets). Also have a cable tester for physical layer checks.
  • Define Audit Goals: Decide what metrics you will measure: end-to-end latency, jitter (mean and maximum), packet loss percentage, clock sync offset, multicast group membership changes, and bandwidth utilization per VLAN.

Step-by-Step Network Audit for Audio Protocols

1. Physical Layer Inspection

Before diving into protocol-level metrics, verify the physical infrastructure. Check that cables are properly terminated and meet the required category (CAT6 or better for 1 Gbps; CAT6A for 10 Gbps). Use a cable certifier to measure length, attenuation, and near-end crosstalk. Faulty cables cause CRC errors and packet retransmissions that degrade audio. Inspect switch ports for link status and speed/duplex mismatches—all audio endpoints should be set to full-duplex at the speed negotiated by the switch.

2. Monitoring Network Traffic

Deploy a packet capture on a mirror port or use a network tap to monitor the audio VLAN. With Wireshark, apply a display filter for the protocol (e.g., dante, aes67, ptp). Look for:

  • Multicast group stability: Frequent IGMP leave/join messages indicate flapping, which can cause intermittent audio loss.
  • PTP message frequency: PTP sync packets should arrive at a steady rate (typically once per second). Gaps or bursts indicate clock issues.
  • Packet inter-arrival time: For audio streams, packets should be evenly spaced. Use Wireshark’s I/O Graph to visualize timing jitter.
  • CRC errors: Statistics > Protocol Hierarchy shows frame check sequence errors. Any CRC errors mean physical layer problems.

Use Dante Controller’s latency tracking feature (if applicable) to see per-device latency and jitter reports. For AES67/Ravenna, tools like Ravenna’s system viewer provide similar diagnostics.

3. Measuring Latency and Jitter

End-to-end latency includes processing time in each device plus network transit time. To measure:

  1. Place a test signal source (e.g., a tone generator connected to an audio input) and a measuring device (e.g., an oscilloscope or software like RME DigiCheck) at the destination.
  2. Record the time difference between sending and receiving a known marker (e.g., a square wave edge or a timestamp injected in the audio stream).
  3. Repeat at different times and under load to capture jitter. Jitter is the variation in latency. For most audio protocols, jitter should be below 1 ms (ideally under 250 µs).

Use PTP-based measurement tools: many audio protocols use PTP for synchronization. Capture PTP sync and delay request-response messages to calculate clock offset and network asymmetry. High asymmetry increases effective jitter. Tools like ptp4l (from linuxptp) can log and analyze PTP timestamps.

4. Checking Packet Loss and Duplicates

Packet loss is the most direct cause of audio artifacts. Use Dante Controller or Wireshark’s UDP statistics to count lost packets. For a stress test, max out channel counts and observe loss under load. Also check for duplicate packets (which can happen due to network loops or port flapping). In Wireshark, use the Expert Info to spot retransmissions or duplicate ACKs.

Note that some protocols (like Dante) use redundant streams or forward error correction (FEC) to mitigate loss. An audit should differentiate between primary and secondary streams and verify that failover works when a link drops.

5. Evaluating QoS and VLAN Configuration

Audio traffic must be prioritized over other network traffic. Verify that switches are configured with strict priority or Class of Service (CoS) marking for audio packets. In most setups:

  • Audio data packets should have CoS/DSCP values of 5 (CS5 or EF) for low-latency media.
  • PTP (clock sync) should be marked higher, e.g., CoS 7 (CS7) or DSCP 47 (EF).
  • Control traffic (like Dante Controller’s discover packets) can be marked at lower priority.

Confirm that each switch port applies the correct queue trust. Also check that audio traffic is isolated on a dedicated VLAN or a separate subnet to avoid broadcast storms and other non-audio traffic. Use Wireshark to verify that packets arriving on the audio VLAN have the expected DSCP values.

6. Switch Configurations and IGMP Snooping

Switches must be properly configured for multicast audio streams. Enable IGMP snooping on all VLANs that carry audio (especially for Dante and AES67). Without snooping, multicast floods to all ports, wasting bandwidth and potentially causing congestion. Verify that the querier is correctly elected and that each switch knows the multicast groups.

Check that Spanning Tree Protocol (STP) is tuned to avoid delays when links fail. Rapid Spanning Tree (RSTP) or Multiple Spanning Tree (MSTP) is preferred to keep convergence time under 1 second. For redundant Dante networks, use audio-specific redundancy (e.g., dual redundant networks or Dante Redundancy) rather than relying on STP alone.

Analyzing and Addressing Common Issues

After collecting data, compare against known thresholds:

  • Latency > 1 ms per hop: Indicates congested links or misconfigured QoS. Consider upgrading to 10 Gbps or segmenting traffic.
  • Jitter > 1 ms: Causes audio buffering issues. Check PTP sync quality, switch buffer settings, and cable noise.
  • Packet loss > 0.1%: Unacceptable for professional audio. Look for faulty cables, full queues, or duplex mismatches.
  • High CRC errors: Replace cables or transceivers; clean fiber connectors.
  • PTP offset > 100 µs: Master clock may be asymmetric; reconfigure PTP domain or use a boundary clock.

Common fixes include:

  • Creating dedicated audio VLANs and restricting VLANs on trunk ports.
  • Setting traffic shaping on control ports to limit low-priority traffic.
  • Replacing non-managed switches with managed switches that support IGMP snooping and QoS.
  • Ensuring all devices on the audio VLAN share a single PTP grandmaster clock.
  • Using redundant network paths with active-active or active-standby failover.

Verifying Improvements and Ongoing Monitoring

Once changes are implemented, rerun the entire audit under the same conditions. Compare metrics before and after. Document the baseline values for future reference. Set up continuous monitoring using SNMP-based tools (e.g., PRTG, Zabbix, or vendor-specific like Audinate’s Network Monitor). Monitor key indicators: link utilization, CRC errors, packet loss per port, and PTP clock offset. Alerts should trigger when thresholds are exceeded.

Schedule quarterly audits for stable systems and more frequent audits during expansions or major events. Keep an up-to-date network diagram and configuration library.

Conclusion

Network audits for audio protocols are not a one-time task but an ongoing practice. As you add devices, update firmware, or change cabling, conditions shift. A rigorous audit process ensures that your network delivers the low latency, low jitter, and zero packet loss that modern audio-over-IP systems demand. By understanding your protocols, preparing thoroughly, measuring accurately, and acting decisively on findings, you can guarantee compatibility and performance across even the most complex audio networks.

For further reading, consult the Audinate Network Audio 101 guide and the AES standards page for protocol details. For advanced network diagnostics, the Wireshark documentation provides excellent capture insights.