When your X32 isn’t cooperating on a Sunday morning, your entire service depends on diagnosing the problem quickly. The good news is that most X32 issues follow predictable patterns. Audio problems typically stem from one of a few common causes: broken signal paths, incorrect routing, misconfigured settings, or occasionally a hardware connection issue. This guide walks through the most frequent problems and their solutions, using systematic troubleshooting to get you back on track.
Diagnosing No Audio Signal
When you plug in a microphone and hear nothing at all, the first step is isolating whether the problem is with the microphone, the cable, the X32 channel, or the main output. Start by selecting a microphone that you know works—probably the main vocal microphone from a previous service. Plug it into Channel 1 of your X32. Tap the microphone gently while watching the input meter for Channel 1 on the mixer’s screen.
If you see the meter move, your signal is reaching the X32 and the microphone works. If you see no meter movement, the problem is either the microphone or cable. Try a different microphone or cable to narrow it down. Most churches keep a backup microphone or cable specifically for troubleshooting.
Once you’ve confirmed signal is reaching the X32, select Channel 1 on the mixer by pressing its fader. Look at the buttons below the channel fader. You should see a button that routes the channel to the main output—it might be labeled “Out,” “Main,” or “L-R,” depending on your firmware version. Press this button and confirm it illuminates, indicating the channel is routed to the main output.
Next, look at the main output faders on the right side of the mixer. The Left and Right main output faders should not be pulled all the way down. Move them to approximately the 0 dB position (marked with a line). If the main faders were at the bottom, that’s your issue—nothing comes out regardless of your channel settings.
Now, looking at the main output meters (also on the right), tap the microphone again. You should see signal movement on the main output meters. If you still see nothing, the problem might be in your speaker connections. Check that the X32’s output cables are firmly connected to your power amplifier, and that the amplifier itself is turned on and functioning.
Feedback: Causes and Solutions
Feedback occurs when your speakers send audio back into a microphone, which then gets amplified, sent back to the speakers, and repeats, creating an ever-increasing screech. This is one of the most panic-inducing problems in live sound, but it has clear causes and solutions.
First, immediately pull the fader of the offending channel all the way down. This stops the feedback. Then, identify which channel is causing the problem. Most feedback in churches comes from the main vocal microphone. Once you’ve muted the problem channel, investigate why feedback is occurring.
The most common cause is the microphone being pointed toward a speaker. During setup, ensure all microphones point toward their source (the vocalist’s mouth, not toward the stage monitors or main speakers). The second most common cause is the main output level being too high. If the overall system level is cranked excessively loud, the speakers are blasting sound at such volume that it’s bleeding into open microphones.
The third cause is more subtle: channel feedback where a channel is routed to multiple outputs and those outputs are reaching the same speaker. For example, if Channel 1 is routed to both the main output and a monitor auxiliary, and both those outputs go to the same speaker system, you’ve created a feedback loop. Check your routing carefully.
To prevent feedback, establish a few preventative practices. First, use cardioid microphones that reject sound from the rear and sides—this is standard for worship but bears repeating. Second, keep the main output level moderate; your power amplifier should be controlling the actual volume heard in the room, not the X32’s main faders. Third, ensure only the channels actually being used are routed to the main output; muted, unused channels should have their routing bypassed.
If feedback occurs unpredictably, consider whether a newly added audio source is the cause. Sometimes a monitor speaker has been turned up or moved closer to a microphone without anyone realizing it. If possible, have one person focus on locating the problem source while another operates the mixer.
USB Audio Not Showing Up in OBS or vMix
You’ve got the X32 connected to your streaming computer via USB, but OBS or vMix doesn’t see it as an audio input option. First, verify that the USB cable is firmly seated in both the X32 and the computer. Try a different USB port on the computer if available—sometimes USB ports stop working.
On the X32, navigate to Setup, then IO, then USB. Confirm that “USB Audio” is enabled. If it’s disabled, enable it and the mixer will reboot. Wait for the reboot to complete, then unplug and replug the USB cable to force the computer to re-enumerate the device.
On Windows, open Device Manager (search for “Device Manager” in the Start menu). Look for “Behringer X32” in the list. If you see a yellow question mark, the device driver needs attention. Visit Behringer’s website, download the latest USB drivers, and install them. After installation, restart your computer and try again.
On Mac, open System Preferences, go to Sound, and check the Input tab. You should see “Behringer X32” listed. If it’s missing, restart your computer. Restart the X32. Unplug the USB cable, wait 10 seconds, and plug it back in.
If the X32 shows up as a sound device but OBS or vMix still doesn’t see it, open OBS and go to Settings > Audio. Click the dropdown for “Mic/Auxiliary Audio Device” and look for the X32. If it’s not there, click the dropdown for “Audio Monitoring Devices” and verify it’s available there. The device might be listed under a different name; look for “USB Audio CODEC” or “Behringer USB.”
Scene Corruption and Recovery
Occasionally, the X32’s internal memory can become corrupted, causing scenes to load with unexpected settings or a scene to fail loading entirely. If you suspect a scene has become corrupted, attempt to load a different scene first. If other scenes load correctly, just this one scene is problematic. Load a known-good scene and manually re-enter the settings that the corrupted scene should have.
To prevent future corruption, regularly export your show files to a USB drive. Insert a USB drive into the X32’s USB port (the one on the front panel, not the rear Ethernet USB). Go to Setup > Show > Export. Select your show file and export it to the USB. Keep multiple copies of these backups.
If multiple scenes are corrupted or your show file becomes unloadable, you can recover from your backup. Insert the USB drive containing your exported show file. Go to Setup > Show > Import. The X32 will import the show file from the backup, restoring your scenes.
Routing Accidents and How to Fix Them
Sometimes a channel that should go to the main output accidentally gets routed only to a monitor bus, or vice versa. To check routing on a channel, select that channel by pressing its fader. Look at the row of buttons below the channel parameters. You should see at least one button illuminated indicating the output(s) the channel is routed to.
For most channels, “Main” or “L-R” should be illuminated. If it’s not, press it to route the channel to the main output. If “Main” is already illuminated, check whether another button is also illuminated—perhaps the channel is routed to an auxiliary bus unintentionally. Press unnecessary buttons to deactivate them.
A common accident is accidentally disabling all routing for a channel. The result is you hear nothing from that channel in any output. Again, select the channel and press the “Main” button to re-enable main output routing.
Another routing mistake involves the channel send levels. A channel might be routed to the main output, but its send level to a monitor bus is too high, causing the channel to appear loud in monitors and quiet in the main mix. This is confusing. Verify that you’re actually adjusting the correct send level for the monitor bus, not the main output level.
Distortion and Level Issues
If your audio sounds distorted or muddy, the most likely cause is excessive gain at the input stage. Check the preamp gain for the affected channel. If you see the input meter in the red zone, the gain is too high. Reduce the gain until peaks sit at -12 dB to -6 dB.
If the overall system output is distorted, the problem is likely the main output level being too high. Pull the main L/R faders down slightly. The actual volume heard in the room is controlled by your power amplifier, not primarily by the X32’s main faders. The X32’s main faders should typically sit at 0 dB, with the amplifier controlling volume.
If audio quality sounds generally poor or muddy despite correct levels, you might have EQ problems from a previously saved scene. Load a fresh scene or check whether old EQ settings from a previous service are affecting the audio. Bypass or reset the EQ on affected channels.
Power and Connectivity Issues
If the X32 won’t turn on, verify that the power cable is firmly connected to both the mixer and the wall outlet. Try a different wall outlet to rule out a breaker issue. Listen for any indicator lights or sounds when you turn on the power switch. If there’s absolutely no response, the power supply might be faulty.
If the X32 loses USB connection periodically, try a different USB cable and a different USB port on your computer. Wireless USB hubs should be avoided for mixer connectivity. Use direct wired connections for reliability.
If your X32 seems sluggish or unresponsive, it might be running low on internal memory or processing power. This is rare but possible after many years of use with large show files. Power cycle the mixer completely (turn it off, wait 30 seconds, turn it back on). If sluggishness persists, contact Behringer support about a possible firmware update or hardware inspection.
Getting Help and Escalating Issues
For problems you can’t resolve with this guide, Behringer provides official support through their website. You can also find active X32 communities on Reddit (r/livesound) and numerous Facebook groups dedicated to Behringer equipment. Church tech coordinators often share solutions with each other in these communities.
Before reaching out for help, gather information: What exactly is not working? What have you already tried? Does the problem occur consistently or occasionally? What was different about today compared to previous successful services? Having this information ready speeds up troubleshooting dramatically.
Most X32 problems resolve with simple troubleshooting and clear thinking. The mixer is fundamentally reliable, and professional sound engineers worldwide use them successfully for complex productions. Develop the habit of checking one thing at a time systematically, and you’ll be able to diagnose any issue.