The latency of the MADI I/O is four samples.
The M-32 DA Pro creates an entirely new output signal and does not pass on any
embedded information. One exception are SysEx messages (incl. MIDI over MADI) that are
passed on between the ports chosen in the MIDI Remote settings.
10.3.3. MADI Port Mirroring
A redundant MADI connection protects from loss of audio in case of a single cable failure. To achieve
redundancy, the receiver must support MADI redundancy. The sender must send two identical MADI
signals on two outputs, usually the coaxial and optical ports.
The M-32 DA Pro features independent routing for both MADI output ports. For this reason, a "mirroring"
of the signal must be manually created. In order to do this, the routing of the two MADI outputs should be
configured to contain the same routing.
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 DA Pro sends different
audio signals on both ports. Always ensure that the routing is correct for both output ports.
10.4. AVB Output Streams
The AVB streams
leaving
the M-32 DA 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
. See Section 5.4, “AVB Network Latency” for details on AVB latency.
The output streams of the M-32 DA 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
DA Pro does not include an AVDECC controller.
Outgoing AVB streams are monitored by the device. The possible states of the color indicator bar of
each output stream are the following:
Description
Indicator
Possible solution
Disabled
grey
Create routing
Disabled
orange
Create connection with AVDECC
controller
Streaming/Transmitting
green
SR mismatch
red
Verify that the sample rates of
talker and listener are identical
Waiting
yellow …
Wait for listener to be ready
Listener Fail
red
Verify proper listener
configuration
No Bandwidth
red
Use faster network speed (1
GBit/s instead of 100 MBit/s)
Domain Boundary
red
Reconnect all devices and reboot
switch
Internal Error
red
Reboot device
RME M-32 DA Pro User’s Guide
47
| 10.4. AVB Output Streams
