Approximate reading time: 7 Minutes

 ·  Source: Behringer

RME Digiface Dante Perspective

 ·  Source: RME

Rupert Neve Designs RMP-D8 8-channel Dante Mic Pre

Rupert Neve Designs RMP-D8 8-channel Dante Mic Pre  ·  Source: Rupert Neve Designs

MOTU Ultralite AVB

MOTU Ultralite AVB  ·  Source: MOTU

Behringer Wing Digital Mixer

Behringer's Wing DIgital Mixer  ·  Source: Behringer

Audio Networking is becoming an increasingly important part of live and studio setups. But what’s the difference between all the networking formats? Do you know your Dante from your AVB? And which networking format should you choose? Grab a coffee and let us guide you through the maze of audio networking protocols.

What is Audio Networking?

Up until a couple of decades ago, if you needed to send multiple channels of audio over long distances, you had few choices. Typically you’d be running audio over balanced line analogue cabling, using physical patch bays and distribution amplifiers. The analogue approach has some notable downsides though: cable cost, maintenance and limitations of cable length.

With the advent of digital audio it’s now possible to send multi-channel audio down a single Ethernet cable. You can even distribute those channels to multiple sources, format depending. Importantly, this means no more expensive, bulky multicore snakes, no loss of audio quality over distance and much more flexibility in routing.

Sounds great? Well, there are multiple audio networking formats and worse, they are not mutually compatible! So what are your choices and what should you be looking for when you buy your next digital mixing console? We thought it was about time we had a quick round-up of the most common audio networking formats. All have their own pros and cons but it’s important that you choose the format which suits your requirements… and budget!


If you’ve worked with or looked into network audio, it’s inevitable you’ll have come across Dante. Introduced around the mid-noughties, Dante has almost become the generic trade term for networked audio. Importantly, Dante is the only network system with which you could build a complete system from microphone to mixing console, to speaker system wholly on a single audio network.

Focusrite Red 8Line with Dante connector

Focusrite Red 8Line with Dante connector

You’ll find more pro audio gear offering Dante network support than any other audio networking format, either built-in or via accessory networking cards. Dante also runs over your existing Ethernet network as it uses IP packets for data transfer. The major downsides to Dante for you, the user, are cost and complexity. You’ll find Dante equipped hardware is expensive thanks to chipset licensing costs. Dante’s control software is also, how shall we put this… challenging to use! There are certified courses in Dante networking for example…


  • Runs over standard Ethernet network
  • Greatest support of any audio networking format
  • Best prospects for long-term support
  • The “Industry-Standard” for mid to high-end pro audio


  • Dante-equipped hardware is expensive due to licensing costs
  • Dante control software not easy to use with many stages of “certification” for those wishing to master the technology


Audio Video Bridging or AVB is another audio networking format you’re likely to have heard of. An open-source format under the designation of IEEE 1722, you may also have come across it branded as Milan in pro audio systems. AVB has many similarities with Dante in that it’s a way of sending network audio over an Ethernet network. Well, when we say Ethernet network, there are some caveats

The designers of AVB identified an issue with sending latency-sensitive information, such as audio and video, over Ethernet. As data is sent as packets, it can sometimes be “held up” in a queue of data. AVB uses the concept of time-sensitive networking which means your audio or video data carries special priority flags to reduce latency. (NB: since publishing this article, it transpires typical Dante latency can be as low as 125u seconds which is, in fact, lower than the 2ms of AVB)

PreSonus is one of only a handful of manufacturers to support AVB.

One of the biggest issues with AVB is that it requires AVB certified Ethernet hardware. Whilst this hardware is 100% backwards compatible with regular Ethernet, it does add extra cost, complexity and incompatibility. On the flip-side, because AVB is open source, the hardware tends to be more affordable as there are no licensing costs.

Unfortunately, industry adoption of AVB has been minimal, with perhaps only Presonus and MOTU building their audio networking gear around AVB. At the time of writing, it’s an uncertain future for AVB in pro audio. Many manufacturers who originally championed AVB are now offering Dante interface solutions for many of their existing AVB equipped product ranges.


  • Theoretically lower latency than Dante thanks to time-sensitive networking
  • Lower cost as an open-source format
  • AVB hardware compatible with existing Ethernet cabling and architecture


  • Requires AVB certified Ethernet switches and hardware
  • Low industry takeup and uncertain future in pro-audio



When is an audio network not an audio network? Answer: when it’s AES50! AES50 is an open-source audio networking format for multi-channel audio carried over regular CAT5 networking cable. Now, strictly speaking, AES50 isn’t an audio networking format as it’s inherently a point-to-point connection protocol. Think about a mixing desk connected to a stage box; that’s a classic point-to-point setup.

We’re including AES50 here as it’s one of the most commonly found ways of connecting multichannel audio gear over CAT5 cable. AES50 is also used extensively by Midas and Behringer, with consoles such as the X32, M32 and Wing offering Dante networking solutions. As a result of those desk’s ubiquity, you’re likely to encounter AES50 in most modern live venues and project studios.

Remember we said AES50 isn’t an audio network format? Well, that doesn’t mean you can’t create an audio network based around AES50. AES50 can be networked using specialised routers via centralised “star network’ topologies. It’s also possible to buy interfacing solutions to connect your AES50 gear to Dante networked hardware for example.

Behringer Wing Digital Mixer

Behringer’s Wing digital mixer supports AES50

Music Group’s adoption and inclusion of AES50 has assured it a strong place in the live sound industry. We expect this open-source format to remain as the default connection for interconnecting consoles and stage boxes, for example.


  • Extremely low (practically nil) latency in operation
  • Low cost as an open-source format
  • Ubiquity thanks to Music Group adoption (X32, M32 ,Wing)
  • Can be interfaced and networked with Dante via 3rd party hardware


  • Doesn’t natively support networking
  • Requires specialised hardware to create an audio network

Other Proprietary Formats

You might be reading this and shouting at the screen, “But my mixing desk doesn’t use any of those networking formats!” Yes, there are audio networking formats aside from those we’ve already mentioned. Worthy of note are Allen & Heath’s gigaACE, and Waves Sound Grid which you’ll find on DigiCo, Yamaha and even Allen & Heath desks! There are also some older legacy formats such as CobraNet which is the granddaddy of audio networking formats.

We haven’t gone into detail on these formats, because in our opinion the future of things seems fairly clear cut. Allen & Heath, DigiCo and Yamaha all offer Dante networking cards for their professional range of mixing consoles. If that isn’t an admission that Dante is emerging as the dominant industry standard, we don’t know what is! None the less, it’s a good idea to familiarise yourself with these other formats, if only to be aware of what gear will work seamlessly together.

What Networking Format Should I Choose?

Ultimately, your choice of networking format will be governed by budget, application and to some extent the mixing console you feel most comfortable with. Dante offers the only networking format which can be supported cross-platform. It seems almost every manufacturer is offering Dante plug-in cards or native Dante support nowadays making it a “future-proof” solution.

With that said, if all you need is a simple point-to-point connection from desk to stage box, AES50 is simple and affordable and may well be all that your application requires. AVB networking offers much on paper, but its requirements for dedicated switches and lack of wider industry adoption means this may well be the “Betamax” of audio networking.

What do you use in your day to day productions? Have you dipped your toes in the water of audio networking yet? Drop us a comment and let us know what format you’re using!

2 responses to “Dante, AES 50, AVB and all that: What audio networking format is right for you?”

  1. There are some fundamentally flawed statements in this article.
    Predominantly relating to costs and “complexity” of Dante Systems.
    Network switches for AVB are on average at least 3x the cost of network switches for AVB, and the comments regarding latency are incorrect too.
    Dante latency can be selected to be as low as 125uSeconds.
    Please address these factual errors.

    • Bob Malkowski says:

      Hey Liam, thanks for your reply. let me try and address your points in turn:

      As mentioned in the article, AVB requires certified network switches which are more expensive than regular Ethernet switches as used by Dante.

      The flipside is that Dante hardware is typically more expensive than AVB systems and especially more so than AES50 systems. This is an avoidable factor caused by Audinate’s monopoly on the chipsets implemented by manufacturers. That cost has to be passed on to the customer.

      Theoretically, AVB should offer lower latency than Dante due to time-sensitive networking. However I am happy to concede that if in practice you’re seeing latency as low as 125u seconds that’s lower than AVBs typically 2ms.

      AES50 still offers the lowest latency of all however at 63us. In reality would any of this be noticeable in a live venue? It’s debatable!

      I have yet to meet a fellow live engineer or systems engineer that hasn’t had a gripe about how difficult Dante is to work with. I’ve also spoken with academic institutions with large Dante networks complain about how unintuitive Dantes networking software is. I’m happy to stand my ground on it being a complex system to use, if not to implement physically.

Leave a Reply

Your email address will not be published. Required fields are marked *