|
Frequently Asked Questions About
IP-Audio Networks
With more than 1,500 installed studios
(and more in the works), there’s a lot of talk about Axia these
days — a lot of it from our competitors!
You know how it goes... when there's
something new on the scene that challenges the old order, there
is a lot of labored huffing and puffing as some people dependent
on the old way get desperate to hold back the advancing tide.
Telos' founder, Steve Church, said it 20 years ago in the Telos
10 manual: The first reaction to a fresh idea from the guys who
are threatened is some variation of “it won't work.” The next
phases are grudging acceptance in the face of the evidence, and
finally, copying the innovation as they see it succeed in the
marketplace. Clearly, Axia is now in the third phase, but there
are still some quite creative variations on “it won't work”
being thrown around. We thought you’d appreciate some straight
talk to clear the air about some of the things being tossed
around.
General Topics:
-
“I’ve been told that with Axia, latency
increases whenever you add inputs.”
-
“The other guys say Axia
consoles don’t have all the features they have.”
-
“Your competitors say you have to
replace Ethernet switches every 3 – 4 years.”
-
“I’ve heard switch standards are
pushed by Microsoft and the PC industry.”
-
“They say Axia networks only
work with one switch.”
-
“Your competition says that you have to
be an IT expert to run an Axia system.”
-
“What about network collisions? Isn't
Ethernet going to drop audio packets?”
-
“How do I know that Audio over IP
will be reliable? It's new, unproven technology.”
-
“What about Program Associated Data? Is your
system compatible?”
-
“Does your system route logic with
audio, too?”
-
“I wouldn’t use IP-Audio,
because I don’t want compressed audio in my studios.”
-
“If IP-Audio is uncompressed, I guess I can't
use it for STL, because that's always compressed.”
-
“What is the best audio format
to use with Axia systems?”
-
“Axia looks interesting, but I'll
wait until you've got some stuff in the field.”
-
“Are those customers happy?”
-
“I wouldn’t buy Axia consoles; I
want modular boards.”
-
“What happens if I need to replace
an on/off switch? Do I have to send the module back to the
factory?”
-
“What does Telos know about
console design, anyway?”
-
“I've heard your consoles are good at
mix-minus. What's different about the way you do it?”
-
“How many mix-minuses can your
consoles have?”
-
“I just need a router — I
don't need consoles.”
-
“A friend in the PA business told me
about Cobranet. That's something like Livewire, right?”
-
"Where does Axia fit into the
Open Systems Interconnection (OSI) Reference Model compared
to Cobranet and EtherSound?"
-
“I've heard that Axia costs
half as much as the other guys. What did you leave out?”
-
“Those other guys say they’re just
the same as you. After all, you all do audio over CAT-5.”
-
“We have an AM station, and those guys say
their system can do mono streams, and yours can't.”
-
“One of your competitors talks about
'islands of reliability.' They say they're more reliable
than you.”
-
“If my favorite delivery system
isn’t on your list of partners, can I still use my system
with Axia?”
-
“Another company says their system is
better than Axia since they're more efficient with
bandwidth.”
-
“I’ve heard that I have to
use CAT-6 to connect everything. That could get pricey.”
-
“What happens if someone accidentally
unplugs a cable? What then?”
-
“I’ve heard that there's a PC inside
your nodes. Is this true? I don't want to trust all my audio to a PC.”
-
“Your competitors say that your networks
can catch viruses. Is this true?”
-
“Do Axia networks have
any single points of failure?”
-
“I've been hearing about IPv6 a lot. Will
this affect how Axia networks operate?”
-
“Is Axia more expensive to install
than traditional routing systems?”
-
“Do I need your help to install
an Axia system?”
-
"One of your competitors says Axia
gear isn’t reliable, because you’re part of Telos, and Telos
is known for power-supply problems."
-
"The other guys say that their gear
doesn’t require you to configure Ethernet switches. They say
their products are just 'plug and play.'"
-
"OK, but they also say their
node-like devices don’t need to be configured when you replace them,
like Axia Nodes do."
-
"Your competitors say their
version of Audio Nodes are better because they can handle mixed signals."
-
"Your competition says they’ve got a
track record of many years’ building consoles. Axia doesn’t
have that experience."
-
"Why can't I just use my favorite
switch with Axia?"
-
"Is it OK to mix brands of
switches within the same Axia network?"
PowerStation Topics:
“I’ve been told
that with Axia, latency increases whenever you add inputs. The
more sources you add, the higher the delay.”
No, Livewire's latency remains
fixed at the same low value regardless of the channel count.
You can run a system with a thousand channels and the
latency will be the same as for a single stereo stream.
Indeed, the delay is so consistent that channel-to-channel
phase shift is less than 1/4 sample.
The total latency of an analog
input to analog output using the Axia Livestream format is
about 2.75 milliseconds:
To put this into perspective,
the analog input to output latency on a self-contained BMX-Digital
is about 1.75 milliseconds.
The backplane of a modern
Ethernet switch can handle full duplex traffic on all ports
simultaneously without any packet loss. And since Axia
component links are designed so that they never exceed any
port's capacity, we never exceed the switch capacity. The
way we prevent port overload is simple: we “own” each port.
Every Axia audio node is plugged into an unshared 100Base-T
port on the switch. Even when all of a node’s inputs and
outputs are active, we are still well under the bandwidth of
the ports, and the switch is completely under control.
Because the switch has the backplane capacity to handle all
ports fully loaded, the system performance doesn’t change
from one to thousands of audio channels.
Let's explore the issue of
switch capacity a little further. We know how much capacity
is required per port for each node, and we know that a node
will never produce or consume more than 16 stereo streams
total. But what about the mix engine? To support a large
console with a lot of buses, inputs, mix-minus outputs,
etc., you may have 40 or 50 simultaneous signals (or more).
Because this could exceed the port capacity of a 100Base-T
port, the mix engine is connected via Gigabit Ethernet only.
Using Gigabit for the engine, we could support a 200 fader
console with 200 outputs and still have room to spare! Each
console's mixing engine gets its own Gigabit port.
“The
other guys say Axia consoles don’t have all the features they
have. Like voice processing.”
Sure we do. Voice dynamics is a
standard feature on all Axia consoles — and it was developed
by Omnia's Frank Foti, who knows a little something about
audio dynamics processing. Other standard features include
per-source EQ and panning, headphone EQ and a one-touch
off-air recording function, all of which can be set and
saved to instantly recall each jock’s favorite settings. The
Element console features four stereo program buses, and four
stereo aux sends with two stereo aux returns for off-air
production.
Element also does things that no
other console can do. For example, you can connect the
latest Telos broadcast phone systems with one RJ-45 — all
audio I/O for four hybrids plus line-selection control from
a tightly integrated drop-in panel enter the system using
one skinny Ethernet cable. It has optional dynamics
processing on the headphones. It has a one-touch record-mode
button for recording phone bits. It has a powerful system
that lets you set, save and recall events and personal
preferences for each jock. A clock that can be synched to
NTP network time. A motor fader option. Add our Pathfinder
routing control package, and you get extensive
user-programmable event handling, built-in silence-sense
that automatically switches to a backup audio feed,
interactive on-screen virtual control panels for studio PCs,
and much more.
“One of
your competitors says that you'll have to replace the Ethernet
switches every 3 – 4 years. And when you do, you'll have to load
all new software to work with it (if you can even make your
stuff work with it).”
Ethernet is a standard, IEEE
802.3. Axia gear works with any switch or router that
supports the standard. We do generally need higher-end
switches because Livewire uses advanced multicast and
Quality-of-Service features that are not included in low-end
switches.
You might want to upgrade to a
larger or more powerful switch for some reason in the
future; for example, if you were to add more studios to a
cluster. Or maybe you would like to change from copper to
fiber for some kind of remote uplink connection. Or you
might want to replace an older switch at some point. Thanks
to IEEE 802.3, the replacement switch would simply plug into
the network and function, with no software changes needed on
any equipment. But there is certainly no requirement to do
this at any particular time interval. Ethernet's open and
evolving nature gives you choices that closed systems don't.
That's an advantage.
“I’ve
heard that switch standards are pushed by Microsoft and the PC
industry, and they change all the time. Won't I have the risk of
my Axia equipment becoming obsolete?”
Not to belabor this point, but
Ethernet standards are supervised by the IEEE (Institute of
Electrical and Electronics Engineers), a non-profit group
that takes input from a quite large number of interested
parties. Ethernet switches are always getting faster and
having new features to make networks more capable, robust,
reliable and flexible. But these new features don’t obsolete
other equipment. Think about it: if you buy a new switch for
your computer network, do you have to throw out your old
PCs? Of course not.
“They also say that Axia networks only work with one switch, and
if they stop making that switch, I won't be able to expand or
modify my network.”
Axia has qualified several
different switches from well-known manufacturers such as
Cisco and Hewlett-Packard to suit the
needs of different-sized installations. We are not tied to a
particular switch or manufacturer. Indeed, as time goes on,
we find more switches that include the features we need.
Ethernet has been around for
more than 30 years. It is supported by hundreds of vendors.
It continues to evolve to be faster and more powerful, to
use different connection media, etc., but backward
compatibility is always maintained.
“Your
competition says that you have to be an IT expert to run an Axia
system.”
We’re engineers, and we like to
talk tech. Sometimes, we talk about the tech more than we
need to! But in this respect, an IP-Audio network is like a
car: you don't have to understand how the engine works in
order to drive it. Just connect two pieces of gear together
with CAT-5e and they will talk to each other — like plugging
a mic into a mixer. The Livewire protocol takes care of
routing the audio without any need for intervention from
you. And the equipment interface is all web-based with GUI
control. It works intuitively, and you don't have to know
anything about the tech inside to make it work.
That having been said, another
of the advantages of Ethernet and IP is that bookshop
shelves are full of well-written books that can explain any
aspect of standards-based networking at any level of detail
you might want.
“What about
network collisions? Isn't Ethernet going to drop audio packets?”
Years ago, Ethernet used a
shared coax cable. In rare cases two devices would grab the
bus simultaneously. When this happened, one would back-off
and send a few milliseconds later. These were the famous
collisions. But With today's switched Ethernet, there is no
shared bus – each device completely owns its own full-duplex
link. There are never collisions or lost packets as a result
of network congestion; it’s physically impossible.
“How do I
know that Audio over IP will be reliable? It's new, unproven
technology.”
Axia uses the same technology
that underlies VoIP telephony. Did you know that nearly 75% of the Fortune 100 companies now use VoIP? Or that VoIP PBX
systems now outsell the old kind by a wide margin? With
these systems, telephones plug into a standard Ethernet/IP
network. Contrast this with traditional PBX phone gear —
proprietary devices which required you to purchase phone
sets and parts exclusively from the company that built the
mainframe. You were locked into a single vendor, because the
technology that ran the mainframe was owned by the company
that made the gear. (Kind of like the TDM router companies.)
IP is now accepted as a universal
transport for almost any kind of signal. You see it in
television studios, business teleconferencing, government
communications, banking, etc. And it's hardly unproven,
especially for applications specific to radio studio
infrastructure. As of 2009, over 1,500 studios around the
world - many in mission-critical, 24/7 broadcast
applications in major markets like New York City, Chicago,
Paris, Rome and Bangkok - have been built using Axia
IP-Audio infrastructure.
“What about Program
Associated Data? Is your system compatible?”
Yes. Devices that generate PAD
plug into the Axia network; the information they supply is
sent along with its associated audio, and any devices that
need it can also plug into the network and retrieve it. This
means that you can send audio and PAD together, without
incurring extra costs for separate audio and data networks.
“Does
your system route logic with audio, too?”
Of course. IP is great for data,
no? Logic commands from external devices like CD players,
DAT machines, etc., enter the network using GPIO Nodes. The
logic data is then “bound” to the audio stream, and is
routed with it to whatever console the source is loaded on.
Devices equipped with Livewire
interfaces (like the latest Telos Zephyrs and phone hybrids,
Omnia audio processors and IDC satellite receivers, for
example) supply audio and control logic directly from the
device to the Ethernet switch over a single CAT-5e
connection, further simplifying in-studio wiring and making
Livewire’s audio+logic routing even more convenient.
“I
wouldn’t use IP-Audio, because I don’t want compressed audio in
my studios.”
Livewire is not compressed. Axia
networks carry linear, 48 kHz, 24-bit studio-grade audio,
and there are switches that have enough bandwidth to carry
10,000+ channels of uncompressed, real-time stereo audio
simultaneously.
“If IP-Audio is
uncompressed, I guess I can't use it for STL, because that's
always compressed.”
Sure you can, using Ethernet
radios from companies like Motorola, Exalt, Dragonwave and
others. These line-of-sight radios (and
others like them) are capable of data rates of 45 Mbps or
more —
enough for several channels of uncompressed audio and data in each
direction. On the other hand, if you want a compressed link,
the latest generation Telos Zephyr can do that for you. It
takes Livewire audio in, generates a compressed IP stream,
then delivers it back again to another Livewire network or
to traditional analog or AES devices.
“So
what is the best audio format to use with Axia systems?”
Axia networks don't care what
format your music files are stored in. During the playout
process, your playout software will uncompress any
compressed-format files (MP3, MP2, apt-x, etc.) and present
them to the Axia IP-Audio Driver. What this means is that
all audio that moves within the Axia system is the same -
uncompressed.
So, the question really becomes,
what audio format is best for your storage needs, your
convenience, and the desired audio quality you want to have
on-air. Our feeling, since large capacity hard drives are
very cheap nowadays, is that it's better to store all audio
in a linear fashion, as the resultant audio quality will be
higher, especially after any audio processing.
“I know
Axia is a new division of Telos. It looks interesting, but I'll
wait until you've got some stuff in the field.”
Actually, as of this writing
(July, 2009), there are already 1,500 installed studios
worth of Axia equipment. The adoption curve is turning
sharply upward, so by the time you read this, there are
likely to be many more. There are many other people using
Axia gear for non-studio applications like fiber or
microwave links. Some have built routing switchers.
“Are
those customers happy?”
Very! Axia systems are faster to
install than traditional routing setups, work reliably and
are easy to reconfigure. Why not talk to the people actually
using it and see what they have to say? We’ll be happy to
provide you with a list of references upon request.
“I
wouldn’t buy Axia consoles; I want modular boards.”
Our Element console is modular.
Element modules contain groups of four faders, which are
easily accessed for service by removing just two screws and
a cable or two. They’re hot-swappable, too – since all the
mixing is done away from the board, in the StudioEngine, you
can even take out a module while it’s on the air without
affecting the audio in any way. Indeed, you can hot-swap the
entire console without disrupting audio.
“What
happens if I need to replace an on/off switch? Do I have to send
the whole module back to the factory?”
Element components are made to stand up to
even the most heavy-handed jocks. For instance, we use
switches designed for avionics, and rated for long life. We
even designed our our own buttons and protective bezels
specifically to prevent switch element damage from abuse.
Of course, we realize that all equipment
requires maintenance eventually, so Element modules are made
to be serviced easily in the field. On/off switches, for
instance, can be individually replaced, as can individual
faders. And since actual audio mixing is done outside the
console, in the Axia StudioEngine, you can actually pull a
module while it's on-air without disrupting any audio
streams controlled by its faders.
“What
does Telos know about console design, anyway?”
Quite a lot, actually. Axia
President Mike Dosch, the man who designed PR&E’s Radiomixer
console, also designed Element. We’ve got the biggest R&D
department in the broadcast industry, and it’s filled with
folks who’ve spent years around consoles, figuring out what
works and what doesn’t. We have over a dozen ex-broadcasters
on our staff, by the way. It's fair to say we know our way
around faders and buses.
“I've heard
that your consoles are good at mix-minus. What's so different
about the way you do it?”
We’re part of Telos, so as you
might imagine, we’ve studied mix-minus for a long time. And
we’ve always been amazed at how complicated and confusing it
is to set up correctly. With today’s radio shows relying
heavily on phones and remotes, something needed to be done.
Our Element consoles generate
mix-minuses automatically, on-the-fly, without any
intervention needed from talent. The way it works is simple:
when a caller is on the air, he hears the main Program feed,
minus himself. When off the air, he hears a special
“off-line” phone mix that can contain audio sources:
pre-fader audio from the host mic, other phone callers, etc.
Best of all, mix-minus settings
for audio sources such as phone hybrids and remote codecs
are assigned to the source itself, not the console fader —
so when a source that needs a mix-minus is loaded onto any
fader, on any console, the mix-minus settings are
automatically loaded too.
At the physical level, mix-minus is easy, too. Livewire
carries audio in both directions, so one RJ-45 covers
everything.
“How
many mix-minuses can your consoles have?”
One for every fader! There’s a
lot of processing power in our StudioEngines, enough that
Axia consoles can provide automatic mix-minuses
simultaneously for every fader on the console. You’ll
probably never need to have 40 mix-minuses running at once,
but isn’t it nice to know that you could?
“I
just need a router — I don't need consoles.”
No problem. Axia networks can
work with your existing consoles. Just plug the inputs and
outputs into our audio nodes — and use Router Selector nodes
to control X-Y switching functions. For sophisticated
systems, use our Pathfinder router control software package.
You can do everything any other router can do – and much
more.
“A friend in
the PA business told me about Cobranet. That's something like
Livewire, right?”
Cobranet was not developed for
broadcast use, which demands very low latency in the
DJ-to-headphones path. Cobranet is much higher latency than
Livewire, making trouble for live listening. It also will
not allow non-audio traffic on the links — an important
consideration for broadcasters who wish to have machine
control, PAD, RDS, etc. integrated within their facility.
There are also limits to the
number of audio sources Cobranet can handle. Cobranet groups
audio channels into “bundles” (which are packets), 8 mono
audio channels per bundle. According to the Cobranet
website, there is a systemwide network limit of 8 bundles. 8
bundles x 8 channels = a 64-channel limit, whereas IP-Audio
networks using the Livewire protocol can handle upwards of
10,000 stereo streams.
Cobranet is not IP Audio, since
it works only at the Ethernet level. Axia networks use
state-of-the-art IGMP (Internet Group Management Protocol)
to manage the transmission of Multicast audio streams, which
allow multiple subscribers to receive and use audio from the
same origination point. IGMP also makes it possible to
dynamically add and subtract subscribers from a stream.
Cobranet does not use IGMP; users must map out individual
point-to¬-point connections with Unicast IP addressing. If
more than one destination wants to listen to a given source,
the source has to send multiple copies of the stream, which
then hits Cobranet’s limit of 8 streams coming from any
given source. You could choose to send audio as Multicast IP
data to all points on the network, but with 8 bundles of
channels active, all 100Base-T links everywhere in the
system would be at full capacity. These limitations make
Cobranet unsuitable for broadcast audio networks.
"I
read an article recently about broadcast audio networks and how
they relate to the Open Systems Interconnection (OSI) Reference
Model. Where does Axia fit in that model, and how does it
compare to Cobranet and EtherSound?"
You might have read Brent
Harshbarger's article in ProAV Magazine (archived
here). As the article says, the OSI model is a
seven-layer framework that defines network functions.
Axia operates on Levels 1 through 5 of the
OSI model. The IP Network Layer provides routing
capabilities. The UDP Layer provides transport service using
port numbers. The RTP Layer provides additional information
about streams, helping to identify media format and look for
dropped or duplicate packets, as well as other useful
functionality using the RTP standard for best compatibility
with other media streaming solutions. By comparison,
EtherSound and Cobranet function on only the first two
network layers.
“I've heard that Axia costs half as much as the other guys. What
did you leave out?”
Nothing. Our cost savings compared to
traditional routers are achieved by using standard,
off-the-shelf switching hardware rather than custom-built
solutions. It’s a lot less expensive to use a mass-produced
Ethernet switch available from any network vendor than it is
to construct a customized cross-point routing switcher, with
its cards, frame and peripherals. This is the same principle
that has driven almost all stations to use PCs for audio
playout and editing – they are a lot cheaper and more
powerful than any broadcast-industry specific machine could
be.
Another way Axia saves money lies in the way
PC audio is handled. With a traditional router, PC audio
must be brought in through a router input card or console
module; bringing multiple channels of audio into the system
in this manner (from workstations or digital delivery
systems) can significantly increase the overall cost of the
system.
Instead, we wrote an IP-Audio Driver for
Windows PCs that looks just like a sound card to the OS, but
streams audio in and out of the computer’s network card
instead. Or, if you need the realtime MPEG compression or
time compression features of a high-end sound card, our
partner Audioscience makes an audio card with a Livewire
output that plugs directly into the Axia network. Either of
these approaches eliminates the cost of the I/O needed to
get audio into the switching network. So Axia clients
usually realize several thousand dollars worth of savings
over and above the cost of the sound cards themselves.
“Those
other guys say they’re just the same as you. After all, you all
do audio over CAT-5.”
We all use Category cable, but
that’s where the similarity stops. Axia IP-Audio networks
are standards-based, adhering to Internationally-recognized
Ethernet standards. Using a standard is much different than
using a proprietary protocol with CAT-5. This standard makes
it possible for any broadcast equipment or software vendor
to interface directly with Axia networks.
Here’s a partial list of
companies that
make products using the Livewire standard to connect
directly with IP-Audio networks. (Ask the other guys what
products connect to them directly, without using a
proprietary interface or breakout box.)
“We have an AM
station, and those guys say their system can do mono streams,
and yours can't.”
Axia has monaural compatibility
as well. You can feed a mono stream into an Audio Node and
then route it as dual-stereo. This is built-in to all of our
Analog and AES/EBU Nodes.
“One of your
competitors talks about 'islands of reliability.' They claim
that a networkable console with built-in inputs and outputs is
more reliable than an Axia console.”
They can claim anything they
like, but the fact is that Axia systems are just as reliable
-- if not more so -- than any console with built in I/O.
This is because each Axia studio has its own edge switch,
and each edge switch (with all its studio peripherals
connected) is its own self-contained audio network. This
includes all of the inputs and outputs to and from
that studio. In the unlikely event that everything but one
studio failed, that studio could still be operated
independently of the rest of the network.
“If my
favorite delivery system isn’t on your list of partners, can I
still use my system with Axia?”
Yes, the same way you do it now:
just plug the delivery system’s outputs into our inputs, and
send the contact closures into our GPIO nodes. (Then ask
your delivery system provider when they’re going to become
an Axia partner!)
“Another
router/switcher company says their system is better than the
Axia standard, since they're more efficient with their
bandwidth.”
Why is this at all relevant?
Sure, Ethernet/IP packets have overhead from the required
headers. But the capacity of the Ethernet links and switches
is plenty high enough to handle all that is needed. So this
makes no difference in practical use and is never seen by
the user.
“I’ve heard that I have to use CAT-6 to connect everything. That
could get pricey.”
CAT-6 is used for only two
heavy-traffic network segments: connecting Axia mixing
engines to Ethernet switches, and connecting switches to
each other. All other equipment is connected with common,
inexpensive CAT-5e cable.
“What
happens if someone accidentally unplugs a cable? What then?”
Axia audio nodes “advertise” the
presence of their audio streams to the entire Livewire
network. So if someone unplugs a node, the sources attached
to it will be offline. But all you have to do is plug that
node back in, and the node will “advertise” that the audio
streams are available again. Within 10 seconds, all
destinations that need those sources will be back up and
running.
Additionally, among the many
features of Pathfinder is a silence detect function that can
be programmed to switch to another feed should one stop
working for any reason.
“I’ve heard
that there's a PC inside your nodes. Is this true? I don't want to trust my audio to a PC.”
No, Axia audio nodes do not have a PC inside
them. They do have webservers, which allow you to examine
and configure them from any networked computer with a Web
browser - a feature found in every well-designed networked
device.
Our first generation of DSP engine used an
Intel industrial motherboard running a Pentium-4 processor.
We use a mix of Intel and TI and Motorola processors in our
various products. Some people think that if there's "Intel
inside" it must be a PC, but that is just as silly as
imagining that every product with a Motorola processor
inside is a mobile phone.
We do make use of PC's on our system to run
certain applications, such as complex routing configuration
and control, backup/restore/diagnostics apps, etc. These are
programs that are rich in information, and benefit from
being run from a PC with a big monitor. You really wouldn't
want to attempt such functions with a few buttons and a
microscreen.
“Your competitors
say that your networks can catch viruses. Is this true?”
There are no general purpose
operating systems in Axia devices, so the answer is “No.”
You can keep computers attached to your Livewire audio
network safe by keeping it isolated from data networks.
“Do Axia networks have any
single points of failure? Is there a central ‘brain’ I can lose
that will take the system down?”
Axia networks are distributed,
with no central box. Ethernet networks can be designed any
number of ways, including those that are fully-redundant and
self-healing. Normally, our clients build larger facilities
with “edge switches” serving each studio, connected to a
redundant core. Each studio is able to operate stand-alone.
“I've been hearing
about IPv6 a lot. Will this affect how Axia networks operate?”
Internet Protocol version 4
(IPv4) is the IP addressing structure that powers the
Internet. The Internet Engineering Task Force (IETF) has
designated IPv6 as the successor to version 4, due to its
larger address space, which offers more flexibility in
routing traffic and allocating addresses, providing hundreds
of billions more possible IP addresses than IPv4.
There are no compatibility
issues between products using IPv4 or IPv6 addressing. Both
addressing schemes can co-exist on the same network and
interoperate smoothly. Axia systems employ Multicast
streaming for audio routing. This is fully developed within
IPv4, but it it not widely used under IPv6. For this reason,
Axia will continue to use IPv4 until such time as IPv6 will
provide the same consistent performance. We monitor the
technology standards very closely and we plan to move to
IPv6 when Multicasting is widely implemented.
There is one case in which IPv4
could be a limitation: If you plan to have several hundred
billion devices on your network. If you have plans to build
such a large network, call us. We'll gladly implement IPv6
for you right away!
“Is Axia
more expensive to install than traditional routing systems?”
In fact, Axia costs lots less to
install, because everything in an Axia network connects
using off-the-shelf Ethernet cables, which carry multiple
uncompressed channels of stereo audio. 100Base-T links can
carry 25 audio channels simultaneously; Gigabit links can
handle 250. The money saved just from the elimination of
expensive multi-pair cable for studio interconnects can be
significant.
Even our audio connectors are
designed to promote fast, inexpensive installation. All of
our Audio Nodes use the Radio Systems StudioHub+ RJ-45
standard for I/O jacks (except for mics, which use standard
XLR connectors); a huge variety of adapters are available
from Radio Systems for all kinds of devices. Tally up the
savings in labor realized from not having to purchase and
hand-solder hundreds of XLR and RCA connectors, and the
money saved becomes even more impressive.
There’s considerable time saved
during Axia installations as well. Due to the reduction of
cabling and the quick connection of devices, our clients
tell us that installation of Axia networks goes 30% to 50%
quicker than wiring studios the traditional way.
“Most
companies recommend that I bring them on-site to help install
and configure their systems. Do I need your help to install an
Axia system?”
With those other guys, you'd
better hire their systems engineers. With us, it's much
easier! If you know how to use
a Web browser and plug a telephone into the wall, you’ve got
all the skills needed to install and configure your new Axia
network. And Axia Technical Support is there to help if you
need it, too.
If you still decide you’d like
on-site installation services, we’ll be happy to talk with you about it.
"One of your
competitors says Axia gear isn’t reliable, because you’re part
of Telos, and Telos is known for power-supply problems."
It’s true that some older Telos phone gear
had power supply problems. We made a mistake; the parts
Telos R&D sourced weren’t as robust as their maker said they
were. Of course, Telos took care of our clients and replaced
all the faulty parts at our cost. But Axia R&D engineers are
not the same as Telos’ R&D group, and they learned from
previous mistakes.
Axia buys state-of-the-art power supplies
from a company that does nothing but design and build power
supplies. And Axia gear is extremely reliable. In the last 5
years, Axia has shipped thousands of consoles, audio nodes,
studio engines and routing control hardware around the
globe. During that time, there have been less than a dozen
power supply failures.
Here’s an example: the power supply in our
new PowerStation is made by SynQor, a company who makes OEM
power supplies for Fortune 500 companies. It’s part of a
family of power supplies designed for high-uptime telecom
apps; designed to withstand all-weather installation at the
base of cell towers in remote locations.
Some companies would like you to believe
that only they can guarantee reliable power supplies,
because they build their own and therefore control the
quality. But we think trusting hardened, industrial-grade
power supplies from a major manufacturer is nowhere near as
scary as trusting someone else’s home-brew design.
"The other guys say
that their gear doesn’t require you to configure Ethernet
switches. They say their products are just 'plug and play.'
"
You should examine that claim closely. All
Ethernet switches, even those from Cisco and HP, must be
configured to ensure that IP-Audio signals (which are made
up of faster, smaller packets than standard network data
packets) receive data priority and are transmitted properly
to air. Axia makes switch configuration as painless as
possible. If you like, we'll configure your network's switch
for you, free of charge. If you prefer to do it yourself,
clear, concise "how to" documents are posted at
AxiaAudio.com/manuals/
.
"OK, but they also
say their node-like devices don’t need to be configured when you replace
them, like Axia Nodes do."
Not exactly true; we both do the same thing,
just differently. Both our equipment and theirs needs to be
configured, initially, by the use of a network connection
and a browser.
With their system, each device is given a
name – “BOB”, for instance. That name is independent of the
device's IP address, but all the configuration info is tied
to its name. That information is then distributed around the
network and stored in each of the other devices. When you
need to replace a failed unit with a new one, you name it
“BOB” and it reclaims the configuration info previously
stored for “BOB” from the other devices on the network.
That’s pretty easy.
Axia is pretty easy, too. We have a program
for your PC that, with one button, archives the settings for
every Axia device — a single file with all of your settings.
If you have to replace a Node, you can quickly restore its
settings with one mouse click using iProbe.
Our competitors argue their system doesn’t
need a PC to replace a failed "node". But what’s the big
deal about connecting a PC? After all, it’s a network. A
bigger question is: why are they so concerned about their
gear failing?
"Your competitors say
their versions of Audio Nodes are better because they can handle mixed signals."
That’s a good idea! Axia’s new console
engine, PowerStation, accepts mixed signal types, too. And
with PowerStation, it's not just a mix of audio — it's a mix
of inputs, outputs, console control, GPIO logic, everything;
think of PowerStation as a Super-node. After all, your
console is the logical place to have a mix, not your
outboard nodes.
"Your competition says
they’ve got a track record of many years’ building consoles.
Axia doesn’t have that experience."
True; Axia is only 6 years old with 1,500
consoles so far. That’s actually quite a lot of consoles…
more than Klotz, more than Logitek, more than SAS, and more
than the post-PR&E Harris. But just because our company is
young doesn’t mean we have less console experience. In fact,
the engineer we recruited to run our console division has
been designing consoles longer than Wheatstone has. He
designed broadcast consoles for PR&E before coming to Axia.
"Why can't I just use my favorite switch with
Axia?"
People ask us this question every so often. We have
standardized on Cisco and HP because their reliability, feature
sets and performance are the best we've found. They also offer a wide
range of switches at all price points to meet individual users'
needs.
How come other manufacturers' switches don't measure up? This is mostly due to individual manufacturers' differing
implementation of the same "standards". For file transfers and
e-mail, these differences are immaterial. But for VoIP and, most
especially, IP-Audio, these implementations become more
important. It's quite possible for a given switch to "work" with just a few
nodes attached, but when a more robust test of Axia's
capabilities is applied, that same switch can fail.
For example, we found a nice, inexpensive switch
from a well-known manufacturer which, on paper, met all specs
and worked with small systems in the lab. However, it turned out
to not actually meet its own published specs when deployed for rigorous service
in a large Livewire system.
For this reason, we recommend and qualify only
selected Cisco and HP switches
for Axia clients.
"Is it OK to mix brands of switches within the same
Axia network?"
For small systems with simple networking structures,
yes. But if you plan on expanding your network or using
more sophisticated routing functions - such as
implementing multiple core switches, or redundant links
between edge and core switches - we recommend choosing
switches from a single manufacturer to ensure seamless
interworking.
Questions
about PowerStation
"Why should I choose
PowerStation instead of assembling a studio from discrete
components?"
PowerStation makes studio building easier
and faster. With PowerStation you don’t have to configure
lots of separate components; to get a studio up and running
quickly you simply connect your audio sources, name them
using the Web interface, and start feeding audio. There’s
not a lot of configuration to do because all the
functionality of those separate components are contained in
a single box, and they all talk to each other already.
"You say that I
can build 'stand-alone studios' with PowerStation. What do you
mean? I thought Axia gear was all networked."
PowerStation was designed after listening
carefully to clients who asked for an easy way to set up one
or two independent studios. PowerStation combines audio I/O,
machine logic, mix engine, console CPU, Ethernet switch and
power supply (with optional power redundancy) into one
fan-free box. This dramatically cuts setup time, since
there’s only one piece of equipment to configure.
Consequently, you can use PowerStation to
quickly build a self-contained studio that operates all by
itself. Of course, if you want to connect your PowerStation
studio to an IP-Audio network, you can, with one easy
Ethernet connection.
"How large a console
can I use with PowerStation?"
PowerStation supports Element consoles as
large as 40 faders or as small as 2 faders (and everything
in between) in either single-frame or split-frame
configurations.
"Do I need an
external core switch to connect PowerStation studios?"
PowerStation includes “simple networking”
capabilities; you can connect up to 4 PowerStation studios
together, daisy-chain style, using the network switch that’s
built in — with no need for an external switch to link them.
Copper Gigabit ports and SFP ports for fiber are both
provided.
If you want to network more than 4 studios
that are built with PowerStation, you’ll need a core switch.
"Some of your
competitors’ gear has built-in switches. But you said that the
Cisco and HP switches you specified were more powerful than any
switch they could design. Now, your gear has a built-in switch.
What gives?"
We did say that, and we stand by it: we were
comparing their TDM routers with Cisco switches. Certainly
you’ll agree that the Ethernet switching core Cisco provides
is more powerful than a TDM switching core.
Remember, switches located in the studio are
just edge switches. They are not highly complex, since they
primarily just provide access to local I/O. It’s the central
core switch that does the heavy lifting of intra-facility
signal routing.
We still think that Cisco and HP know more
about making Ethernet switches than anyone else. That’s why
we specify their equipment for Axia networks’ core switches.
But our clients asked us for a one-box solution for studio
I/O and switching, and we gave them what they asked for:
PowerStation.
And by the way, PowerStation’s edge switches
use the very same chipsets that Cisco switches do.
"How much I/O does
PowerStation MAIN have?"
PowerStation MAIN comes with 4 Analog
inputs, 2 AES/EBU inputs, 2 Mic inputs with switchable
Phantom power, 6 Analog outputs and 2 AES/EBU outputs. There
are also 4 GPIO ports and 14 Ethernet ports for connection
of Livewire-enabled audio devices.
Connecting a PowerStation AUX via Ethernet
doubles the audio and logic I/O, and adds redundant power
capabilities.
"Are you sure that’s
enough I/O for an on-air studio?"
Clients have been telling us that the
growing number of Livewire-ready devices are helping shrink
the need for conventional I/O. For instance, two dozen
Livewire partners are now making profanity delay units,
satellite receivers, high-end audio cards and content
delivery systems that integrate with Axia networks using an
Ethernet cable to transport all audio, logic and messaging.
To see a list of Axia partners, visit
www.AxiaAudio.com/partners/ .
"What if I need more
I/O than is built in to PowerStation?"
No problem; it’s easy to expand your I/O by
adding a PowerStation AUX to any PowerStation MAIN. Of
course, you can plug an Axia Audio Node into PowerStation’s
Ethernet switch, too. In fact, you can connect as many as 14
Livewire devices to any PowerStation MAIN. Even your playout
or production PCs (using the Livewire Audio Driver or an
AudioScience Livewire sound card) can plug into the Ethernet
ports on the back of each PowerStation MAIN.
"What’s the
difference between PowerStation MAIN and PowerStation AUX?"
PowerStation MAIN is the core of the studio.
It contains the Mixing Engine, console CPU, audio I/O, GPIO
logic ports, Ethernet switch and power supply for all these,
plus the console.
PowerStation AUX connects to the MAIN using
one CAT-5 cable and one power link. It instantly doubles
your audio and logic I/O, and adds automatic redundant
backup power too.
"Why the
redundant power? Are you afraid your power supplies will fail?"
Quite the contrary! Some folks prefer the
security of redundant console power supplies, so
PowerStation offers this. In fact, PowerStation’s redundant
power protects not just the console, but the audio inputs,
the Ethernet switch and the mix engine, further ensuring
your studio’s uptime. As far as we know, no other console
company provides this level of power backup.
Axia buys state-of-the-art power supplies
from a company who makes OEM power supplies for Fortune 500
companies. They’re part of a family of power supplies
designed for high-uptime telecom apps; designed to withstand
all-weather installation at the base of cell towers in
remote locations. We have the utmost confidence in these
high-end components, and you can, too.
"If the power
supply were to fail in one box, would it affect any systems in
the other, or is the backup truly redundant?"
The backup power is truly redundant, meaning
that not only is the console power supply redundant, but
power for the mixing engine, audio, logic and even the
Ethernet switch is redundant as well. In short, every
component in both the MAIN and AUX will continue operating
if one or the other power supply quits. The switchover is
seamless, too — it takes place automatically and does not
affect your audio. In the case of such event, a front-panel
alarm illuminates; clients using PathfinderPC can have an
e-mail notification sent as well.
"Why are those heat
sinks so big?"
PowerStation is completely silent and
fan-free! Those heat sinks provide convection cooling so you
can rack it with the rest of your studio gear. PowerStation
breathes so easily that the front-panel is cool to the
touch, and the perforated front panel ensures unobstructed
airflow without the need for rack spacers.
"Some of PowerStation’s
Ethernet ports have PoE. Why?"
Many new Ethernet devices use PoE (Power
over Ethernet) to eliminate wall-warts or ride-along power
supplies. PowerStation has PoE in anticipation of future
broadcast gear that will use PoE.
"We just outfitted 3
studios with previous Axia gear. Is that obsolete now?"
No way! PowerStation plugs right into
existing Axia networks, and other Axia gear connects to and
works seamlessly with PowerStation.
All Axia equipment uses standard switched
Ethernet for audio and logic transport. This guarantees that
our future products will always work perfectly with even the
earliest Axia equipment.
|