Dante Flow Limits: Diagnose No More Flows Errors

TL;DR — A Dante flow is a packet stream that carries one or more channels between devices. Flow capacity is separate from channel count: a device can have free channels yet lack another transmit or receive flow. Read the subscription tooltip, identify whether the limit is on the transmitter or receiver, count destination relationships, then consolidate routes or intentionally create multicast. Verify device-specific limits and network bandwidth before changing a working system.

A flow is not the same as a channel

A Dante subscription connects one transmit channel to one receive channel, but the network carries those subscriptions inside flows. A unicast audio flow normally carries up to four channels from one transmitter to one receiving device. Adding channels between the same pair may reuse that flow; sending the same channel to another receiver needs another unicast flow.

Device flow capacity depends on its Dante implementation, hardware, and firmware. Never infer the limit from the number of channel labels alone.

The Dante subscription errors guide explains how to read routing-matrix states before changing the design.

Diagnose the failed side first

1. Read the subscription tooltip

Hover over the failed subscription in Dante Controller. Record the exact transmitter, receiver, channels, and error. No more flows (TX) points to exhausted capacity on the transmitting device. No Receive flows points to the receiving device subscribing to too many distinct transmitters or streams.

Do not treat every red icon as a flow error. Format, clock-domain, scheduler, identity, and discovery failures need different fixes.

2. Draw the source-to-destination relationships

List each transmitter and the receivers consuming its channels. Four channels sent from one stagebox to one console can commonly share one unicast flow. The same channel sent to FOH, monitors, broadcast, recording, and a lobby processor creates separate destination relationships and may exhaust transmit flows.

On the receive side, many channels from one transmitter can be efficient, while a few channels from many different transmitters can consume more receive flows.

3. Confirm the device limits

Use the manufacturer's current documentation and Dante Controller device information to confirm supported transmit flows, receive flows, and channels per flow. Limits vary. Firmware may affect capabilities, so record the installed version before planning a change.

4. Remove abandoned routes

Delete obsolete test, recording, spare-console, or previous-show subscriptions only after confirming their owner. A route matrix often accumulates destinations that are no longer in the operational plan. Removing a legitimate safety, record, or broadcast feed merely to clear an error is not a fix.

Choose the least disruptive remedy

Multicast can reduce transmitter fanout because multiple receivers join one multicast flow. It is not a universal capacity button: multicast can propagate across links, consumes bandwidth even with no active receivers, and requires a deliberate switch design. Read the unicast versus multicast guide before converting routes.

Test capacity under show conditions

Build the complete show route, including record, broadcast, lobby, comms, backup, and spare paths. Confirm every subscription, then inspect transmit and receive utilization, flow status, clock stability, and latency counters. Exercise the planned failover and restore sequence.

If deleting a multicast flow, remember that receivers may return to unicast. That conversion can suddenly exceed transmitter flow capacity or link bandwidth. Remove or redesign dependent routes before deleting the flow, then retest.

Document the routing budget

Record:

• each device's model, firmware, channel capacity, and Tx/Rx flow limits;
• source-to-destination relationships and their unicast or multicast type;
• multicast channel groups, owners, and switch requirements;
• normal and peak link utilization;
• reserved capacity for backups and temporary feeds;
• the approved change, validation, rollback, and escalation owner.

Keep the operational summary with the digital audio network tech rider, not only in one engineer's Controller view.

Dante flow-limit checklist

• The exact subscription tooltip is recorded.
• The exhausted side is identified as Tx or Rx.
• Device-specific flow limits and firmware are confirmed.
• Current source-to-destination relationships are mapped.
• Obsolete routes are removed only with owner approval.
• Any multicast change includes bandwidth and IGMP review.
• Full show load, failure, restore, and rollback are tested.
• Routing capacity and ownership are documented.

FAQ

What is a flow in Dante?

A flow is a stream of network media packets carrying one or more channels from a transmitter. Unicast flows serve one receiving device; multicast flows can serve multiple receivers.

What does no more flows mean in Dante Controller?

It means the indicated device cannot create or accept another required flow. The tooltip distinguishes exhausted transmitter capacity from exhausted receiver capacity.

How many channels fit in a Dante flow?

A unicast audio flow commonly reserves space for up to four channels, but device capabilities vary. Multicast channel capacity also varies by device. Confirm the current manufacturer's specification.

When should I use multicast in Dante?

Consider multicast when the same channels feed several receivers and unicast fanout is inefficient. Review switch configuration and every affected link because multicast can increase network-wide traffic.

How do I fix a Dante flow limit error?

Identify the exhausted side, map device relationships, confirm actual limits, remove obsolete subscriptions, and consolidate or redesign routes. Use multicast only when its bandwidth and switch behavior are understood and tested.

Keep capacity visible before show day

Flow limits become manageable when routing demand, reserved capacity, multicast ownership, and rollback are visible to the whole production team. Keep that record in Techrider.live with the current input list and network notes so collaborators can edit, save, and inspect history without circulating another stale file.