Keys to a Quality Sound Check

The service did not go well. The lead tech was disappointed that there were so many issues with the band. As he began to explain the problems, I asked questions about the sound check and it quickly became very clear that this was the primary issue. The tech’s response was, “But the band lines never change, why would we have to check them?”

The second law of thermodynamics essentially states that there’s a natural tendency of any isolated system to degenerate into a more disordered state. While this scientific statement was not written for churches or tech, it still holds true in the church world. We must realize that our systems, even sitting untouched, will have issues.

I then asked if the tech team had a written flow of their sound check or a checklist that described to the entire team – including the worship team – what needs to be checked. After thinking a moment, the tech asked an insightful question: “How do I take our good sound check to the next level so that it sets us up for success?”

I picked up on two key words in that statement that led me to realize this was a solid team. The words “good” and “us.” A quality pre-service check requires a team effort. I knew I was working with tech that wanted to get better. With that in mind, here are five things I used to help improve this church’s sound check.

1. Get ahead of the game.

The first tenant of a quality sound check is a pre-line check. This takes two or three people. The goal is to test everything before the worship team arrives. Best case is to have someone at front of house, another person on the stage and, if applicable, a third person listening to the worship team’s monitoring systems.

Depending on your specific setup, you may need more or less people. For example, I’ve seen churches put a DiGiGo console and KLANG in-ear monitoring system at front of house that also allows them to do monitoring checks. I’ve also seen tablets implemented to allow the mix engineer to test lines while on stage.

Whatever the situation, have someone check every line, starting with channel one on the console. Listen for signal on every channel. For vocals and band instruments that have microphones, physically hear them through the system. It’s best to test direct boxes with the actual instrument or playback, but at minimum, tap the 1/4 inch connector with your finger and hear the signal buzz at front of the house. Be sure to check video playback lines as well.

Speaking of video, it’s good practice to check all the video switcher inputs and outputs during this process. Start at input one on the switcher and run the same process that audio does, see every camera and output work. Verify the screens and projectors are receiving the correct signal.

2. Check everything with the worship team.

When the worship team arrives, make sure they’re aware of the practice structure. This structure should be known, and there should be a designated person to run the first part of this practice. Typically, this is a tech that steps the worship team through each check; most often, it’s the front of house engineer.

As with the pre-line check, this person calls out (usually over a mic linked to the stage monitors) who needs to play next. The goal is to be able to quickly hear each line and make sure the worship team is good with its monitors.

Best practice is to have the drummer start by doing each individual drum and then allowing enough time to test the settings for the rest of the team. Also have the drummer continue to play while you check every other vocal and instrument. This helps ensure everyone is hearing at the levels they need.

If there’s an issue, the drummer may have to stop until it’s resolved and then the drummer can start playing again. If you do this right, it almost sounds like a jam session with a solo listen of each vocal and instrument.

Once the initial worship team check is done, the front of house engineer should find out who is singing which part for each song. Write this down. Part blending is important. Do a quick acapella check of the vocals, allowing the FOH engineer to quickly EQ each vocal and do a quick blend check. Many worship leaders like to do an acapella check before or after rehearsing each song, and if that’s the case, you can skip this step.

3. Rehearse with the worship team.

Hand things over to the worship leader to start the team’s rehearsal. It’s important for techs to rehearse with the team – I’ve seen many who disengage at this point. Be a part of the rehearsal. Listen to what’s going on and be active in solutions.

The worship team should rehearse each entire song, and at some point, they should also rehearse the transitions between songs. I encourage worship leaders to always simulate “the real thing” to the best of their ability. If someone is going to speak between songs, note that during the rehearsal, and if possible, practice it.

This means that when you move on to song two, rehearse the ending of song one, followed by the transition and then start into song two. It gives everyone in the room the opportunity to hear things will flow. If someone isn’t at the rehearsal, the worship leader should talk through

how that part will work, and again, techs should always listen and take notes.

4. Go through everything.

Try to block enough time the day of the service to do a complete run through of the first part of it. This is a non stop actual run of every portion up until the pastor gets on the platform.

If possible, set a time for when the pastor can make the transition to the platform, rehearses it, does a mic check, and then talks through with the team any curve balls that may come up during the sermon. This is also a great time to double check any images or illustrations they may want to show and also to get a heads up on any end of sermon cues.

5. Take time to breathe.

Plan for down time – end all rehearsals, checks and run throughs 30 to 45 minutes before before the service begins. Many churches have a quick meeting (10 minutes maximum) during this time to make sure everyone is on the same page. While I recommend this meeting, it can’t turn into a 30 minute work session. The goal should be to tie up any high level questions, calm nerves and pray for the upcoming service.

I’m regularly asked if sound check can be held on a different day than the service. While it’s best to do all of it on the same day, splitting it up into multiple days can still work. That said, if at all possible, try to do a full run through on the day of.

Remember that technical gear is also an instrument of worship. I don’t see any difference between a mixing console and a guitar or vocalist. Techs need just as much testing, playing and practice as the worship team does. I understand it seems like a lot of work for a volunteer, but know that the plans of the diligent, caring and conscientious worker will lead to an advantage.

Or as scripture puts it, “The plans of a hard working person leads to prosperity...” Proverbs 21:5 (God’s Word Version)

Original Article appears at Church Sound Magazine

Article written by David Leuschner

Previous
Previous

LED Walls | Episode 12 | The Tech Arts Podcast

Next
Next

Wireless DMX