Table of Contents
Advertisement
The receiving device usually ignores the audio contents of the two MADI signals.
Therefore, the redundancy may appear to be set up even though the M-32 AD Pro sends
different audio signals on both ports.
10.2. AVB Output Streams
The AVB streams leaving the M-32 AD Pro are described as "output streams". In this case, the device
acts as a talker. The talker defines the presentation time and therefore the latency across the network.
This is set per default to 2 ms.
The output streams of the M-32 AD Pro are by default empty, containing a clock signal but no audio
signal. To send audio with AVB, a routing must be created for each outgoing stream.
To establish a connection between a talker and a listener, an AVDECC controller is required. The M-32
AD Pro does not include an AVDECC controller.
Outgoing AVB streams are monitored by the device as follows:
Description
Disabled
Streaming/Transmitting
SR mismatch
Waiting
Listener Fail
No Bandwidth
Domain Boundary
Internal Error
10.2.1. Change AVB Output Stream Size
Each of the four AVB streams can have a size of 4, 8, 12 or 16 channels.
To change the amount of channels in the outgoing AVB stream on the device:
1. Open one of the four AVB tabs in the OUTPUT section.
2. Move the cursor to highlight the current AVB Stream Size and press the encoder.
3. Rotate the encoder to configure a new stream size and confirm by pressing the encoder again.
To change the amount of channels of the outgoing AVB stream:
1. Connect to the device remotely (see: Section 8.5.1, "Finding the Device on a Network").
RME M-32 AD Pro User's Guide
Indicator
grey
green
red
yellow ...
red
red
red
red
Possible solution
Create connection with AVDECC
controller
Verify that the sample rates of
talker and listener are identical
Wait for listener to be ready
Verify proper listener
configuration
Use faster network speed (1
GBit/s instead of 100 MBit/s)
Reconnect all devices and
reboot switch
Reboot device
10.2. AVB Output Streams | 42
Advertisement
Table of Contents
