Pro AV Index Independent · Pro AV Reference

Dante vs AES67 vs Milan: Which to Specify

Short answer Specify Dante when you need the widest device ecosystem and simplest commissioning. Specify AES67 when you must bridge two different vendors' systems. Specify Milan when you need guaranteed bandwidth and deterministic latency on a dedicated network. Most installed projects end up Dante with AES67 enabled as a bridge.

What each one actually is

Dante is a proprietary transport from Audinate. It carries audio, clock and control over standard Ethernet, and its commissioning tool discovers devices automatically. Its advantage is not technical elegance — it is that several thousand product models already speak it.

AES67 is an interoperability standard, not a product. It defines a common denominator — stream format, PTP profile, discovery — that lets equipment from different ecosystems exchange audio. It deliberately does not define control.

Milan is a certification programme layered on AVB/TSN. Where Dante and AES67 ride on best-effort Ethernet, AVB reserves bandwidth in the switch itself.

Densely populated fibre distribution frame with LC connectors and aqua OM3 patch cords
All three transports ride the same physical infrastructure. The differences are in clocking, bandwidth reservation and control.Photo: Brett Sayles / Pexels

The comparison that matters

DanteAES67Milan
TypeProprietary transportInteroperability standardCertification on AVB/TSN
ClockPTPv1 (native), PTPv2 in AES67 modePTPv2 (IEEE 1588-2008)gPTP (802.1AS)
Switch requirementAny managed switch with QoSAny managed switch with QoSAVB/TSN-capable switch
Bandwidth guaranteeNo — best effortNo — best effortYes — reserved
DiscoveryAutomaticManual or SAP/SDPAutomatic
ControlIncludedNot definedIncluded
Device ecosystemLargestCross-vendor subsetSmallest

How to choose

Ask three questions in this order.

  1. Is the network shared with IT traffic? If yes, Milan is usually out — you will not get AVB switches through a corporate IT department. Dante with correct QoS is the pragmatic answer.
  2. Do two vendors have to interoperate? If yes, AES67 is the bridge, but budget commissioning time for clock domain reconciliation.
  3. Is deterministic latency contractual? If yes — broadcast, live production with strict specs — Milan on a dedicated network is the only one that guarantees it rather than approximates it.

The mistake to avoid

Enabling AES67 mode on Dante devices “just in case” changes the clock behaviour of the whole domain. Turn it on when there is a specific device to bridge to, not as a default.

Frequently asked

Can Dante and AES67 run on the same network?

Yes. Dante devices can enable an AES67 mode that exposes standards-based multicast streams alongside native Dante flows, but the network must carry PTP correctly and the two clock domains have to be reconciled.

Is Milan the same as AVB?

Milan is a certification layer built on top of AVB/TSN. All Milan devices are AVB devices, but not all AVB devices are Milan certified.

Which protocol has the lowest latency?

Milan and AVB give deterministic latency because bandwidth is reserved by the switch. Dante can be configured lower on paper, but its latency is only as reliable as the network's QoS configuration.

Specifying a system right now? [邮箱位 · 待填] [电话位 · 待填]