The Best Network Topology for Live Sound

Live sound networks must handle three primary traffic types: audio (e.g., Dante, AES67), control (e.g., OSC, MIDI, console remote), and management (e.g., DHCP, SNMP, web GUI). Each has different tolerance for latency and packet loss. Audio requires deterministic, low-latency delivery; control can tolerate slight delays but must be reliable; management traffic is less time-sensitive. Mixing these on a single flat network without segmentation can lead to congestion, dropped packets, and audio dropouts.

The network must also be resilient. A single switch failure or cable cut should not take down the entire system. Redundancy at the switch, link, and device level is critical for high-stakes events. Additionally, cable runs must be planned to avoid exceeding Ethernet distance limits (100m for copper) and to manage power over Ethernet (PoE) requirements for devices like stage boxes and wireless mic receivers.

The star topology is the most common and easiest to deploy. All devices connect to a central switch or a small cluster of switches. This provides a single point of management and makes troubleshooting straightforward. For small to medium-sized productions, a single managed Gigabit switch with sufficient ports is often adequate. Ensure the switch supports IGMP snooping to prevent multicast audio traffic from flooding all ports, and has a robust backplane to handle full line-rate throughput.

However, the star topology has a single point of failure: the central switch. If it fails, the entire network goes down. For mission-critical events, a redundant star or ring topology is recommended. In a redundant star, two independent switches (primary and secondary) are used, with devices connected to both via dual NICs (e.g., Dante Primary and Secondary ports). This provides failover without interruption, but doubles the switch count and cabling.

The redundant star topology is the gold standard for Dante and AES67 networks. It uses two separate networks (primary and secondary) that are completely isolated. Dante devices automatically send audio on both networks; the receiving device selects the best signal. This provides seamless failover with zero packet loss. The primary and secondary switches should be identical and configured identically (except for IP addressing).

Ring topologies (e.g., using RSTP or proprietary protocols) can provide link redundancy with fewer cables, but they introduce complexity and potential convergence delays. In a ring, if a cable breaks, the ring must reconverge, which can cause a brief audio dropout (typically 1-2 seconds with RSTP). For live sound, even a short dropout is unacceptable. Therefore, SSOUNDS recommends a redundant star topology for all critical audio networks. Rings are better suited for control networks where brief interruptions are tolerable.

VLANs (Virtual LANs) allow you to logically segment a single physical switch into multiple isolated networks. This is essential for live sound to prevent control traffic (e.g., console remote, wireless mic management) from interfering with time-sensitive audio. A typical setup uses three VLANs: one for audio (e.g., VLAN 10), one for control (VLAN 20), and one for management (VLAN 30).

Audio VLANs should be configured with strict QoS (Quality of Service) to prioritize Dante/AES67 traffic. Control VLANs can have lower priority. Management VLANs should be restricted to authorized devices and often use a separate IP subnet. Trunk ports between switches carry all VLANs, while access ports are assigned to a single VLAN. Proper VLAN configuration prevents broadcast storms and reduces unnecessary traffic on the audio network.

Switch placement should minimize cable runs while maintaining accessibility for troubleshooting. For large venues, place switches at FOH (Front of House), monitor world, stage left/right, and any delay tower positions. Use fiber optic links for runs longer than 100 meters (e.g., from FOH to stage). Fiber is immune to EMI and can run hundreds of meters without signal degradation. For shorter runs, shielded Cat6a or Cat7 copper cable is recommended.

Always use separate physical paths for primary and secondary network cables to avoid a single cut taking down both networks. Label all cables clearly and use color coding (e.g., red for primary, blue for secondary). Keep network cables away from power cables and other sources of interference. For outdoor events, use ruggedized connectors and weatherproof enclosures for switches.

Enable IGMP snooping on all switches to ensure multicast audio traffic is only sent to ports that have subscribed. Disable STP (Spanning Tree Protocol) on ports connected to Dante devices to prevent port blocking during convergence. Instead, use RSTP on uplinks between switches for redundancy. Set all Dante devices to use the same clock source (e.g., a dedicated master clock or the console).

For large networks, consider using a dedicated network management tool (e.g., Dante Controller, AES67 Discovery) to monitor latency, clock status, and subscription errors. SSOUNDS line array systems are designed to integrate seamlessly with standard Dante/AES67 networks, and our engineering team provides detailed network design support for complex deployments. Always test the network thoroughly before show day, including failover scenarios.