WheatNet-IP BLADE 3
/ June 2018
page A – 113
A P P E N D I C E S
WheatNet‑IP is compatible with and can successfully stream to and from AES67
devices made by other manufacturers. WheatNet‑IP supports two AES67 packet timings
(more on this later), 1ms and 1/4ms.
First a brief overview.
WheatNet‑IP and most other audio‑over‑IP technologies
(AES67, Livewire, Ravenna, Dante, etc) are based on using common IP protocols for
identifying, parsing, transmitting, and routing digital information over an IP network. This
is no coincidence because all of these AoIP technologies depend on using standard off
the shelf network switches to move packets around the network. We must use protocols
these switches understand if they are to be useful for this.
We speak of “packets” when talking about AoIP because that is how IP networks
work. Any information that is transmitted on an IP network whether its a print job,
email, a browser session, or AoIP is first broken down into discrete digital pieces, each
representing a very small part of the entire “message”. These discrete pieces of digital
information are put together in a specific order with standardized blocks of identification
information (specified by the IP protocol); the assembly of identification and digital
information is then called a “packet” and any IP network device knows how to transmit
and receive these “packets”.
Thus any content of any kind sent over an IP network is broken down into individual
fragments sent one piece at a time and reassembled by the receiving device into useful
information. As long as the sending device, network switches, and receiving device all
use the same rules for this process it all works. These “rules” are what is referred to as
the “IP Protocol”.
It is very important to understand this point: network switches have no special functions
or structure that is made for routing audio. To the switches, packets are much the same
whether they are AoIP, video, email, or a print job. It is the data within the packets that
is unique.
Wheatstone, in the process of developing WNIP, has taken audio that is input into a
Blade, digitized it into digital pieces and inserted these digital pieces as the payload into
standardized packets that use these IP protocols.
So have the other vendors of AoIP systems. So what makes them different from each
other?
As far as sending and receiving IP audio streams, not much at all. Yes there are
huge differences relating to control and discovery and special features like mixing and
processing, but for the actual stream itself very little, mostly having to do with the spe‑
cifics of the payload within the packets themselves.
The Audio Engineering Society, recognizing this fact and wanting to create a standard
that would allow different AoIP devices to stream with each other came up with the
AES67 standard, which describes the IP protocols to be used to identify and route the
packets and also describes some standard ways to put together the digital pieces of audio
information in the packet payload.
WheatNet-IP and AES67
Summary of Contents for WheatNet-IP BLADE3
Page 2: ...Technical Manual Wheatstone Corporation Jan 2016 Audio Over IP Network WheatNet IP BLADE3 ...
Page 16: ...Quick Start 12 WheatNet IP BLADE 3 Jan 2016 Figure 4 ...
Page 290: ...page A 61 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Click Next Click Install ...
Page 338: ...page A 109 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S ...
Page 366: ...WheatNet IP BLADE 3 June 2018 page A 137 A P P E N D I C E S ...