Dante Multicast Flow Setup: Create, Verify, and Remove It Safely

TL;DR — Create a manual Dante multicast flow only when one transmitter must feed enough receivers to justify a shared stream and the network is prepared to carry it. In the transmitter's Device View, choose Create Multicast Flow, select only the required channels, create the flow, then subscribe receivers normally. Verify IGMP behavior, every affected link, receiver latency, and real audio under full load. Save the baseline and define how to remove the flow before changing production.

A multicast flow changes transport, not the channel patch

A Dante transmit channel can be carried in a unicast flow for a specific receiver or placed into a multicast flow that multiple receivers can join. Unicast and multicast can coexist on the same Dante device, and channels are selected individually for multicast transmission.

Receivers still subscribe to named transmitter channels in the Routing view. Creating a multicast flow changes how selected channels cross the network; it does not replace channel naming, subscriptions, clocking, format compatibility, or destination testing.

Use the unicast versus multicast guide to choose the transport and the multicast bandwidth guide to calculate and monitor its link-by-link cost. This guide owns the operational create, verify, and remove procedure.

Decide whether a manual multicast flow is justified

Multicast can reduce transmitter flow use when the same source feeds many receivers. It can also put the stream onto network links where it is not needed if multicast control is absent or incorrect. Do not convert a working unicast route merely because multicast sounds more scalable.

Before changing transport, record:

• the transmitter's current unicast and multicast flow use;
• every receiver that needs each selected channel;
• channel count, sample rate, encoding, and expected bitrate;
• switch path, uplinks, VLAN, querier, and IGMP snooping state;
• hardware and software receiver types plus their latency settings;
• a known-good preset or route record for rollback.

The smallest correct change is usually one logical program group, not every channel on the transmitter.

Create the multicast transmit flow

1. Reserve a maintenance window and notify route owners.
2. Open the transmitter in Dante Controller Device View.
3. Confirm device identity, firmware, clock, sample rate, and current flow state.
4. Choose Create Multicast Flow from the device's flow controls.
5. Select only the transmit channels required by the approved destination plan.
6. Review the selection, create the flow, and wait for Controller to report it.
7. In the Routing view, create or confirm receiver subscriptions to those named channels.

Channel capacity per multicast flow depends on the transmitter implementation and format. Controller exposes the valid selection for the device; do not assume a universal number. If the required group does not fit, use the smallest number of deliberate flows and document the split.

Verify the network before accepting audio

Follow every link that carries the flow

Measure transmitter access, switch uplinks, receiver access ports, and redundant legs separately. Compare traffic before and after the change. A healthy transmitter port does not prove a shared uplink has margin.

Prove IGMP behavior rather than assuming it

All Ethernet switches forward multicast, but managed multicast behavior depends on the design. Correct IGMP snooping and querier operation can restrict traffic to ports that requested the group. Incorrect IGMP configuration can interrupt delivery; no pruning can spread the stream more widely. Verify the running switch state and counters on the actual VLAN.

Test every receiver class

Subscribe each approved hardware and software destination, then pass identifiable audio under full production load. Confirm subscription state, clock, latency, channel order, level, and continuous playback. Software endpoints may have different latency constraints from hardware; do not infer one class from the other.

Test failure and restoration

Exercise only the failures the design claims to survive: receiver disconnect and reconnect, approved primary/secondary failover, switch restart in a redundant design, and transmitter restart in a maintenance window. Watch multicast membership recover, then confirm audio at every destination.

Do not clear counters or restart devices before capturing a failure. Record timestamps, subscriptions, multicast group or flow identity, link utilization, errors, latency events, and clock events. The Dante network health guide explains how to correlate that evidence.

Remove or roll back a multicast flow

Before deleting a flow, identify all subscribed receivers and protect their downstream outputs. Save the current route and device state, remove or replace affected subscriptions as the approved plan requires, then delete the intended multicast transmit flow from the transmitter's flow controls.

After removal, confirm whether Controller rebuilds required subscriptions as unicast and whether transmitter flow capacity remains sufficient. Pass audio again at every destination. A successful delete action is not proof that the replacement transport works.

Multicast flow acceptance checklist

• The fanout and transmitter flow budget justify multicast.
• Only approved transmitter channels are selected.
• Channel grouping respects the device's supported flow capacity.
• Switch topology, VLAN, IGMP snooping, and querier ownership are known.
• Before/after traffic is measured on every affected shared link.
• Hardware and software receivers pass stable full-load audio.
• Latency, clock, channel order, and physical destinations are verified.
• Approved failure and restoration tests pass.
• Baseline, flow identity, route list, owner, and rollback are documented.

FAQ

How do I create a multicast flow in Dante Controller?

Open the transmitter's Device View, choose Create Multicast Flow, select the required transmit channels, and create the flow. Then create or confirm normal receiver subscriptions in the Routing view and verify the network plus real audio.

When should I use a Dante multicast flow?

Use it when the same source must feed enough receivers that shared transport improves the transmitter flow budget, and only after confirming the network can carry and control the traffic. Keep simpler unicast routes when they meet the requirement.

Can Dante use unicast and multicast at the same time?

Yes. A Dante device can use both, and individual channels can be selected for multicast. Document which channels use each transport so troubleshooting and rollback remain clear.

How many channels can a Dante multicast flow contain?

There is no safe universal number for every device and format. Capacity depends on the transmitter implementation and operating format. Use Controller's valid selection and the manufacturer's current documentation for the exact endpoint.

How do I remove a Dante multicast flow?

Identify every dependent receiver, save the baseline, protect outputs, remove the intended transmit flow in Device View, and verify that required routes return using the planned transport. Retest real audio and link load afterward.

Put multicast ownership in the Rider

Record the transmitter, selected channels, receiver list, transport choice, switch path, IGMP owner, measured load, latency evidence, validation, and rollback in Techrider.live. Invite the system and network engineers to edit the same rider, save the accepted design, and inspect history before changing the multicast plan.