As promised a few weeks ago, here is a basic troubleshooting guide. Whether the problem is no sound, noise, or something else, these steps will give you a good place to start.
- Prevent the Problem: As the old cliche says, “An ounce of prevention is worth a pound of cure.” This statement is especially true in audio. It amazes me how many of the problems I have had to troubleshoot could have (and probably should have) been easily prevented. A line check, while time consuming and boring will save you a ton of time and embarrassment when everyone is in the room. There is nothing quite like spending ten minutes troubleshooting a bad monitor, only to realize you never plugged it in. Look for a post about efficient line checks in the near future.
- Be Organized: If you have a rat’s nest of cables on the stage that are all a jumbled up mess, not only are problems more likely, they are harder to solve. There is nothing like trying to follow a wire through a knot of cables to see if it is plugged in to the right channel. Speaking of that, make sure you have a full input list that tells you where everything is supposed to be plugged in, how it is supposed to be routed. Put in as much detail as possible and keep it updated. This really helps to give you a better understanding of signal flow and all the potential pieces that could cause the problem, and gives you a handy guide to where everything should be plugged in and how it should be patched. I include channel name (and the name of the person using that channel, so I can call them by name if I don’t know them), stage and console patching, whether the channel requires phantom power, and notes on type of mic and specific routing. If seeing a copy of my input list would be helpful for you, let me know.
- Separate and Mark: This is part of the organizational step, but I am going to list it separately. Make sure you label bad equipment as bad. I use gaff tape and silver sharpie for this. I always write down what is wrong with the item, not just “broken”. That will save time when it comes to fixing it. Labeling also prevents you from using bad equipment and having to troubleshoot all over again.
- Apologize and Communicate: Whether it is your fault or not, apologize to the band for the delay. As a musician, it is very frustrating to be ready to play, and then not being able to. Communicate what the issue is, let them know you are working on it. They don’t need to know every step, but let them know you are thinking about them. Also, if you are going to do anything that might make noise, ask them to take out their in-ears, or turn them off. Don’t take risks with their hearing. If you would want to mute it in the house speakers, have the same consideration for the musicians.
- Eliminate the Obvious: It amazes me how many issues I run into that probably should not have been issues (see step 2). For example, a plug not fully seated, an amp not turned on, etc. If something is not working, check the connections. Ask the musician to unplug and replug the chord. (Don’t say, “Is it plugged in?” Use their name and say please. No point in coming across as a jerk. That won’t help anyone.)
- Determine the Seriousness: Is this problem something you can live with? If there is a bit of hum during rehearsal, is it worth delaying the rehearsal, and possibly keeping everyone later, or can this be solved afterwords, or tomorrow, when your troubleshooting is not under the stress of a time crunch? If it’s Sunday morning, is this a problem that will (or has the potential to) affect the service. Typically, I follow the better safe than sorry philosophy, especially on Sundays, but there are times where no one in the room but me would notice the problem. Ask yourself, and your worship leader, is that worth stressing over today?
- Find a Work-Around: If you are trying to get something fixed quickly to get a service or rehearsal running, this should be your go to tool. Often, we do not have time to find and solve the problem, we just need a functioning solution. Fifteen minutes before service or sound check starts is not a great time to take apart a monitor and check the soldering connections. That is something to do on Monday. When troubleshooting in a time crunch, the goal should be finding a workable alternative. Always keep spare mics, monitors, and cables handy, and make something work, anything, even if it is not the ideal set-up.
- Eliminate and Isolate: When you have time to seriously dig in and do the real troubleshooting, this is my process. Go through the entire signal change start to finish and eliminate all possible causes. For example, if you are troubleshooting a buzz in an electric guitar channel, look at the entire chain. It starts with the guitar, then each pedal on the board, the amp, the mic, the cables, the snake, the stage rack, the console. Use the process of elimination to narrow down the possibilities. Plug the guitar straight into the amp and bypass the pedal board. If the problem goes away, you know it is somewhere on the pedal board, if it persists, then the pedals are not the problem. Try a different guitar, different cable, different amp, different mic, different snake channel, different board channel, different power source, all one at a time until you figure out the problem. Eventually you will find the problem. Then isolate that part to confirm that is the problem. Remove everything else possible from the signal chain and make sure the problem is actually that part and not something else.
- Fix the Issue: Now that you have found and confirmed the problem, fix it. Don’t just put it in the corner of the closet. The old adage “out of site, out of mind” really applies here. If you don’t see the problem part, you won’t fix it. Put it on your desk, so you can’t check your e-mail without staring at it. Put it in the middle of the floor of your office so you trip over it every time you walk in. Do not let yourself forget about it. If you can fix it yourself, great, but if you are paying someone else to fix it, make sure you know the cost to repair vs. replace. Often I have found there is a significant difference, but sometimes it is not much more to buy a new replacement part then to repair the old one. Just make sure you don’t replace it with a cheap part that you may have to troubleshoot again in a year.
I hope this guide is helpful to you. If you have any tips that I have missed, or questions, please add them in the comments section.