AES50 Stage Boxes on the X32: Connect, Chain & Route Them Right

A digital stage box replaces the fat copper snake we all used to wrestle from the stage to front of house with a single ethernet cable. One skinny cable, and every input on stage arrives at your console — that’s AES50, and it’s built into every X32 and M32.

It’s also where a lot of “why is there no sound” mysteries are born, because a stage box adds one more routing layer on a console that already had two. So let’s walk it start to finish: which box to buy, how the A and B ports actually chain, and how to route inputs and outputs so signal lands where you expect.

Prefer YouTube? Watch this video on the channel.

Which Stage Box? The Four (Plus Two) Options

Behringer makes four AES50 stage boxes. The SD8 and its big brother the SD16 are built to sit on the stage deck. The S16 and S32 are rack-mount designs — though practically, all of them can live in a rack. Midas makes the DL16 and DL32 with Midas preamps if you want the step up.

And an honorable mention I use constantly: the X32 Rack as a stage box. It’s a full standalone mixer, but because it speaks AES50 it integrates with the whole X32 family — and having a dedicated console for in-ear monitors keeps the band off your front-of-house mixer, where a musician “adjusting their ears” can accidentally adjust the room. I’ve written more on that setup in using the X32 Rack as an IEM mixer and stage box.

How the A/B Ports Chain

Every stage box has two ethernet ports: AES50 A and AES50 B. The connection is genuinely two-way — audio flows in both directions — but the wiring rule is simple if you hold one picture in your head:

Coming from the console, the A port on a stage box is always the input. The B port daisy-chains to the next box’s A port.

Console AES50 A → first box’s A port. First box’s B port → second box’s A port. And so on down the chain.

Channel numbering follows the chain order, not the box model: the first box in the chain gets the first 8 (or 16) inputs, the second box gets the next batch. Swap the cable order and the numbers swap with it — an SD8 chained second is inputs 17–24; chained first, it’s 1–8. If four SD8s were chained, they’d be 1–8, 9–16, 17–24, 25–32 in cable order.

Is It Even Connected? The 30-Second Check

Before touching any routing, confirm the console sees the box. Push Routing and tab to the first inputs page — there’s a graphical view of every stage box connected, with a green square when the link is healthy. If two boxes share one port you’ll see “1 of 2,” and tapping down a layer shows the second box.

The hardware agrees with the screen: a green LED by the AES50 port on the box itself, and lit A/B link lights. If the graphic doesn’t show your box, it’s a cable or power problem — no amount of routing will fix it.

Routing the Inputs

With the box connected, the console needs to be told to use it. Set your four input banks as USER inputs (Routing → inputs tab), then on the users tab, assign each channel its source: change the category from Local In to AES50 A, then pick the input number.

The demo in the video makes it concrete: a mic in the SD8’s input 1 arrives as AES50 A input 1. Move that same mic to the second box in the chain — an S16 — and it now arrives at input 9, because the second box starts where the first box’s channels end. Same mic, same cable type, different address.

Routing the Outputs (the Part Everyone Skips)

Stage boxes don’t just bring audio from the stage — their XLR outputs send audio back: monitor wedges, in-ear systems, powered speakers at the stage.

Two pieces have to agree. On the console, the AES50 A/B tabs decide which outputs get pushed down the cable — I set the columns to user outs, then assign each one on the users tab (out 8 as the main mix, a mix bus to an output, whatever the room needs). On the box, the SD8/SD16’s switch (the S16 uses a knob) decides which batch of those outputs — 1–8, 9–16, or 17–24 — lands on its physical XLR ports.

Flip that switch and the box’s XLRs change identity — which is exactly the “audio just stopped” moment in the video. If an output dies right after you touched the box, check the switch before you check anything else.

One habit worth stealing: user outputs assigned once show up everywhere you point them — the console’s own XLR outs and the AES50 stream can carry the same assignments. Set them deliberately once, and every destination stays predictable.

Set It Up Once, Correctly

Everything above is exactly the kind of configuration you want to do once, save as a scene, and never improvise on a Sunday morning. (And always save your scene before experimenting — View → scenes → save. The console will ask if you want to overwrite. You do.)

If you’d rather start from a working configuration than a blank console, ShowBuilder builds your complete X32, M32, or WING show file around your exact stage boxes and hardware — free to start, from $49 to download your .scn or .snap file. There’s also my X32 Show File & Routing Master File Package with my default routing and console layout plus a routing cheat sheet ($45.99).

Related

• X32 USER Input & Output Routing: Send Any Source to Any Channel
• Using the X32 Rack as an IEM Mixer and Stage Box for FOH
• Behringer X32 Routing and Configuration for Church Audio

More X32 training on my YouTube channel: Youtube.com/@CrazyAmazingDesigns.