Dante vs MADI vs AES50: Which Audio Network Should You Use?
Published
\u201CWhy am I running 32 XLR cables to FOH?\u201D — a question every engineer asks once. The answer is digital audio networking: a single Cat5e or BNC cable carrying 32, 64, or 128 channels in each direction. Three protocols dominate, and which one you pick usually depends on what gear you already own.
Quick comparison
| Spec | Dante | MADI | AES50 |
|---|---|---|---|
| Physical layer | Cat5e/6 (RJ45) | BNC coax or fiber | Cat5e (EtherCon) |
| Channels per link | 64 (1Gb), 512+ (10Gb) | 64 | 48 each direction |
| Max distance | 100 m / segment | 100 m coax, 2 km fiber | 100 m |
| Routing | Software (Dante Controller) | Hardware patch only | Point-to-point only |
| Needs a switch? | Yes (managed) | No | No |
| Latency (typical) | ~250 \u00B5s–1 ms | ~1–3 samples | ~62 \u00B5s |
Dante
Dante is the dominant protocol for audio-over-IP in pro live and broadcast. It runs on standard Ethernet, supports software routing through Dante Controller, and is supported by hundreds of devices from dozens of manufacturers.
Pick Dante when:
- You’re mixing gear from multiple brands. Dante is the interoperability layer.
- You need flexible routing — sending one mic to FOH, monitors, and recording with a software click rather than re-patching.
- You’re building a rig with multiple stage boxes, multiple consoles, or computer-based playback (UA Apollo, RME with Dante card, MOTU).
- You can run a managed Gigabit switch (Luminex GigaCore, Cisco SG350) and trust it to be configured right.
Watch out for:
- Switch quality matters. Cheap unmanaged switches will cause clock drift and dropouts. Spend the money on a managed switch with QoS configured.
- Clock master is critical. Pick one device as the master, set the rest to follow. Shifts mid-show cause clicks.
- The free Dante tier is 32x32. Higher channel counts on a Mac/PC need a paid Dante Virtual Soundcard or DVS Pro license.
MADI (Multichannel Audio Digital Interface)
MADI predates the audio-over-IP wave — it’s a 64-channel bidirectional point-to-point link over BNC coax (or fiber) that was the broadcast/recording standard for two decades. Still used heavily in studio environments and high-channel-count broadcast.
Pick MADI when:
- You need long runs over fiber (up to 2 km) without a network switch hop in between.
- You’re tied to existing MADI infrastructure — SSL, Avid, Lawo, Yamaha CL/QL series, RME UFX-MADI gear.
- Latency must be near-zero (sub-ms) and predictable.
Watch out for:
- No software routing. Channel 1 in is channel 1 out. Re-routing means re-patching at a hardware patchbay.
- BNC quality. Use 75-ohm video-grade coax, not generic BNC. Reflection issues over cheap cable will mute the stream.
- Format variants. MADI has 56-channel and 64-channel variants and different sample-rate options. Confirm both ends speak the same dialect.
AES50
AES50 is Behringer/Midas’s answer to MADI — a point-to-point digital trunk over Cat5e (EtherCon). It runs at 48-channel pairs (96 channels each direction on the X32/M32 family’s dual AES50 ports) and adds a control overlay so a console can talk to a stage box on the same wire.
Pick AES50 when:
- You’re in the X32/M32/Wing ecosystem (Behringer, Midas, Klark Teknik). It’s the default trunk between consoles and stage boxes (S16, S32, DL16, DL32, DL251).
- You want zero infrastructure overhead — no switch, no configuration, plug-and-play between two devices.
- Latency is a hard constraint (62 \u00B5s at 48 kHz is best-in-class).
Watch out for:
- Single brand only. Behringer/Midas talks AES50; almost nothing else does. Cross-brand requires a converter.
- Strict cable spec. Use shielded Cat5e (\u201CSTP\u201D) — unshielded UTP can pick up RF noise on long runs and cause dropouts.
- Point-to-point only. No switching, no fan-out to multiple consoles without a hardware splitter.
How to pick in practice
For most new IEM/playback rigs in 2025+, the decision tree is roughly:
- Buying into a Behringer/Midas family? AES50. Cheapest, fewest moving parts, low latency, no switch.
- Mixing brands or need software routing? Dante. The interoperability tax is worth it.
- Long runs (\u003E100 m), broadcast, or tied to existing infrastructure? MADI — usually over fiber.
How IEM Rig handles this
When you wire components in IEM Rig’s Signal Flow view, ports declare their protocol (dante, aes50, ultranet, madi, slink). The wiring engine picks the right cable type automatically — a Dante port and an AES50 port look like the same EtherCon physically, but you can’t actually connect them, and IEM Rig won’t let you. The Signal Flow legend colors digital audio in blue and shows the trunk’s channel count on the edge label, so you can see at a glance that one Cat5e is doing the work of 48 XLRs.
Ready to plan your own rig?
Open IEM Rig →