Page 89 - Dante Controller User Guide

Dante Controller User Guide

Figure 2 - Two multicast flows, with half the number of channels in each

Deleting Multicast Flows

Care should be taken when deleting a multicast flow, as the existing subscriptions will convert back to
unicast. This has the potential to result in exceeding the link capacity or maximum number of flows at the
transmit device, as multiple unicast flows will be established between the transmitter and its receivers. It
may be advisable to remove some or all of the audio routes prior to deleting the multicast flow.

Note: Certain Ethernet switches support IGMP (Internet Group Management Protocol), a protocol
that provides the ability to 'prune' multicast traffic, so that it travels only to those end destinations that
require that traffic. If this is the case, and IGMP is correctly configured on all the Ethernet switches,
then multicast audio will not flood throughout the network, but will instead be sent only over the links
required to deliver it to subscribed devices.

AES67 Flow

The AES67 Flow option is only available for AES67-enabled devices.
When AES67 Flow is checked, the selected channels will be added to an AES67 multicast flow. Only
AES67-enabled devices can receive AES67 flows. Dante devices cannot subscribe to AES67 flows from
other Dante devices.
RTP transmit flows (including AES67 flows) from non-Dante devices appear in blue at the far right of the
Routing tab of the Network View, and at the bottom of the Available Channels list in the Device View >
Receive tab. AES67 flows are identified by their transmit multicast IP addresses, rather than device
names.
For AES67-enabled Dante devices, each device transmit channel can simultaneously support an AES67
multicast flow and a standard Dante multicast flow.
AES67 flows support 8 channels. If more than 8 channels are selected for an AES67 flow, multiple flows
will be created.

Copyright © 2020 Audinate Pty Ltd. All rights reserved. -89-