Church AV Troubleshooting 101: How to Diagnose and Fix Production Problems Fast

There is nothing quite like the sinking feeling of something going wrong fifteen minutes before service starts. No audio in the monitors. The projector shows a blank screen. The livestream won’t connect. Your pastor’s mic is cutting out. In those moments, you need to think clearly and move fast — and if you haven’t developed a troubleshooting framework, you end up doing what most people do: unplugging and replugging things randomly and hoping something works.

I’ve been in those moments more times than I can count. And at Crazy Amazing Designs, troubleshooting is one of the things I love helping church tech teams build real skill in — because a team that can diagnose problems quickly is a team that stops dreading Sunday morning and starts owning it.

Why Church AV Troubleshooting Is Particularly Hard

Church production environments are uniquely challenging to troubleshoot because of complexity and time pressure. You’re dealing with multiple interconnected systems — audio console, video switcher, presentation software, streaming encoder, lighting board — that all have to work together. When something breaks, the failure could be anywhere in that chain. And you have a fixed, immovable deadline.

The other challenge is institutional memory. A lot of churches have production setups that were configured by someone who left, with no documentation. Volunteers don’t know why things are set up the way they are — they just know which buttons to press when things work. When something breaks, they have no mental model to fall back on.

That’s the #1 thing Crazy Amazing Designs helps churches build: understanding. Not just “press this button to fix this” — but a real understanding of how signal flows through your system so that when something unexpected happens, you can figure it out.

The Troubleshooting Framework That Actually Works

Step 1: Isolate the Signal Chain

Every AV problem is a signal that’s either missing, wrong, or going somewhere it shouldn’t. Before you do anything else, ask yourself: where is the signal supposed to be, and where is it breaking down?

For audio: the signal path goes Source (microphone or DI) → Cable → Stage Box/Input → Console Channel Strip → Bus/Output Mix → Output Cable → Speaker System. A missing microphone in the house mix could fail at any one of those points. Your job is to identify WHERE.

For video: Source (camera, ProPresenter, playback) → Cable → Switcher Input → Switcher Output → Projector/Display. A blank projector screen could be a camera that’s off, a bad HDMI cable, a switcher input that’s not selected, a resolution mismatch, or a display that’s not set to the right input.

Starting from one end and working toward the other — rather than guessing at random — is the single biggest efficiency gain in troubleshooting.

Step 2: Use Solo and Meter Functions

On your X32 or any digital console, the Solo button is your best friend when troubleshooting audio. Soloing a channel routes it to your headphones for monitoring without affecting the main mix. If you can hear signal in your headphones when you solo a channel, the input is working — the problem is downstream. If you can’t hear anything, the problem is upstream from the console.

Meters tell you whether signal is present at all. If your channel meter isn’t moving when a microphone should be active, you have a physical input problem — check the cable, the connector, phantom power (if it’s a condenser mic), and the gain knob. These three checks will solve the majority of “no audio” issues in minutes.

Step 3: Swap the Cable First

Cables are the most common single failure point in any live production environment. Before you start questioning your routing, your console settings, or your software, swap the cable. I’ve seen production teams spend 30 minutes troubleshooting a complex routing issue that turned out to be a broken XLR cable.

Keep a small bag of known-good spares for your most common cable types: XLR, TRS, HDMI, and ethernet. If you can swap a cable in 30 seconds, do it before anything else.

Step 4: Know Your Resolution Mismatch Symptoms

A TON of church video problems come down to resolution or frame rate mismatches. If your projector is flickering, showing a scrambled image, or showing “no signal” despite a connected source, the source and the display may be set to different resolutions or frame rates.

On the ATEM Mini, if an input shows “No Signal” in the multi-view monitor, it’s almost always one of three things: the source device is outputting a resolution the ATEM doesn’t support, the cable is bad, or the HDMI handshake failed (often fixed by power cycling the source device). I cover cable types and what to use where in my video Live Production Cables — HDMI vs HDMI Fiber vs SDI vs Fiber — this one is worth watching if you’re ever dealing with “no signal” mysteries.

Step 5: Check the Obvious Things

I say this with the deepest respect: check the obvious things. Is it muted? Is the gain turned up? Is the right input selected? Is the output assigned correctly? Is the display set to the right input?

The human brain, under time pressure, skips right past the obvious because it assumes someone would have already checked. Many production emergencies have been solved by realizing the monitor mix send for Bus 3 had accidentally been turned off. Or the projector was set to HDMI 2 when the signal was on HDMI 1. Check the simple things first, every time.

Building a Troubleshooting Culture on Your Team

The best thing you can do for your church’s long-term production health is document your system and train your team to understand it — not just operate it. This means having a system diagram that shows signal flow, a list of what each X32 bus is used for, notes on your ProPresenter screen configuration, and a record of what each ATEM input is connected to.

When your lead tech is sick on a Sunday, the backup volunteer shouldn’t be flying blind. Crazy Amazing Designs can help you build that documentation and train your team — whether that’s through team Zoom training sessions, on-site consulting, or both.

The other piece of troubleshooting culture is post-service debriefs. If something went wrong during service, spend five minutes after the service ends identifying what it was and why. Write it down. Over time, you’ll build a church-specific troubleshooting guide that solves YOUR problems, not just generic ones.

Where It Gets Complicated

Intermittent problems are the hardest to troubleshoot because they don’t reproduce on demand. A microphone that cuts out “sometimes” could be a marginal cable, a worn connector, a wireless interference issue, a software bug, or a power problem. If you can’t reproduce the failure, you can’t test your fix.

The strategy for intermittent problems is substitution: swap out each variable in the chain one at a time until the problem stops. Start with the most likely culprit (usually the cable), then work toward the less likely ones.

Also: networked audio and video systems add a whole new category of troubleshooting complexity. If you’re running Dante audio networking, NDI video over IP, or AES50 digital snake connections, problems in those systems require understanding the network layer in addition to the audio/video layer. This is where having someone who knows both production AND networking is genuinely valuable — and it’s one of the specializations at Crazy Amazing Designs.

Stop Dreading the “Unknown Problem” — Get Trained

The difference between a church tech team that panics when something breaks and one that handles it calmly is knowledge and practice. You can’t practice in front of a congregation, but you CAN build the knowledge in advance.

I’m Nathan Robb at Crazy Amazing Designs, and I offer single Zoom sessions where we can walk through YOUR specific system, build your troubleshooting muscle, and document your setup so your whole team understands it. One session can make a bigger difference in your Sunday morning confidence than a year of figuring it out on your own.

Book a single Zoom session at CrazyAmazingDesigns.com/training

More church production training at Youtube.com/@CrazyAmazingDesigns

In Christ, Nathan Robb