Audio-over-IP (AoIP) protocols like Ravenna and Dante have become the backbone of professional audio distribution in broadcast, live sound, and recording environments. They replace traditional point-to-point analog or digital connections with networked packet-based transport, offering flexibility, scalability, and reduced cabling. But with great power comes complexity. Even seasoned audio engineers can face frustrating dropouts, latency, or silence when the network misbehaves. This comprehensive guide walks you through the most common issues in Ravenna and Dante systems and provides practical, step-by-step troubleshooting strategies to get your audio flowing reliably.

Understanding the Underlying Protocols

Before diving into troubleshooting, it helps to grasp how Ravenna and Dante differ from each other and from generic IP audio. Both use standard Ethernet but employ different discovery, clocking, and transport mechanisms.

Dante: The Plug-and-Play Giant

Developed by Audinate, Dante leverages Layer 3 IP networking, supports AES67 interoperability, and automatically discovers devices via mDNS. Its automatic clocking and redundant network paths make it popular in fixed installations and live sound. However, its reliance on multicast for many streams can challenge unprepared network switches.

Ravenna: Open and AES67-Native

Ravenna, developed by Lawo and ALC NetworX, is an open standard built on AES67 and SMPTE ST 2110-30/31. It uses PTPv2 (IEEE 1588-2008) for precision timing and often requires manual configuration of multicast addresses and flow control. Ravenna is common in broadcast studios where tight integration with video-over-IP is needed.

Both protocols demand careful attention to network infrastructure, clock synchronization, and firmware consistency. When issues arise, the root cause often lies in one of these three areas.

Common Issues and Their Root Causes

1. Device Discovery Failures

One of the first signs of trouble: your console can’t see the stage box, or your DAW won’t list the Dante virtual sound card. This usually points to network misconfiguration.

  • Broken mDNS or DNS-SD: Dante relies on multicast DNS. If your network blocks mDNS (common in corporate networks), devices won’t discover each other.
  • VLAN misalignment: Devices on separate VLANs without a multicast router or IGMP querier cannot see each other.
  • Firewall interference: Windows firewalls often block Dante Discovery and other essential ports (UDP 8700-8707, 14336-14688).

2. Audio Dropouts and Intermittent Silence

Intermittent audio dropout is a symptom of packet loss. Even 0.1% loss can cause audible clicks or pops. Common culprits:

  • Excessive switch utilization: When a switch port nears 100% bandwidth, packets are dropped. AoIP typically uses less than 10% of a 1 Gbps link per stream, but aggregating many streams can still overwhelm.
  • IGMP snooping misconfiguration: Without proper IGMP snooping, multicast streams flood all ports, leading to collisions and drops.
  • Poor cable quality: Damaged or unterminated Cat5e/Cat6 cables introduce errors. Use a cable tester or look for link flap in switch logs.

3. High Latency or Jitter

Latency is the time a packet takes to travel from source to destination. Jitter is its variability. Both degrade audio quality, especially for live monitoring or broadcast talent.

  • Network congestion: Competing traffic (file transfers, video streams) can add jitter. Quality of Service (QoS) prioritization is essential.
  • Clock drift: Ravenna’s PTPv2 grandmaster clock must be accurate to sub‑microsecond levels. A free‑running oscillator in a switch can introduce jitter.
  • Buffer underruns: If network jitter exceeds the receive buffer size, packets arrive late and are discarded. Adjusting buffer depths (e.g., from 1ms to 2ms) can help, but at the cost of latency.

4. Synchronization Loss (Clock Errors)

Both Dante and Ravenna use a single clock leader to synchronize all devices. If the leader fails or is disrupted, devices may fall back to internal clock, causing audible drift or locked status flashing.

  • PTP boundary clock not configured: In Ravenna networks, each switch layer must be set up as a boundary clock or transparent clock to preserve PTP accuracy.
  • Multiple clock sources: If two devices claim to be clock leaders (e.g., two Dante controllers), chaos ensues. Ensure only one grandmaster is active.
  • Network path asymmetry: PTP assumes symmetrical delay in both directions. If your network uses different paths for upload and download (e.g., via a router with unequal routes), PTP timing breaks.

5. No Audio at All

Complete silence is more straightforward to diagnose but still frustrating. Check the obvious first: is the signal routed in the controller software? Then verify that the correct sample rate and bit depth are matched across all devices. Dante and Ravenna do not auto‑negotiate sample rates.

Systematic Troubleshooting Workflow

Instead of shooting in the dark, follow this logical escalation path. Document every change so you can revert if something goes wrong.

Step 1: Validate the Physical Layer

Troubleshooting begins with the cable. Use a cable certifier or at least a continuity tester. Ensure connectors are fully seated and not near power cables. For long runs, verify link speed and duplex. A mismatch (e.g., one side forced 1 Gbps full duplex, the other auto‑negotiates 100 Mbps half duplex) will cause heavy packet loss.

Switch to a known‑good patch cable to rule out physical faults. The device LED should be solid green; if it’s orange or flickering wildly, you have a problem.

Step 2: Verify IP Configuration

Every AoIP device needs a unique IP address, correct subnet mask, and (if needed) default gateway. Use the controller software or web interface to check:

  • IP address assignment: Are devices using DHCP or link‑local (169.254.x.x)? For Dante, link‑local is default and works within a single subnet. For Ravenna, DHCP is often required.
  • Subnet consistency: Two devices on different subnets will not see each other without routing.
  • VLAN tagging: If using VLANs, ensure the switch trunk port allows the correct VLAN ID and that the device is configured to tag.

Step 3: Test Connectivity with Basic Tools

From a computer on the same network, use ping to test basic reachability. A high ping time or packet loss indicates network stress. Use traceroute to see the path between devices; unexpected hops through routers or firewalls often signal misconfiguration.

For Dante, Audinate provides the free Dante Controller which includes a network health dashboard. For Ravenna, use Wireshark to inspect PTP (IEEE 1588) packets and check for Sync, Follow_Up, and Delay_Resp messages.

Step 4: Examine Multicast Handling

Multicast is the lifeblood of AoIP. Improper multicast setup is the number one cause of dropouts.

  • Enable IGMP snooping on every managed switch.
  • Assign an IGMP querier on each VLAN (only one querier per VLAN). For small networks, many switches have a built‑in querier.
  • Check multicast group addresses: Dante defaults to 239.x.x.x; Ravenna uses 232.x.x.x (SSM). Ensure these ranges are not blocked by access controls.
  • Use multicast to unicast conversion (available on some switches) to reduce flooding for devices that only need one stream.

Step 5: Implement Quality of Service (QoS)

Without QoS, a large file transfer can delay audio packets by tens of milliseconds. Configure QoS as follows:

  • Classify audio packets based on DSCP (Differentiated Services Code Point). Dante uses EF (46), Ravenna uses AF41 (34) or CS4 (32).
  • Set priority queues: Place audio traffic in the highest priority queue with strict priority (not weighted fair queuing).
  • Guarantee bandwidth: Reserve at least 30% of link bandwidth for audio to allow growth.
  • Apply QoS on all ports (ingress and egress). Many switches drop QoS markings at the switch boundary if not trusted.

Step 6: Analyze Clocking

For Ravenna, use the PTP Management pages in the device web interface to verify grandmaster synchronization. Look for offset values under 1 μs and Announce message rate of 1 packet per second. If the grandmaster is a switch, confirm it is configured as a boundary clock.

For Dante, Dante Controller shows clock status per device. A “Locked” status with low jitter is good. If a device shows “Sync” but not “Locked,” check the clock leader selection and ensure no device is set to “Preferred Master” inadvertently.

When using AES67 interoperability between Dante and Ravenna, ensure both sides use the same clock reference (PTP grandmaster) and sample rate (48 kHz is standard).

Advanced Troubleshooting Techniques

Using Wireshark for Packet Inspection

Wireshark is the ultimate diagnostic tool. Capture traffic on a switch mirror port (SPAN) to monitor all AoIP traffic without disrupting the network. Look for:

  • Duplicate ACK or retransmissions: Indicates packet loss.
  • Out‑of‑order packets: Usually caused by ECMP (Equal Cost Multi Path) routing. Disable ECMP for multicast.
  • PTP delay asymmetry: Filter for ptp and check that the Delay_Resp message arrives consistently.

For professional support, share filtered Wireshark captures with your device manufacturer.

Network Redundancy and Resilience

Both Ravenna and Dante support redundant networks. Dante uses a primary and secondary port; Ravenna can use a Seamless Redundancy (SMR) protocol (IEEE 802.1CB). However, redundancy adds complexity:

  • Both paths must be identical in latency and topology.
  • Switches must support RSTP or MSTP for fast failover (below 50 ms).
  • Test redundancy by pulling a cable during an active show to confirm seamless switchover.

Firmware and Software Versioning

Outdated firmware is a hidden source of instability. Manufacturers update their firmware to fix bugs, improve PTP accuracy, and add AES67 compatibility. Create a version matrix and update all devices to the latest stable release before deployment. Keep a rollback plan in case the new firmware introduces regressions.

Best Practices for Reliable AoIP Operation

Network Design

  • Use dedicated switches for audio traffic. If sharing with video or data, ensure strict VLAN separation.
  • Deploy a star topology rather than daisy‑chaining switches to reduce hop count and latency.
  • Choose non‑blocking switches that can handle backplane throughput equal to the sum of all port speeds.

Edge Cases and Interoperability

When mixing Ravenna and Dante within the same network, support for AES67 is critical. Many Dante devices can now receive Ravenna streams via AES67, but you may need to enable AES67 mode in Dante Controller and adjust the latency to 5 ms or higher. Similarly, Ravenna devices can enumerate Dante sources if both sides agree on multicast addresses and clocking.

Documentation and Lab Testing

Before a live event, build a lab network with the exact switches, cable type, and device firmware you plan to use. Stress test it with heavy artificial traffic (e.g., iPerf) to simulate real‑world conditions. Document all configurations—IP assignments, QoS rules, IGMP querier, PTP profiles—so you can restore them quickly.

When to Call for Help

Despite exhaustive troubleshooting, some issues require manufacturer support. If you experience:

  • Persistent clock lock failures even with correct PTP
  • Random device crashes with no network correlation
  • Interoperability between brands that defies all configurations

then contact Audinate or the Ravenna device manufacturer (e.g., Lawo, DirectOut, Neumann) with your configuration files, switch configs, and packet captures. Many vendors offer free webinars and knowledge bases.

Conclusion

Troubleshooting Ravenna and Dante systems is a blend of methodical network diagnosis and understanding audio‑specific protocols. By mastering the steps outlined here—verifying the physical layer, ensuring correct IP configuration, tuning multicast and QoS, and validating clocking—you can resolve the vast majority of common issues. The best defense against AoIP problems is a well‑designed, documented network combined with proactive firmware updates. When everything aligns, the rewards are pristine, low‑latency audio that seamlessly scales from a single studio to a global broadcast.