Dante audio networking

A Dante transmitter packetises audio and sends it to one or more receiving devices. In a typical setup, a stage box transmits microphone channels to a mixing console, while the console sends mixes to output devices. Audio channels are assigned through subscriptions, commonly managed in Dante Controller. Discovery and control make the devices visible, but seeing a device does not by itself prove that every intended audio route is working.

The system uses network clock synchronisation so participating devices agree on the timing of digital samples. One eligible device becomes the clock leader, with other devices following its timing. Clock configuration, sample rate and receiver latency must suit the actual system. A signal-flow plan remains essential because a successful network subscription can still feed the wrong console input or an output that is muted.

• Confirm device compatibility, channel capacity and supported sample rates before allocating routes.
• Use suitable Ethernet cabling and switches with capacity for the intended traffic.
• Label devices and channels so the routing view reflects meaningful physical sources.
• Check clock status and subscription status separately, then verify audio by listening.

Network transport can replace many individual audio runs with a shared infrastructure. It allows sources to reach several destinations, such as a live console and a recording system, without an analogue split at every endpoint. This flexibility is valuable when a production changes, but it also means that routing becomes less visible than a collection of labelled copper connections. Documentation and disciplined naming become part of the audio system.

Dante does not make every network suitable for time-sensitive sound. Available bandwidth, switch behaviour, competing traffic and configuration all affect reliability. Some installations use a dedicated audio network; others use a properly engineered shared network. Neither approach excuses testing. A general-purpose network that works well for file transfers may still have unsuitable energy-saving features, multicast handling or traffic policies for a particular audio design.

Many Dante routes use unicast flows, while multicast can serve suitable one-to-many distributions. Flow limits and bandwidth matter as well as the headline channel count. Multicast requires appropriate network planning; enabling it indiscriminately is not a cure for routing problems. Where IGMP snooping is used, the switch design must also provide the required querier behaviour and be checked against the equipment guidance.

Redundancy is a specific supported mode, not a promise attached to every device with two sockets. Some dual-port products offer switched mode instead. For redundant operation, maintain separate primary and secondary network paths as specified by the manufacturer, and do not casually bridge them together. Shared power or a shared upstream component may still create a common failure point even when two cables are present.

At a conference in Dubai, a digital stage box supplies lectern microphones and playback channels to the main console. A recording computer receives a separate selection of sources through a compatible Dante interface. During preparation, the engineer gives devices descriptive names, chooses the project sample rate and confirms that each receiving device has an appropriate latency setting. The recording system is tested for both routing and local disk performance.

1. Build and inspect the network before opening the room to attendees, keeping audio and unrelated traffic under the agreed design.
2. Confirm that the intended clock leader is stable and that no device reports a clock or subscription error.
3. Route each source to its console input, then test the independent recording subscriptions.
4. Run programme material and speech through the complete system while monitoring for errors, dropouts and unexpected routing.

A late request for another recording feed is checked against device flow limits and network capacity rather than accepted solely because a spare connector exists. If redundant equipment is used, the engineer tests each path independently under controlled conditions. BarCoe Studios runs short hands-on live sound certificate courses for audio engineers that include a basic overview of Dante audio networking; see the audio engineers workshop for the course context.

Confusing a network link with a valid audio route can send troubleshooting in the wrong direction. A link light confirms only part of the connection. Mismatched sample rates, clock problems, exhausted flow capacity, device permissions or incorrect subscriptions can still prevent sound. Check status messages before replacing equipment, and distinguish an audio routing issue from a local console channel that is simply closed.

• Do not connect a secondary redundancy port to the primary network without checking the required operating mode.
• Avoid changing switch settings during a show without a tested recovery plan.
• Do not choose the smallest latency setting merely because it appears more professional.
• Keep firmware compatibility and configuration backups within the preparation process.

Dante and AES67 are related but not interchangeable terms. Some Dante devices can exchange AES67 streams when appropriately supported and configured, but this does not transfer every Dante discovery, routing or management feature to another ecosystem. Verify the exact device capabilities instead of assuming that any network audio port can communicate with every other one.