Talking with worship technicians and worship leaders, I often hear the complaint that from week to week, the quality of Sunday morning services varies.
Some of this stems from training, such as when there’s a problem and the tech doesn’t know how to fix it. Some of it is skill; for example, some sound engineers just have a better ear and command of the equipment than others.
The skill level of musicians may also vary, usually due to lack of experience and thus confidence. When they know a song, no problem, but when they’re unsure, they hold back and can become tentative.
But in my experience, there’s another primary contributor to the problem of inconsistency: equipment status and organization.
Example: It’s five minutes before the start of the service, and the sound engineer is sweating bullets, being told to set up for an additional four musicians that the worship leader hadn’t mentioned until just now. No time for sound check, no time for even a simple line check for these new players.
The mics and direct boxes are quickly located, plugged in, and positioned, and then the engineer high-tails it to the sound booth in time for the start of the service.
Rough estimates are made requiring the input gain and monitor levels, a quick prayer murmured, and the channels are unmuted for the opening song.
Then, and of course, “it” happens: that infamous bzzzzzzzz that makes everyone’s hair stand on end!
This particular time, the problem is the additional bass player’s direct box. Time for a split decision: mute the channel or quickly get to the stage to check find the cause, likely the line cord on the bass, or the direct box is faulty (or set wrong), or the direct box cable is bad, or…?!?
With so many potential trouble spots, and so much else going on during the service, the choice is likely going to be to mute the channel and be comforted by the fact that at least some of the sound coming from the bass rig is still being heard in the house, so the player’s efforts aren’t completely wasted.
Was this entire situation preventable? Of course! And, as usual, it’s the simple things that matter most.
There are at least five things that could and should have been done prior to this “sweat and bzzzzzz” fest:
1) Basic maintenance. All cables and cords need to be checked on a monthly basis. In addition, these should be treated properly (wrapped correctly) and organized (hung in a single, logical location). I recommend a peg board, where cables are sorted by type and length. This way, they can be easily found, even in pressure situation, and will work correctly.
There should be at least two spare cables for each variety of cables (and connectors) being used.
2) Organization. Staying with audio, it’s vital to know exactly how many inputs, and what type, will be required for each and every service. And all of these must be set up and tested ahead of time.
3) Communication. Techs should regularly interface with the worship leader and never be shy about asking if anything new or unusual is coming up. Do this early, and as often as necessary. It beats being surprised, and, it also beats having things go wrong on Sunday.
Still, last-minute stuff can and will happen. Working sound at my church recently, I noticed on the worship order that a missions report had been scheduled, and it would be delivered by someone we weren’t outfitted with a headset/lavalier mic. This was 10 minutes before the service.
So I walked up to the stage and quickly arranged for one of the vocalists, at the appropriate time, to hand off her vocal mic to the person delivering the report, and then to collect it when he was done. Nothing genius, but a last-minute solution that worked smoothly and well. When the time came, I was ready to quickly adjust that particular mic channel to adjust for the new person’s particular voice and mic handling.
4) Plan ahead, and always have a “plan B.” Normally the above scenario would not have been an issue because we always keep a spare “just in case” handheld mic on a stand on the stage (discretely out of the way). But at this particular point in the service, it was already going to be used by someone else on the worship team.
5) Have a party! (You didn’t see that one coming, did you?) Once every few months or so, the entire tech team should get together to go through all of the equipment, making sure it’s all there, working properly, and organized. It really helps to make this a fun, festive event, with pizza and cold drinks and some time for everyone to “just hang.”
Keep these five things in mind, and you’ll see a dramatic improvement in consistency from service to service.