The Shift to Networked Audio in Modern Studios

The professional audio industry has undergone a fundamental transformation over the past decade. Traditional point-to-point analog snakes and MADI-based digital infrastructures are rapidly giving way to Audio over Internet Protocol (AoIP) systems that offer unprecedented flexibility, scalability, and cost efficiency. Whether you are building a new facility or retrofitting an existing control room, the network hardware you choose — switches, cabling, media converters, and power infrastructure — will determine the reliability and performance of your entire audio ecosystem.

Unlike consumer networking where occasional packet loss might go unnoticed, studio AoIP networks demand deterministic behavior. A single dropped packet can produce an audible click or pop during a critical take. Jitter that would be irrelevant for web browsing can destabilize word clock synchronization across dozens of devices. This reality means that every component in the data path must be selected with the same rigor you would apply to a mixing console or microphone preamplifier.

This guide provides an in-depth technical walkthrough of the considerations, trade-offs, and best practices involved in selecting AoIP switches and supporting network hardware. You will learn how to evaluate port density, Power over Ethernet (PoE) budgets, managed versus unmanaged architectures, and the specific protocol requirements for Dante, AES67, and AVB. By the end, you will have a clear framework for building a network that delivers sub-millisecond latency, sample-accurate synchronization, and years of maintenance-free operation.

Understanding AoIP Protocols and Their Network Requirements

Before selecting hardware, it is essential to understand how different AoIP protocols interact with network infrastructure. While all AoIP systems encapsulate audio as IP packets, the transport mechanisms, clocking strategies, and multicast behavior vary significantly.

Dante

Developed by Audinate, Dante is the most widely adopted AoIP protocol in professional audio. It operates over standard Gigabit Ethernet and uses Layer 3 IP routing with multicast for one-to-many distribution. Dante devices automatically discover each other via mDNS and DHCP, and the Dante Controller software manages routing and latency configuration. Dante requires switches that support IGMP snooping to prevent multicast traffic from flooding all ports. Without IGMP snooping, a Dante network with many multicast flows can overwhelm switch buffers and cause audio dropouts. Dante also benefits from Quality of Service (QoS) prioritization using DiffServ Code Points (DSCP), with audio traffic typically marked as EF (Expedited Forwarding, DSCP 46).

AES67

AES67 is an interoperability standard that allows devices from different manufacturers to exchange audio over IP. It is not a full control protocol like Dante but rather a transport and synchronization specification. AES67 relies on Precision Time Protocol (PTPv2) according to IEEE 1588-2008 for clock synchronization. This adds a requirement for the network to support PTP boundary clocks or transparent clocks on switches. Not all managed switches implement PTP hardware timestamping, which is critical for achieving the sub-microsecond synchronization accuracy AES67 demands. When building an AES67 network, verify that your switch supports the SMPTE ST 2059-2 profile or can be configured as a PTP-aware boundary clock.

AVB (Audio Video Bridging)

AVB is an IEEE standard suite (802.1BA) that includes Stream Reservation Protocol (SRP), credit-based shaping, and precise timing. AVB switches must support these extensions to guarantee bandwidth and latency for time-sensitive streams. AVB is less common in studio environments than Dante but is used in some automotive and live sound applications. Native AVB switches are typically more expensive and less widely available than standard managed switches configured for Dante or AES67.

The takeaway is that your protocol choice directly influences switch selection. Dante requires IGMP snooping and QoS. AES67 demands PTP support. AVB requires switches with IEEE 802.1Qat and 802.1Qav capabilities. If you plan to run multiple protocols on the same network, you need a switch that can satisfy the most stringent requirements of all protocols simultaneously.

Key Factors in Choosing AoIP Switches

Port Count, Density, and Future Expansion

The first step in selecting a switch is to inventory every device that will connect to the network. This includes audio interfaces, stage boxes, digital mixing consoles, DSP units, intercom panels, monitoring controllers, DAW computers, and any ancillary equipment such as VoIP gateways or video codecs. For each device, note whether it connects via copper RJ45, SFP fiber, or SFP+ 10 GbE. Add 20 to 30 percent overhead for future expansion, temporary connections for guest engineers, and management access points.

For a small project studio with a single control room and one live room, a 16-port or 24-port switch is typically sufficient. Mid-sized facilities with multiple control rooms, a machine room, and several tracking rooms often require 48-port units. Large broadcast centers or post-production houses may need chassis-based systems with modular line cards that support 96 or more ports. When linking multiple switches, ensure you have dedicated SFP+ uplink ports for 10 GbE fiber connections between closets or rooms. Avoid using copper RJ45 ports for inter-switch links in critical paths because twisted-pair copper has higher latency and is more susceptible to EMI over long runs.

Quality and Reliability in Mission-Critical Environments

In a production studio, downtime directly translates to lost revenue and missed deadlines. Consumer-grade switches from home networking vendors are not engineered for the thermal, electrical, and mechanical demands of 24/7 professional use. Their power supplies lack the filtering and redundancy needed to maintain stable operation under fluctuating mains voltage. Their cooling fans are often undersized or use sleeve bearings that fail within two to three years. The switch silicon itself may have shallow packet buffers that overflow under sustained multicast traffic.

Vendors with proven track records in pro audio include Cisco (Catalyst 9200/9300 series), Netgear (M4250 series purpose-built for AV), Luminex (GigaCore series), and AudioScience (custom-configured switches). These models offer features such as redundant hot-swappable power supplies, side-to-side airflow designed for equipment racks, and extended operating temperature ranges. Industrial-rated switches add conformal coating on circuit boards to protect against humidity and dust, plus vibration resistance for mobile or touring use. While these switches cost more upfront, the total cost of ownership over five years is often lower due to fewer failures, less troubleshooting time, and higher resale value.

Power over Ethernet (PoE) Budgeting

Many modern AoIP devices can be powered directly through the Ethernet cable using Power over Ethernet. This eliminates the need for separate AC power adapters, simplifies cable management, and allows centralized UPS backup. PoE+ (IEEE 802.3at) delivers up to 30 watts per port, sufficient for most audio interfaces, small stage boxes, and intercom panels. PoE++ (IEEE 802.3bt) delivers up to 60 watts (Type 3) or 100 watts (Type 4) per port, necessary for devices with motorized preamps, large touchscreens, or integrated DSP processing.

When evaluating PoE switches, pay close attention to the total PoE budget. A 24-port switch marketing PoE+ on all ports may have a total budget of only 190 watts, meaning it can deliver full 30 watts to at most six ports simultaneously. If you connect 24 PoE+ microphones, the switch will either shut down ports or brown out, causing erratic device behavior. Calculate your total PoE draw by summing the maximum power consumption of every powered device, then add 20 percent headroom. For studios with many PoE devices, consider a switch with a high total budget or a PoE injector panel between the switch and the devices. Also, remember that PoE switches generate more heat, so ensure your rack has adequate front-to-rear airflow and that the switch’s fan direction matches your rack cooling orientation.

Network Speed and Throughput

Gigabit Ethernet (1000BASE-T) is the absolute minimum for any professional AoIP deployment today. A single 24-bit, 96 kHz audio channel over Dante consumes approximately 5 to 6 Mbps of bandwidth. A 64-channel bidirectional flow uses roughly 640 Mbps, leaving ample headroom on a Gigabit link for control traffic and occasional bursts. However, if you are running 128 or more channels, or if you are combining audio with uncompressed video-over-IP, you will need 10 Gigabit Ethernet for backbone connections between switches and for high-density device connections.

10GBASE-T over copper Cat6a cabling works well for distances up to 100 meters and is backward compatible with Gigabit, simplifying migration. SFP+ fiber connections offer lower latency, better electrical isolation, and longer reach — up to 10 kilometers with single-mode optics. For very large facilities, consider 25 GbE or 40 GbE uplinks using QSFP+ ports. While these speeds are overkill for audio alone, they future-proof the network for video and allow massive headroom for uncompressed multichannel audio alongside metadata, control, and monitoring traffic. When comparing switches, look at the backplane switching capacity and forwarding rate (measured in millions of packets per second) to ensure the switch can handle full line-rate throughput on all ports simultaneously.

Managed vs. Unmanaged Switches

Unmanaged switches are plug-and-play devices with no configuration interface. They forward all traffic indiscriminately, do not support VLANs, and cannot prioritize audio packets. In a very small, dedicated audio network with fewer than eight devices and no external network connections, an unmanaged Gigabit switch can work. However, any scenario involving more than a handful of devices, mixed traffic types, or integration with a building network requires a managed switch. Managed switches provide:

  • VLANs (Virtual LANs) — Partition the physical network into isolated logical segments. Place audio traffic, control traffic (Dante Controller, web GUIs), and management traffic (SSH, SNMP) on separate VLANs to prevent broadcast storms and improve security.
  • IGMP Snooping — Monitors Internet Group Management Protocol messages to learn which ports have joined which multicast groups. Only forwards multicast streams to ports that have requested them, preventing switch flooding and preserving bandwidth.
  • IGMP Querier — When a network has multiple multicast sources, the querier ensures that only one switch is responsible for managing group membership. Without a properly configured querier, multicast traffic can behave unpredictably.
  • Quality of Service (QoS) — Classifies and prioritizes traffic based on DSCP or 802.1p tags. Audio traffic should be placed in the highest priority queue (typically queue 4 or 5) with strict priority scheduling to ensure it is never delayed by best-effort traffic.
  • Spanning Tree Protocol (STP/RSTP/MSTP) — Prevents network loops when switches are connected redundantly. Rapid Spanning Tree (RSTP) converges in seconds, and Multiple Spanning Tree (MSTP) allows load balancing across multiple VLANs.
  • Port Mirroring and SNMP — Port mirroring sends a copy of traffic from one port to a monitoring port for packet analysis. SNMP (Simple Network Management Protocol) integrates with network monitoring tools to alert you to port errors, high CPU utilization, or temperature thresholds.
  • Jumbo Frame Support — While not essential for all AoIP protocols, jumbo frames (MTU of 9000 bytes) can improve efficiency for some AES67 implementations by reducing header overhead. Ensure the switch supports configurable MTU per port.

For any professional studio where audio quality and reliability are non-negotiable, a managed switch is mandatory. The incremental cost over an unmanaged switch is small compared to the troubleshooting time and potential session losses caused by an unmanaged network.

Jitter, Clocking, and PTP Support

Network jitter — the variation in packet arrival time — is a critical concern for AoIP. While protocol receivers include phase-lock loops and jitter buffers to smooth out timing variations, excessive jitter forces larger buffer sizes, which increases latency. For live monitoring or real-time performance, you want the smallest possible buffer, which means the lowest possible jitter. Switches that use cut-through forwarding (where the packet begins egress before the entire packet has arrived) introduce less latency than store-and-forward switches, making them preferable for time-sensitive audio streams. Many purpose-built AV switches support cut-through mode on all ports.

For AES67 and AVB networks, PTP (Precision Time Protocol) clocking is essential. PTP boundary clocks sit at the edge of network segments and regenerate the clock signal, reducing jitter accumulation across long chains of switches. If your switch does not support PTP hardware timestamping, the clock recovery precision degrades. Some enterprise switches can be configured as PTP transparent clocks, which measure the residence time of PTP packets and correct for it, achieving sub-microsecond accuracy. When selecting a switch for AES67, verify that it supports the SMPTE ST 2059-2 PTP profile or the IEEE 802.1AS profile, and confirm that hardware timestamping is available on the ports you plan to use for audio.

Network Topology, Redundancy, and Cabling

Star Topology and Collapsed Core Design

The simplest and most reliable topology for studio AoIP is a star: every device connects to a single centralized switch. This makes troubleshooting straightforward because any problem can be isolated to a single cable, port, or device. For larger facilities, a collapsed core design uses two redundant switches in a primary-backup configuration. Critical devices such as the main mixing console, the primary DAW interface, and the master clock generator are dual-homed — connected to both switches simultaneously. In the event of a switch failure, traffic automatically fails over to the backup with minimal interruption. This approach requires switches that support Link Aggregation Control Protocol (LACP) or active-active redundancy protocols like Cisco’s StackWise or Netgear’s stacking.

Cabling Best Practices

In a studio environment, electromagnetic interference from power cables, dimmer racks, analog audio snakes, and data server rooms can corrupt Ethernet signals. Shielded twisted-pair cables (STP or S/FTP) are strongly recommended. Cat6a cable supports 10 GbE up to 100 meters and offers superior EMI rejection compared to Cat5e or unshielded Cat6. For permanent wall-plate runs, use solid-core cable terminated on punch-down keystone jacks. For patch cables between wall plates and devices, use stranded-core factory-terminated cables. Pre-terminated cables with molded boots are less likely to have installation errors than field-terminated cables.

Fiber optic cabling is the gold standard for runs over 100 meters or for connections between buildings. Single-mode fiber (OS2) supports distances up to 10 kilometers with SFP+ optics and is future-proof for higher speeds. Multimode fiber (OM3 or OM4) is sufficient for runs under 300 meters in a single facility. Fiber also provides complete electrical isolation, eliminating ground loop problems that can plague copper Ethernet connections between distant racks.

Power and UPS Considerations

Every switch and network-adjacent device should be connected to a UPS (Uninterruptible Power Supply) with automatic voltage regulation. Sized to provide at least 30 minutes of runtime at full load, the UPS allows for an orderly shutdown during a power outage and protects against voltage sags that can cause switch reboots. For critical studios, consider dual UPS feeds: one for the primary switch and one for the backup switch, each on separate electrical circuits. Network-attached UPS units with SNMP cards can send alerts when mains power fails or battery capacity drops.

Security and Network Isolation

Your AoIP network should be isolated from general office internet traffic to prevent bandwidth competition and security breaches. The simplest approach is a physically separate network with its own switches and no connection to the outside world. If remote access is required — for remote mixing, VoIP telephony, or system monitoring — place a firewall between the audio VLAN and the corporate network or internet. Configure the firewall to allow only the minimal set of ports needed: UDP 8700-8702 for Dante discovery, TCP 1433 for AES67, and RTP/AVP media streams on dynamically negotiated ports. Disable unused switch ports and enable MAC address filtering to prevent unauthorized devices from connecting. Change all default passwords on switches and AoIP devices, and disable Telnet in favor of SSH for remote management.

Budgeting and Total Cost of Ownership

When budgeting for AoIP network hardware, consider the total cost of ownership over three to five years, not just the initial purchase price. A cheap consumer switch may cost $100 but fail after 18 months, requiring emergency replacement and causing lost studio time. A purpose-built managed switch from a reputable vendor costs $800 to $2,500 for a 24-port PoE+ model, but offers redundant power, industrial cooling, warranty support, and configuration features that reduce troubleshooting time. Factor in the cost of shielded Cat6a cabling ($200 to $500 per drop including installation), fiber runs ($500 to $2,000 depending on distance and termination), UPS units, and network monitoring software. An investment of $3,000 to $8,000 for a small to mid-sized studio network is reasonable and pays for itself through reduced downtime and improved audio quality.

Implementation and Testing

Before connecting any AoIP devices, create a detailed network map showing every device, IP address, VLAN assignment, switch port number, and cable label. Assign static IP addresses or configure DHCP reservations for all permanent devices. Verify cable continuity with a tester that checks all four wire pairs, then run a ping sweep to confirm Layer 2 connectivity. Configure VLANs, enable IGMP snooping with querier, and set QoS policies before plugging in audio equipment. Use Dante Controller or a similar tool to stress-test the network by routing multiple channels and monitoring latency graphs. A healthy network should show consistent latency within the protocol’s claimed specification — typically 250 microseconds or less for Dante on a properly configured switch. If you see jitter spikes, investigate switch buffer usage or incorrect QoS settings.

Conclusion

Selecting the right AoIP switches and network hardware is a technical decision that directly impacts your studio’s sound quality, reliability, and scalability. Prioritize managed switches with sufficient port density, PoE budget, and support for IGMP snooping, QoS, and PTP. Invest in shielded cabling, a star or collapsed-core topology, and a robust UPS. Isolate the audio network from general traffic and secure it against unauthorized access. With careful planning and a willingness to invest in quality infrastructure, you will build a network that delivers flawless audio transport for years. For further reading, consult the Dante Controller manual, the AES67 standard documentation, and Cisco’s guide to multicast design for media networks. A well-designed network is invisible when it works perfectly — and that is exactly the goal.