Dante Device and Channel Names: Build Routes That Recover

TL;DR — Dante subscriptions identify a transmit channel by its channel name and device name, so naming is part of the routing design rather than cosmetic labeling. Give every device a unique, stable role-based name and every channel a clear source name. Export the baseline before renaming, wait for changes to save, inspect affected subscriptions, and verify audio identity. A correctly prepared replacement can inherit the failed device's old name and allow compatible receivers to restore routes.

Names are routing identities

Dante routes a receive channel to a named transmit channel on a named device. A subscription such as Kick@Stagebox-A means the receiver is looking for the transmit channel Kick advertised by the device Stagebox-A.

The physical socket number, console strip name, host product name, and Dante channel name may describe related things, but they are not automatically the same field. Keep those identities aligned in the patch documentation.

The soft patch versus physical patch guide explains the boundary between logical mapping and physical connections.

Build a stable naming convention

A useful device name should tell a technician what role the endpoint performs and distinguish repeated hardware without depending on its temporary location in a controller window.

Choose a pattern such as:

<system>-<role>-<position-or-number>

Examples might include PA-Processor-L, Stagebox-A, Monitor-Console, or Record-Interface-1. The exact vocabulary matters less than consistency across the network, Rider, switch-port description, equipment label, and saved preset.

Apply these rules:

• keep every device name unique across the reachable Dante network;
• use short ASCII names that comply with current Dante device-name rules;
• avoid spaces, punctuation, or non-Roman characters that the device rejects;
• keep the name stable when the role is stable;
• add a number or position only when it distinguishes real endpoints;
• do not put transient facts such as today's IP address or operator name in the identity.

Dante device names follow hostname-style restrictions and are case-insensitive. Channel names allow a wider character set but still have reserved characters and must be unique on their device. Confirm the current limits for the installed Dante firmware rather than assuming every generation accepts the same length.

Name channels for the signal, not only the connector

Channel names should help a receiver recognize the intended source. Kick, Vocal-A, Playback-L, or PA-Drive-L carries more operational meaning than Input 1 when the route crosses several devices.

Preserve the physical connector separately:

This separation makes a repatch visible. If Kick moves from socket 1 to socket 9, the source identity can remain clear while the physical patch record changes.

Avoid putting several unrelated facts into one channel name. Sample rate, gain, phantom power, cable ID, and destination ownership belong in dedicated fields or notes, not in a name that will become unreadable in the routing matrix.

Understand what renaming changes

Renaming a Dante device or transmit channel creates a different routing identity. Receivers subscribed to the old channel@device name may show an unresolved subscription because the requested source is no longer advertised.

Use a controlled rename procedure:

1. export or record the current device names, channel names, subscriptions, and presets;
2. identify every receiver that depends on the name being changed;
3. protect the affected audio destinations;
4. rename one device or channel group at a time;
5. wait at least several seconds for routing changes to save before disconnecting or powering down;
6. inspect unresolved, pending, warning, and error states;
7. rebuild approved subscriptions and verify audio identity at the real destinations;
8. update the Rider, switch labels, presets, and recovery records.

Do not rename endpoints during a live show merely to tidy the matrix. A naming migration is a routing change and needs the same ownership and verification as a patch change.

Use names to support hardware replacement

Because the receiver subscribes to a name, a compatible replacement device can be prepared to assume the failed endpoint's identity. Remove the failed device from the network, configure the replacement with compatible firmware, sample rate, clock, network mode, latency, and channel layout, then assign the old device and channel names.

Receivers that still store those named subscriptions can restore routes to the newly advertised source. This is a recovery mechanism, not proof that the replacement carries the correct signals.

Verify:

• the old device is truly disconnected so no duplicate name exists;
• the replacement exposes the required transmit channels;
• sample rate and clock domain are compatible;
• primary and secondary network modes match the design;
• each receive channel reports a healthy subscription;
• distinct test signals reach the intended outputs;
• preamp gain, phantom power, processing, and physical sockets match the baseline.

The Dante sample-rate mismatch guide covers the format checks required before a named route can carry compatible audio.

Resolve duplicate and placeholder names safely

Device names must be unique. If two endpoints appear with the same intended name, one may adopt a temporary conflict name. Treat that as an identity fault, not a harmless display issue.

First identify the hardware using its product details, IP information, switch port, or supported front-panel identify function. Then:

1. protect destinations that may receive the wrong source;
2. disconnect or isolate the unintended duplicate where authorized;
3. assign each active endpoint a unique approved name;
4. wait for discovery and saved state to settle;
5. inspect all subscriptions that reference either identity;
6. test audio by source, receiver, and physical destination.

Never guess which identical box is which based only on its row position in Dante Controller. The matrix can be filtered and reordered, and a mistaken rename can redirect persistent subscriptions later.

Test the naming and recovery plan

1. Audit the live inventory

Compare device and channel names with rack labels, switch ports, the input list, output list, and saved presets. Resolve differences before failure testing.

2. Export the baseline

Save the approved routing state and record firmware, format, clock, latency, redundancy mode, and physical patch details required to reproduce each endpoint.

3. Test a controlled rename

On a noncritical path or test network, rename a source and observe how its receivers report the missing identity. Restore or rebuild the route and confirm the saved state persists.

4. Rehearse replacement

Remove the source, introduce the designated spare, apply the approved identity and compatible settings, and observe which subscriptions restore. Verify every channel with distinct audio.

5. Test removal and return

Power-cycle or disconnect the approved endpoint, then confirm unresolved subscriptions, discovery, route restoration, and audio recovery behave as documented.

Put naming ownership in the Rider

A buildable handoff lists each device name, role, hardware identity, physical location, switch port, Tx and Rx channel names, socket mapping, format, clock domain, redundancy mode, dependent receivers, spare-device procedure, saved preset, and responsible technician.

In Techrider.live, align Dante names with the input and output lists, invite the system, FOH, monitor, and recording engineers to edit the same Rider, save the accepted naming map, inspect history after a change, and export a dated PDF for load-in.

Dante naming checklist

• Every device has a unique, stable, role-based name.
• Transmit channel names identify real sources and are unique per device.
• Physical sockets, Rider sources, and Dante channels are cross-referenced.
• Existing subscriptions and presets are exported before renaming.
• Changes are given time to save before power or network removal.
• Duplicate names are resolved by identifying the physical hardware.
• Replacement routes are verified with distinct signals at real destinations.

FAQ

How should Dante devices be named?

Use unique, stable, role-based ASCII names that meet Dante's hostname-style rules, such as Stagebox-A or Monitor-Console. Apply the same vocabulary in the Rider, equipment labels, switch ports, and saved presets.

What happens to Dante subscriptions when a device is renamed?

Receivers may continue looking for the old device name and show an unresolved subscription. Treat the rename as a routing change: inspect affected receivers, rebuild approved routes, and verify audio identity.

Do Dante device names have to be unique?

Yes. Each device name must be unique on the Dante network. A conflict can cause a device to use a temporary altered name and can make routing identity ambiguous until the names are corrected.

Can Dante routes restore after replacing a device?

They can when the compatible replacement assumes the failed device's old name and exposes the expected channel names. You must still verify format, clock, network mode, physical patch, gain, and actual audio at every destination.

What is the difference between a Dante device name and channel name?

The device name identifies the endpoint across the network. A transmit channel name identifies one media source on that device. Together they form the source identity used by a receiver's subscription.

Make routing identity recoverable

Create one Rider that ties every Dante name to its hardware, socket, signal, receiver, preset, spare procedure, owner, and verification method before a failure forces the crew to improvise.