Setting up Yamaha SWP1 series
IGMP snooping is enabled on the SWP1 Series by default, and does not need to be set.
Enable IGMP snooping when you wish to use multicasting in general. Even in that case, be careful to use a minimum amount of multicast. Dante configures routing with unicast by default, and multicast will not be required for most of small-to-mid scale Dante systems. To understand when the multicast settings of a switch need to be configured, it’s first necessary to understand multicast and "flows".
There are two audio signal transmission methods that can be used in a Dante network. One method is unicast, in which signals are transferred directly from one device to another specific device. The other method is multicast, in which signals are transferred to multiple devices within the network. By default, all audio transmission within a Dante network is unicast, and there is normally no need to change this setting. Now, let’s examine which method is better for sending the same audio signal from one device to several other devices.
In unicast, packets (audio signals) are duplicated for each device that the signal is sent to. You can set the routing for each of the signals separately without considering whether the signals are duplicates of each other. From the standpoint of efficient use of network bandwidth, unicast might not be ideal, but because it results in low switch loads and makes routing configuration easier, we recommend that you use it under normal circumstances.
On the other hand, with multicast, a single packet (audio signal) is split by the switch and delivered to multiple devices. At first glance, multicast may appear to be the all-around best method, but because the switch has to duplicate the packets for each port and transmit them to each device, multicast results in increased switch loads. Another drawback to multicast is that it results in the transmission of packets to ports that don’t need them. This transmission can be prevented through the use of the Internet Group Management Protocol (IGMP). Each device transmits IGMP messages to report which multicast addresses they need. The switch then remembers which ports are connected to devices that have registered for a specific multicast address and filters the multicast traffic accordingly. This function is referred to as IGMP snooping. Thus, when multicasting audio, you need to be sure to enable IGMP snooping on the switch (if you don’t, multicast packets will be duplicated and transferred to each port). Please remember that the switch may need time (tens of seconds) to determine which ports on the switch are connected to the devices that require multicast data, before IGMP snooping will form the intended multicast groups. You should also remember that multicast is a special setting that can only be configured from the Dante Controller software and that multicast increases the workload of the switch.
In most cases, the audio data that travels through a cable will not exceed 512 channels (at 48 kHz), so in normal circumstances, unicast is the best choice. That being the case, when is multicast absolutely necessary? It is when a transmitter runs out of flows.
When you configure Dante audio routing, flows are created automatically. Flows are the units of transmission for audio data. Multiple channels are grouped into a single flow before being transmitted. Unicast flows can contain up to four channels of audio data. For example, if channel 1 is assigned to a specific receiver, even if no other channels are assigned to the receiver, packets that are big enough for four channels will be sent to the receiver. In connections to the same receiver, because the use of flows with open channels is prioritized, no new flows will be created until all four channels in the most recently created flow are filled.
There are limits to the number of flows that can be assigned to a transmitter or receiver. For example, CL/QL Series consoles and R Series I/O racks can all send and receive 32 flows. For the Rio3224-D, which has 32 analog inputs, to send all 32 channels to a single Dante device, 32/4 = 8 flows are sufficient. However, using unicast flows to send the channels to 4 devices (CL/QL series consoles, for example) requires the use of all 8 × 4 = 32 flows.
Further, the maximum number of channels that can be sent is 32 × 4 =128 in the example above, but because the flows assigned to each Dante device contain four channels, the more flows there are that don’t use all four channels, the lower the actual number of channels that can be sent. Therefore, if a transmitter runs out of the available flows, multicast is necessary to reduce the number of transmitted flows. You can check the number of transmitted flows using the Dante Controller software (under Transmit Flows in the Transmit tab of the Device View). A notification will appear if there are not enough available flows. Also, it’s possible for receivers to not have enough flows in special cases, such as when single channels are received from a large number of devices. In such a case, multicast will not reduce the number of flows, so it’s necessary to reconsider the routing itself.
In conclusion, if there are not enough flows available for transmission, use the Dante Controller software to configure multicast, and reconfigure the network so that less flows are used. In such a case, do not use the routing functions that can be configured from specific Dante devices and software such as CL/QL series console and MTX-MRX Editor; instead, only configure the routing using Dante Controller. Be careful to keep the number of multicast flows (channels) to the minimum, because multicast flows increase the load that the switch is subjected to. Up to eight channels can be grouped into a multicast flow, further increasing their efficiency.