MADI-XX
43
How is audio monitoring streamed?
Audio is streamed using open standard RTSP/RTCP/RTP streaming media protocols and can be
played back by any compliant media player. This includes Quicktime, VLC, and MPlayer.
Others, such as Microsoft Media Player and RealPlayer use their own standards and cannot be
used.
Any player that provides cache control, such as VLC, is good because delay can be minimised.
(To minimise the delay in VLC, go to Settings > Preferences > Input / Codecs > Demuxers >
RTP/RTSP. Tick the Advanced Options, and change the Caching value to 100. Anything less
than this and the player may have problems playing data continuously).
What are the monitor stream URLs?
The URLs to use for listening to the audio monitor streams are:
rtsp://<ip_address>/stream1, rtsp://<ip_address>/stream2, rtsp://<ip_address>/stream3, and
rtsp://<ip_address>/stream4, where ip_address is the IP address of the frame.
What is the recommended network capacity?
Network capacity should be sufficient to carry the intended load. This will be the sum of level and
alarm data together with any streamed audio monitoring data.
The alarm and level data bandwidth required for every monitoring application is up to 370kbps.
The configuration application needs alarm data at 85kbps for logging and every stereo pair
streamed at full bandwidth adds 1.6Mbps.
So, if there are four active monitoring stations and four full-bandwidth audio monitoring streams
the required minimum bandwidth on the network will be nearly 8Mbps.
Lower bit rates can be achieved with lower quality audio steams and/or less alarm or data
information. See the Network Requirements section in the Introduction chapter.
Note: Any routers on the subnet that the frame is connected to must allow multicasting packets to
pass.
