X32 Stage Box No Sound? Local vs AES50 Input Routing Fix

The band is on stage and everything is powered up, but the input meters on your X32 are flat. Nobody touched a cable. It’s easy to panic ten minutes before soundcheck.

Most of the time the cause is one routing setting: the console is listening to the wrong place. Once you know where to look, it’s usually about a 30-second fix. Everything here works the same on the Behringer X32 and the Midas M32, since they run essentially the same software on different hardware.

The Short Answer

Push Routing, open the Inputs tab, and read what each bank of eight is set to. If your mics are plugged into a stage box but the banks say Local, the console is listening to its own back panel, and there’s nothing plugged in there.

Point those banks at AES50 A or AES50 B, whichever port the stage box is actually on, and the meters come back.

If that doesn’t fix it, work through the checklist further down. First, though, it helps to know why this happens.

Why a Plugged-In Mic Can Be Silent

On an analog mixer, the channel 1 input jack was hardwired to the channel 1 fader. The gain knob, the EQ and the fader were all one fixed strip.

A digital console splits that into two layers.

The jack you plug into and the fader that controls it are separate layers. Nothing is connected until you route it.

On one side are all the possible sources: the local XLR inputs on the back of the console, the aux inputs, stage boxes over AES50, and the expansion card. On the other side are the 32 channel faders.

Routing connects the two sides. If it points at the wrong source, you get silence and no error message.

How the Inputs Page Works: Banks of Eight

The Routing → Inputs tab controls what feeds the console’s fader channels. It’s laid out in banks of eight (channels 1–8, 9–16, 17–24 and 25–32), plus the aux faders.

In each column, scroll up or down to pick the source for those eight channels. All eight channels in a bank move together.

A brand-new X32 ships with local XLR inputs 1–32 feeding channels 1–32. To set that by hand, push Routing, go to the first tab (Inputs), and set the left column to Local 1–8. Then do the same for the next three columns.

That factory default is why stage boxes catch so many people off guard. The band moves to a stage box, but the console still listens to the empty jacks on its back panel.

Each channel also has its own source setting. I keep that one set 1:1 (input 1 to channel 1, and so on) and use USER routing when I need per-channel changes, which is the better way to do it.

What Changes When You Add a Stage Box

Sometimes the best way to introduce an X32 is to plug the old analog snake from the stage into the back of the console at front of house. That works if the snake exists and is in decent shape. Still, stage boxes are one of the biggest reasons to go digital in the first place.

A digital stage box takes the mics and instruments on stage, converts them to digital, and sends them all down one shielded Ethernet cable to the console. The signal on that cable is called AES50, and the X32 has two AES50 ports, A and B.

The wiring rules that matter:

• Use shielded Ethernet cable. Shielded cable is a requirement for AES50. Major problems can show up if you skip it.
• It’s point-to-point. The cable is Ethernet, but AES50 isn’t a networking protocol. It goes directly from the console to the box.
• The console connects to the stage box’s A port. On the box, A is the input from the console.
• To chain boxes, run a cable from the first box’s B port to the second box’s A port.

For choosing boxes and how channel numbers work across a chain, see our guide to AES50 stage boxes on the X32.

Three Common Input Layouts

With a stage box in the system, your banks need to point to where the audio actually comes in. Here are three layouts from the video:

Setup	Channels 1–8	Channels 9–16	Channels 17–24	Channels 25–32
Everything plugged into the console	Local 1–8	Local 9–16	Local 17–24	Local 25–32
Everything on stage box inputs over AES50 A	AES50 A 1–8	AES50 A 9–16	AES50 A 17–24	AES50 A 25–32
16 console inputs + a 16-input box on port A	Local 1–8	Local 9–16	AES50 A 1–8	AES50 A 9–16

The third row is where people usually get confused. Two different sources feed one console, and the stage box’s input 1 shows up on channel 17.

Routing on this page also only works in blocks of eight. You can’t put one particular source on one particular fader here. That’s what USER routing is for, covered below.

No Input Audio? Check These in Order

Don’t start pulling cables. Work down this list, because the answer is often in the first few steps.

1. Where should the audio be coming from?

Start with the basic question: is the band plugged into the back of the console, or into a stage box? If your system has documentation, like a patch sheet or a hardware diagram, get it out now. It tells you what the routing should say.

2. Read the Inputs tab

Push Routing and look at the Inputs tab. Do the four banks point at the source from step 1? A stage box on port A with banks set to Local is the classic cause. Change the banks and talk into a mic, and the meter should move.

3. Is the console seeing the stage box?

On the same page, the right side shows a graphic of the stage box connected on AES50 A or AES50 B. There’s also an AES50 A/B connection indicator at the top of the screen.

If neither shows up, changing the routing won’t help. The stage box may not be powered on, so check that first. Then check the cable: shielded, running directly from the console to the box’s A port.

4. Does the bank point at the right port?

A box connected to port B won’t show up on banks set to AES50 A, and a box on A won’t show up on banks set to B. The connection graphic from step 3 shows which port the box is really on, so match your banks to it.

5. Meters moving, but nothing in the room?

Then the input routing is fine, and the problem is on the output side. Check whether the main output is muted or its fader is pulled down.

6. Sources that don’t line up in blocks of eight

If some channels come from the console and some from the box, and they don’t fit into neat banks of eight, use USER routing (next section).

When Blocks of Eight Aren’t Enough: USER Routing

USER routing adds a layer between the inputs and the faders. Use it when a source is plugged in one place and you want it on one specific fader, like a stage box mic on channel 5 or a local XLR on channel 30.

Setup takes two steps:

1. Push Routing, and on the Inputs tab set the banks to User Inputs for all 32 fader channels.
2. Go to the User inputs tab, pick any of the first 32 slots, and assign it a source. That source goes straight to that fader.

After that, you can mix local inputs, AES50 inputs and anything else across the whole console, channel by channel. Our X32 USER input and output routing guide walks through the knobs on that page step by step.

Using the X32 to its full capacity can get confusing, but it feels a lot less random once you can see the layers. No single video can cover every combination of stage boxes and mixed sources, though. That’s why we built ShowBuilder: you describe your console, stage boxes and outputs once, and it builds the routing into a show file you load onto the console, plus a hardware diagram and patch sheet you can print.

The Whole Thing in One Picture

• The input is a separate layer from the channel. Nothing is connected until you route it.
• A new console routes local inputs to the faders. Stage box inputs don’t reach a fader until you change that.
• Routing moves in banks of eight. Change one column and all eight channels follow.
• Using a stage box? Your banks need to read AES50 A or B, matching the port the box is on.
• Mixing sources channel by channel? Use USER routing.

Watch the Video

I go through all of this on the console in the video. You can jump straight to the Inputs tab and banks of eight, stage boxes and the A/B ports, the no-sound checks, or USER routing.

Keep Going

• Send any source to any channel: X32 USER input and output routing.
• Choose, chain and route your boxes: AES50 stage boxes on the X32.
• See the full system: the complete guide to X32 routing and configuration for church audio.
• For problems beyond the console: church AV troubleshooting 101.

More training is on the YouTube channel: youtube.com/@CrazyAmazingDesigns.