The Score Magazine - Archive August 2015 issue! | Page 39

ADIT YA MODI
In this signal diagram of a RAVENNA
network we are showing an incredibly
useful feature of the Horus interface.
Each 8 channels of Input or Output
can be shared between a Number of
DAW’s, OR dedicated to a specific one,
allowing for professional quality I/O
to exist in each dubbing suite, even
though it is all being managed by a
central piece of equipment.
Why RAVENNA?
RAVENNA is an IP-based solution. As such it is
based on protocol levels on or above layer 3 of the OSI
reference model. All protocols and mechanisms used
within RAVENNA are based on widely deployed and
established standards:
• Time synchronization is maintained via PTPv2
(IEEE1588-2008).
• Streaming is based on the well-established RTP
/ RTCP protocols with payload formats defined
by various RFCs (i.e. RFC 3550/3551 et al).
• Both unicast and multicast are supported on a
per-stream basis.
•
Stream management and connection
achieved through SDP or RTSP protocol.
is
RAVENNA capabilities by contributing valuable core functionality
or adding application-specific software modules.
• QoS is based on DiffServ mechanism
• Device configuration and discovery is executed through the use
of DHCP / DN