Dante Controller Routing Basics: Create and Verify Subscriptions

TL;DR — Dante Controller routes a transmitter channel to a receiver channel by creating a subscription at their intersection in the Routing view. Confirm device identity, channel names, sample rate, clock state, and access before clicking. A green checkmark confirms that the subscription is established, not that the source is correct or audible. Pass identifiable audio, verify the physical destination, save the accepted state, and document ownership before handoff.

A Dante route is a receiver subscription to a transmitter

Dante Controller displays transmit channels across the top of the Routing view and receive channels down the side. Clicking an intersection asks that receiver channel to subscribe to that transmitter channel. You do not need to build a channel bundle first; individual channels can be routed independently.

This guide owns the basic create-and-prove workflow. Use the subscription error guide when Controller reports a warning or failure, and the flow limits guide when device capacity is the constraint.

Prepare the network view before routing

Confirm that Controller is watching the intended network

Select the wired interface connected to the production Dante network. Confirm the expected devices appear, then match each software name to a physical label, rack position, model, and address. Do not route solely from a familiar name; names can survive moves or be duplicated after service work.

Expand only the devices and channels you need

Use device and channel filters where appropriate, then expand the required transmitter and receiver. Stable, descriptive names reduce matrix mistakes. If names need to change, do that under controlled conditions and update the patch documentation because subscriptions depend on device and channel identity.

Check compatibility and authority

Confirm transmitter and receiver sample rates, clock synchronization, channel availability, domain membership, and permissions. A visible endpoint may still be unavailable for configuration. The sample-rate mismatch guide and Domain Manager roles guide cover those boundaries in depth.

Create a subscription in a controlled sequence

1. Mute or protect the downstream destination if unexpected signal could be harmful.
2. Identify the exact transmitter device and channel from the approved input or output list.
3. Identify the exact receiver device and channel at the physical destination.
4. Click their intersection once and wait for Controller to report the final state.
5. Pass an identifiable source and verify meters at transmitter, receiver, and audible destination.
6. Label the accepted route in the production record before creating the next critical path.

Route one logical group at a time. For example, complete and test playback left and right before adding talkback or record feeds. A disciplined sequence makes an offset row or column easier to find than a large untested block of clicks.

Read the route state correctly

Hover or open details before changing anything when a route does not settle. Preserve the reported message, device state, and time. Repeatedly clearing and recreating a route can erase useful evidence without fixing the cause.

Verify beyond the matrix

A route test should use a source that can be identified unambiguously: a spoken channel name, tone at an approved level, or known program segment. Follow the signal through the transmitter meter, network subscription, receiver meter, device output, and final destination.

For critical paths, test these conditions:

• normal operation with the complete show patch active;
• device restart or approved network reconnection;
• primary/secondary failover where redundancy is designed;
• loss and restoration of the source;
• preservation of the route after Controller closes.

Dante subscriptions are stored by the devices, so Controller does not normally need to remain open after a route is established. Closing the application is not an acceptance test by itself: prove that audio continues and that the route returns after the approved recovery scenario.

Remove or change routes safely

Treat unsubscribe as a production change. Confirm the route owner and every destination that depends on the transmitter, mute or protect outputs, clear the intended intersection once, then verify that only the expected feed stopped. One transmitter can serve multiple receivers; removing one receiver's subscription does not necessarily remove the others.

When replacing a source, document the old and new crosspoints. Avoid creating a temporary parallel path unless the receiving system is designed to combine both signals safely.

Routing acceptance checklist

• Controller is using the intended wired network interface.
• Device names are matched to physical endpoints and network roles.
• Transmit and receive channel names match the approved patch.
• Sample rate, clock state, access, and channel availability are valid.
• Each subscription reaches a stable final state.
• Identifiable audio passes through the physical destination.
• Levels, polarity, channel order, and downstream mute state are correct.
• Critical restart, reconnect, and redundancy tests pass where applicable.
• The accepted route list, owner, test time, and rollback are documented.

FAQ

How do I route audio in Dante Controller?

Open the Routing view, find the transmitter channel across the top and receiver channel down the side, then click their intersection. Wait for a stable route state and pass identifiable audio through the real destination before accepting it.

What is a subscription in Dante Controller?

A subscription is a receiver channel's request for audio from a named transmitter channel. The receiver stores that relationship and attempts to restore it when the named source is available and compatible.

Does Dante Controller need to stay open for audio to work?

Normally, no. Dante devices maintain established subscriptions without the Controller application running. Verify this behavior and the approved restart or reconnection case on the actual system.

What does the green checkmark mean in Dante Controller?

It means the subscription is established. It does not prove the transmitter carries the intended source, the level is safe, or the physical destination is correct; those require an audio test.

Can one Dante transmitter feed multiple receivers?

Yes. A transmit channel can feed multiple receiver channels, subject to the device's flow capacity and network design. Check the unicast versus multicast guide when fanout grows.

Put the accepted Dante patch in the Rider

Record transmitter and receiver devices, channel names, network role, format, route state, test source, physical destination, owner, validation time, and rollback in Techrider.live. Invite the system and console engineers to edit the same rider, save the accepted patch, and inspect history before changing a production route.