Implementing Audio Networking in Remote Broadcast Vans

Audio networking has become the backbone of modern remote broadcasting, replacing traditional point-to-point analog or MADI runs with Ethernet-based digital audio transport. In a remote broadcast van, space is tight, cable management is a constant battle, and the need for flexible audio routing during live events is high. Implementing audio networking in this environment allows engineers to move dozens, even hundreds, of audio channels over a single Category cable, reducing weight, setup time, and signal degradation. This guide walks through the full process, from protocol selection to final testing, so you can build a system that works reliably in the field.

Understanding Audio Networking Technology

Audio networking relies on digital protocols that encapsulate audio data into packets and transmit them over standard Ethernet networks. The three dominant protocols in professional broadcast are Dante (Audinate), RavenNA (ALC NetworX), and the open standard AES67. All three provide low-latency, high-channel-count transport across switched networks, but each has design considerations that matter inside a van.

Dante

Dante is the most widely adopted protocol in live sound and broadcast. It offers sample-accurate synchronization, automatic device discovery, and easy routing via Dante Controller software. Latency can be set at 0.25, 0.5, 1.0, or 5.0 milliseconds depending on the application. For remote broadcast vans, 0.25 ms or 0.5 ms is typical for microphone and intercom paths. Dante supports up to 512 x 512 audio channels per 1 Gbps link with 48 kHz, 24-bit audio.

AES67

AES67 is an interoperability standard that allows devices from different manufacturers to exchange audio over IP. It does not provide automatic discovery or centralized routing like Dante, so you need a separate control plane (such as WheatNet, Q-SYS, or a third-party management system) to set up connections. AES67 is valuable in multi-vendor vans where a Dante stagebox must talk to a RavenNA console, for example.

RavenNA

RavenNA is designed for ultra-low latency and deterministic performance, often used in high-end broadcast consoles and intercom systems. It supports up to 64 channels per stream and can run at sub-millisecond latency. While less common in rental inventory than Dante, RavenNA is the protocol of choice for many OB truck integrators because of its redundancy features and ability to run on standard IT hardware.

Most modern audio networking deployments in broadcast vans are hybrid, using Dante as the primary transport with AES67 gateways interfacing to legacy or third-party gear. Understanding how these protocols handle clocking, packet timing, and redundancy is essential before choosing a path.

Key Components Needed

Building an audio network inside a remote broadcast van requires more than just a switch and a console. Each component must be chosen for reliability under physical stress, temperature variation, and electrical noise common in mobile environments.

Network Switches

Managed switches are non-negotiable. Use switches that support IEEE 802.1p QoS (DSCP-based priority), IGMP snooping, and VLAN segmentation. For Dante, the switch must handle multicast traffic efficiently because Dante uses multicast for audio streams. Unmanaged switches lack IGMP snooping and will flood all ports with multicast packets, causing packet loss and audio dropouts at high channel counts.

Recommended switches for van environments include the Cisco Catalyst 3560-CX (compact, fanless) or the Netgear M4250 series, which has Dante-optimized profiles preloaded. Ensure the switch has enough SFP ports for fiber runs to external stageboxes or compound connections.

Audio Interfaces and Stageboxes

Stageboxes convert analog microphone or line signals into digital packets. Look for units with at least 8 or 16 inputs and outputs, redundant power supplies, and dual Ethernet ports for daisy-chaining or redundancy. Popular choices include the Audinate Dante-MY16-AUD cards for Yamaha consoles, the Focusrite RedNet series, and the Allen & Heath DT168. In a van, a pair of 16-input stageboxes in the equipment rack connected via a single Cat6 cable to the console area can replace an entire trunk of analog snakes.

Digital Audio Consoles

Modern broadcast consoles such as the Yamaha CL5 or Allen & Heath dLive come with integrated Dante ports. Older consoles can be fitted with Dante or AES67 option cards. When selecting a console for a van, consider the number of built-in DSP channels and whether the surface can be split from the processing engine (for remote control during events).

Cabling and Connectors

Use shielded Cat6a (STP) cables inside the van to reduce electromagnetic interference from generators, lighting dimmers, and RF transmitters. Cat6a supports 10 Gbps over shorter distances, which provides headroom for future expansion. For permanent van wiring, install Neutrik EtherCON connectors or fixed Panduit patch panels rather than consumer RJ45 plugs, which can loosen under vibration. Keep cable runs under 100 meters between active devices.

Software and Management Tools

You need Dante Controller (free) for routing, Wireshark for packet-level troubleshooting, and manufacturer-specific management software (e.g., Yamaha Console Editor, Allen & Heath Director). Additionally, network monitoring tools like PRTG or Observium can track switch port utilization, temperature, and link health during a broadcast.

Planning the Network Architecture for a Remote Broadcast Van

Before you start patching cables, create a logical diagram of your van's audio network. This diagram should show every device, its IP address, VLAN assignment, and redundant path. In a typical van layout, you will have at least three logical networks: audio (Dante/AES67), control (console IP, intercom, camera CCU), and Wi-Fi/guest. Use VLANs to separate these on the same physical switch to prevent broadcast storms and unauthorized access.

IP Addressing and Subnetting

All Dante devices must be on the same subnet and use static IP addresses within a dedicated range, for example 192.168.100.1/24. Do not use DHCP for Dante devices unless your switch provides a dedicated DHCP server with reservations. A single /24 subnet gives you 254 addresses, enough for a typical van. If you anticipate growth, use a /23 (510 addresses) but plan the subnet mask carefully to avoid spanning-tree loops.

Redundancy

For critical live broadcasts, implement Dante Redundancy (primary and secondary ports) or RavenNA Ring topology. With Dante, each device has two Ethernet ports: one for the primary network, one for the secondary. Both networks are physically separate switches. If a cable fails on the primary network, audio switches to the secondary in less than a sample period. This requires twice the number of switch ports and cable runs, but is standard practice in high-end OB trucks.

Power and Grounding

In a moving van, power quality varies. Use conditioned UPS units for all network switches and stageboxes. Ground loops are a persistent problem; ensure all network devices share a common ground reference through the chassis or via an isolation transformer on the network link where needed.

Setting Up the Network

With hardware installed, the next step is configuring the network switching infrastructure. The following sequence applies to any managed switch but check your specific vendor's CLI or web interface.

Step 1: Configure Switch Basics

Disable spanning-tree on edge ports where Dante devices connect (enable PortFast or edge-port mode) to prevent boot-up delays. Set the switch to use IGMP snooping with the querier enabled on the VLAN used for audio traffic. Without IGMP snooping, multicast audio floods every port, consuming bandwidth and CPU.

Step 2: Apply QoS Policies

Dante uses DSCP tags: audio streams are marked DSCP 46 (EF – Expedited Forwarding), PTP clocking uses DSCP 56, and control traffic uses DSCP 0. On your switch, map DSCP 46 to the highest priority queue and ensure strict priority queuing is enabled. Test with a packet generator or by measuring latency with a known signal to confirm that QoS is working.

Step 3: Create VLANs

Define VLAN 10 for audio, VLAN 20 for control, and VLAN 30 for guest/Wi-Fi. Assign the appropriate ports to each VLAN. The switch's IP address for management should be in the control VLAN. Do not route between VLAN 10 and the internet; audio traffic should never hit a router.

Step 4: Connect All Devices

Patch all Dante-enabled devices to switch ports assigned to VLAN 10. Use the shortest cable path inside the rack. Label both ends of every cable with source and destination device names. In a van, labels fade and cables get pulled; use a label maker with clear heat-shrink tubing for permanent identification.

Configuring Audio Devices

Once the network is live, configure each audio interface and console with a static IP address within your dedicated audio subnet. Open Dante Controller; it will discover all Dante devices on the network. If a device does not appear, check that IGMP snooping is not blocking multicast discovery packets, and verify the device is powered and on the correct VLAN.

Assigning Device Names and Latency

Rename each device in Dante Controller with a clear convention, for example Van-Stagebox-Left, FOH-Console, Intercom-Gateway. Then set the latency per device or per subscription. For microphones and intercom, use 0.25 ms or 0.5 ms. For program feeds or remote codecs, 1.0 ms is acceptable. Higher latency reduces CPU load on the switch but increases delay. Keep all devices on the same latency setting for consistency.

Routing Audio Paths

In Dante Controller, create subscriptions from transmitter devices (stagebox outputs) to receiver devices (console inputs). Subscription points can be mono, stereo, or multichannel. For a typical van, you might have: stagebox channels 1–8 to console input bus 1–8, wireless mic receivers to console inputs 9–16, and return feeds from console to intercom. Once subscriptions are created, save the Dante Controller file (an .XML file) and store it in the van's documentation binder. If a replacement device is swapped in, reload the file to restore routing.

Integrating Non-Dante Devices

If you have AES3 or analog gear that must be part of the network, use an AES67 bridge (e.g., Focusrite RedNet D64R) or a Dante-AES67 gateway like the Neutrik NYS-DLI. These devices convert between formats, but note that AES67 does not provide automatic clock synchronization. You must configure a PTP (Precision Time Protocol) grandmaster clock on the network, usually the console or a dedicated Dante clock source, and ensure all AES67 endpoints are PTP-slaved to that master.

Testing and Troubleshooting

Testing should happen in phases: offline bench test, van build test, and on-site test. Skipping any phase invites failures during a live event. Use the following methods to verify performance.

Latency and Jitter Measurement

Connect a signal generator to a stagebox input, route it through Dante to a console output, and measure the round-trip time with an oscilloscope. Acceptable round-trip latency for a live broadcast feed is under 2 ms. If latency exceeds 5 ms, check QoS settings and CPU utilization on the switch.

Packet Loss and Dropout Detection

Run Dante Controller's built-in diagnostics to view device statistics. Any non-zero packet loss on a subscription indicates a problem, likely from a bad cable, loose connector, or insufficient switch buffer memory. Use Wireshark to capture multicast traffic for a few minutes; filter for DSCP 46 frames to see if packets are arriving in sequence and on time.

Network Traffic Analysis

With all signals active, check switch port utilization. If any port exceeds 70–80% of its bandwidth, redistribute devices across ports or upgrade to a 10 Gbps uplink between switch stacks. In a van, a single 1 Gbps port can hold about 250 channels of 24-bit/48 kHz audio, but that includes overhead for PTP and control traffic. Keep headroom to 40%.

Common Issues and Solutions

  • Device not discovered: Check VLAN assignment, disable IGMP filtering temporarily, verify IP subnet match.
  • Audio breaks up or clicks: Check for clock synchronization errors. Ensure all devices are locked to the same PTP grandmaster.
  • Interference noise: Use shielded cable, check ground loops, isolate network switch from high-power AC lines inside the van.
  • Redundancy switch fails: Test by unplugging the primary network cable while audio is active; the secondary network should pick up within one sample. If it does not, check that both networks are correctly wired and that redundancy is enabled on each device.

Best Practices for Reliable Audio Networking

Building the system is one thing; keeping it reliable over years of road use is another. The following practices reduce downtime and simplify troubleshooting.

Use Shielded Cables Everywhere

Shielded Cat6a is not optional in a van. RF from nearby transmission masts, stadium Wi-Fi, and even the van's own generator can couple into unshielded twisted pair, causing packet errors. Terminate shields at the patch panel with a proper ground bond to the van's chassis earth.

Dedicated Network for Audio

Whenever possible, use a physically separate switch or VLAN for audio traffic alone. Do not share the Dante network with file transfers, video streams, or internet access. If space constraints force a shared switch, enable strict QoS and rate-limit non-audio traffic.

Regular Firmware Updates

Check for firmware updates on every Dante device, switch, and console before each broadcast season. Audinate releases Dante firmware updates that improve clock stability and add features. However, avoid updating firmware the day before a live event; test changes in a lab environment first.

Document Everything

Keep a wiring diagram, IP address spreadsheet, Dante Controller file, and switch configuration file in a binder inside the van. Also store digital copies on a USB drive attached to the console. When an engineer swaps in for a shift, they should be able to rebuild the entire network from scratch using those documents.

Implement Redundant Power

Every network switch, stagebox, and console should have dual power supplies connected to separate UPS units. A single UPS failure should not take down the entire audio network. In small vans, a redundant battery backup for the main switch is often enough.

Advanced Considerations

Remote Control and Monitoring

Many broadcasters now operate vans with a remote engineer monitoring from a central facility. Use a VPN router on the van's internet connection to access Dante Controller remotely over WAN. This allows you to reroute audio feeds or check device status without driving to the location. Ensure the VPN link has at least 10 Mbps upload speed for PTP timestamp accuracy.

Interfacing with OB Truck Compound Networks

When a van connects to a larger OB truck compound (e.g., for a major sports event), you may need to extend your audio network over fiber using SFP transceivers and single-mode fiber. Use a dedicated fiber pair for audio and another for control. Keep the fiber plant clean and dust-free; a dirty connector can introduce 10 dB of loss and cause link failures.

Future-Proofing with AVB

While Dante and AES67 dominate today, Audio Video Bridging (AVB) is gaining traction in automotive and professional audio. AVB uses IEEE 1722 and 802.1Qat to reserve bandwidth on the switch. Some newer consoles and stageboxes offer AVB ports. If you are building a van from scratch, consider a few AVB-compatible switches to stay ahead of the curve, but plan for a dual-protocol environment until AVB achieves broader adoption.

Conclusion

Implementing audio networking in a remote broadcast van is a complex but achievable task. By selecting the right protocol (Dante, AES67, or RavenNA), using managed switches with proper QoS and VLAN segmentation, and testing thoroughly under load, you can create a system that delivers pristine digital audio with minimal latency and maximum redundancy. The key is to plan ahead: document your IP scheme, label every cable, and train your engineers on the diagnostic tools. A well-built audio network will serve your van for years, enabling faster setups, fewer cable failures, and higher audio quality at every remote event.