Soundcheck Diaries

Whether I’m mixing at church, working with one of the bands at Campus JAX, or doing an offsite gig somewhere else, there’s one setup that seems to invite troubleshooting adventures: the guitar with a pedalboard that looks like it could launch a small spacecraft.

The musician plugs in.

I unmute the channel.

Nothing.

And then come those famous words every sound engineer has heard at least a hundred times:

“I don’t understand. It worked the last time I used it.”

Of course it did.

Maybe “last time” was yesterday. Maybe it was last week. Either way, the musician usually looks toward the sound booth with that slightly concerned expression that says, What did you do to my guitar?

The truth is, it’s usually nobody’s fault. There are simply a lot of places for a signal to disappear when it has to travel from a guitar, through a collection of pedals and patch cables, into a DI box, down an XLR, through the stage system, and finally to the console.

And every connection is another opportunity for our little guitar signal to wander off and get lost.

I ran into exactly this situation recently at church.

Our worship leader had his acoustic guitar running through about six pedals before hitting a DI box. Everything was connected, everything looked normal, and then he unmuted his guitar.

Nothing.

No signal.

And right on cue:

“It worked last time.”

Naturally.

The challenge at church is that soundcheck tends to be fast and furious. The worship team needs to start rehearsing, and often the time immediately before the service is the rehearsal. Nobody wants to spend 15 minutes watching the sound engineer crawl around on the floor tracing patch cables through six guitar pedals.

So when a guitar signal disappears, I don’t just need to find the problem.

I need to find it fast.

Which raises the real question:

What’s the fastest way to figure out where the signal got lost?

Start With the Signal Path

In this case, the worship leader was playing an acoustic guitar with an onboard pickup, running through several pedals before reaching the sound system.

The signal path looked something like this:

Acoustic Guitar → Pedal 1 → Pedal 2 → Pedal 3 → Pedal 4 → Pedal 5 → Pedal 6 → DI Box → XLR Cable → Stage Input → Console

That’s a lot of places for a signal to disappear.

And this is important not only for sound engineers. If you’re a musician who regularly uses a pedalboard, learning how to troubleshoot your own signal path can save you a lot of heartache—and save everyone some precious soundcheck time.

Step 1: Check the Obvious Stuff First

Before you start unplugging everything, take a few seconds to check the easy things.

Is the guitar volume turned up? Is the guitar actually plugged in all the way? Does the acoustic guitar use an active pickup with a battery? Are the pedals powered? Is the tuner muted? Is there a volume pedal sitting all the way down?

It sounds almost too simple, but these are exactly the kinds of things that get missed when everyone is in a hurry.

And yes, I have absolutely troubleshot an entire signal chain only to discover something was muted.

Humility is an important audio tool.

Step 2: Bypass the Entire Pedalboard

This is the fastest way to eliminate a huge portion of the signal path.

Take the cable coming from the acoustic guitar and plug the guitar directly into the DI box.

Now your signal path is:

Acoustic Guitar → DI Box → XLR → Stage Input → Console

Do you have signal?

If the answer is yes, congratulations. In a matter of seconds, you have confirmed that the guitar pickup is working, the DI is working, the XLR path is working, the stage input is working, and the console is receiving the signal.

You also now know something very valuable:

The problem is somewhere in the pedalboard.

Instead of troubleshooting the entire sound system, you’ve narrowed the search considerably.

Step 3: If There’s Still No Signal, Work Downstream

If the guitar still doesn’t produce signal when connected directly to the DI, the pedals probably aren’t your problem.

Now check the shorter signal path.

Try another instrument cable between the guitar and DI.

Check or replace the guitar’s battery if it has an active pickup.

Try another DI box.

Try another XLR cable.

Try another stage input if necessary.

At this point you’re simply asking:

Where does the signal stop?

That question is much more useful than randomly changing settings on the console.

Step 4: If the Pedalboard Is the Problem, Divide It

Let’s say the guitar works perfectly when plugged directly into the DI.

Now we know the problem is somewhere here:

Guitar → Pedal 1 → Pedal 2 → Pedal 3 → Pedal 4 → Pedal 5 → Pedal 6 → DI

You could start with Pedal 1 and check every pedal and every patch cable one at a time.

But there’s a faster way.

Divide the signal path.

Instead of checking all six pedals individually, start somewhere near the middle of the pedalboard.

For example:

Guitar → Pedal 4 → Pedal 5 → Pedal 6 → DI

Do you have signal?

If you do, then Pedals 4 through 6 and their associated connections are probably okay. Your problem is likely somewhere among Pedals 1 through 3.

If you still have no signal, the problem is likely somewhere in Pedals 4 through 6.

Now divide that smaller section again.

Each test eliminates a large group of possibilities.

That is much faster than staring at six glowing pedals and wondering which one has betrayed you.

Step 5: Check the Patch Cables Too

Remember that the pedal itself may not be the problem.

Every pedal adds at least two connections, and every little patch cable between pedals is another possible failure point.

A pedalboard with six pedals may contain far more individual connections than you realize.

So when you isolate a suspicious section, test both the pedals and the cables connecting them.

Sometimes the expensive pedal is perfectly fine.

The little six-inch cable next to it is the villain.

The Goal Is to Eliminate Possibilities

Good troubleshooting isn’t about immediately knowing what broke.

It’s about reducing the number of things that could be broken as quickly as possible.

Start simple.

Bypass large sections of the signal path.

Confirm what works.

Then keep narrowing the problem until there’s nowhere left for it to hide.

Click here for a downloadable PDF of this chart. Print it out and put it in your guitar cases and/or gig bags for quick reference.

For musicians, learning this process can mean the difference between calmly finding a bad patch cable and spending ten frantic minutes looking toward the sound booth wondering what the engineer did to your guitar.

And for engineers, it gets us back to the thing everybody was waiting to do in the first place:

Soundcheck.

Follow the Signal

The next time your guitar is plugged in and you hear nothing, don’t panic—and don’t start randomly unplugging everything in sight. Follow the signal path, simplify it, and eliminate possibilities one section at a time. Whether you’re the musician holding the guitar or the engineer behind the console, knowing how to quickly find where the signal stops can save precious soundcheck time, a lot of frustration, and maybe even a few accusations that “the sound guy did something.” Because sometimes the culprit really is just that little six-inch patch cable.