We're all about LDI (or as we call it LEDI) this week. We talk about the cool new products we saw at the show. But don't despair if you're not a lighting guy—they weren't all lighting products!
Several years ago, my friend Dave posted a tweet about a few of the things he did during a service. It went something like this: “Push up the snare for the open. Duck the hat down for the verse. Push the guitar for the bridge. Drums up for the breakdown. It’s called mixing.” I’m paraphrasing and don’t remember any of the exact phrases except for the end one, "It’s called mixing." I’m probably going to sound like an old guy here, but I sometimes fear we are losing the art of mixing. I see a lot of younger guys spending a lot of time tweaking all the plugins in the virtual rack instead of building and maintaining a great mix. In my day, I may not have walked uphill both ways to school in the snow, but we did actually have to plug in our plugins. And we were lucky if we had a couple of them.
More than Effects
Mixing is so much more than stacking up virtual vintage compressors, EQs and tubes on every channel. Sure, those things are nice and I enjoy having a virtual rack full of compressors of many variations available when I mix. But those things are the icing on the cake, not the cake itself. If we don’t get things like gain structure and overall musical blend right from the start, plugins only make a bad situation worse. Expecting our plugins to mix for us is a little bit like expecting FinalCut Pro to edit a video for us.
More than Set and Forget
I’ve watched more than one sound guy push the faders up, make some minor adjustments to the gain and EQ then stand there with their hands on the wrist rest, watching the service. They totally missed opportunities to add some dimension by pushing up the guitar between vocal phrases, or highlight a cool bass riff, or pop the drums out during a bridge. I’ve heard the lead vocal go from too quiet to too loud because they wouldn’t touch the fader. That’s not mixing; that’s guarding the console.
More than The Sound Guy
I’ve long said that the guy or gal behind the mixer is every bit a part of the band. We can enhance the arrangement, add dynamics and make a mediocre band sound pretty good. By carefully crafting a mix then staying with it as the song unfolds, we have the opportunity to play our instrument in concert with the band. This is just one reason why sound engineers should know the music. When you know what’s coming up, you can prepare for it and make it better. Even when mixing unfamiliar material, having a working knowledge of music theory is most helpful.
I got to thinking about this a few weeks ago when I found myself mixing for the Night of Illumination event in Nashville. Brady Toops was the artist, and while I’ve heard his music before, I’m not very familiar. The system was an old JBL club series PA and a Yamaha MG24. Not the best system I’ve worked on. With no compression and nothing but on-board effects, it was a lot of work. But it was fun! And by all accounts, it sounded great. Brady and his guitar player are great musicians, and starting with good source material is always welcome. And while the input count was low, I rarely stopped moving my hands.
Without compressors, I had to resort to an ancient technique—manually riding the vocal. I also rode both guitars and pushed the foot actuated tambourine thing up and down as needed. It was honestly some of the most fun I’ve had mixing in a long while.
It’s easy to get into a mode where we rely on all our fancy digital tools to do most of the work for us. But I challenge you to turn off the plugins and just mix for a few weekends. Or at least pull up some tracks and try it. Getting back to the basics of building and maintaining a solid mix without assists will make you a better engineer. Then the plugins really do become the icing on the cake.
The other day I was involved in a conversation in which someone said, “If someone leaves because it’s too loud, we haven’t done our job properly.” Now, I’ve heard this philosophy espoused on more than one occasion, and you probably have, too. It’s a commonly held concept that as tech people we should be invisible and no one should really notice we’re there. And I agree with that, at least in principle. We don’t want to call attention to ourselves, or the technology; we want to call attention to Jesus. I’m on board with that.
However, does that really mean that if someone leaves because it’s too loud—for them—that we’ve failed? I’m not sure I buy into that concept.
We have to establish our philosophy of worship; and that includes volume. I get so sick of the endless volume debate, and especially pastors throwing their tech guys under the bus because it’s too loud; especially when those same pastors have never established an explainable philosophy of worship. And by explainable, I mean that someone could explain it to a mad congregant who thinks it’s too loud.
Pastors, if you’ve never sat down with your music and tech teams and established a good set of guidelines for how loud worship should be, you have no right to complain about the volume or send angry people back to the tech booth to complain. And by the way, this policy should be written down. And it shouldn’t be a single number; e.g.. “Worship shall be no louder than 90 dB.” You have a lot more work to do if you think that’s all it is.
Some congregations like it loud; and that’s OK. It’s also OK if some people are bothered by that. I know some churches who believe that during musical worship, they are celebrating the work God has done on earth through Jesus, and that celebration should be loud. To that I say, Amen! Now, there are other churches who prefer a more subtle, laid back and contemplative approach to worship, with more space for quiet and silence. To that I say, Amen!
I honestly have no problem with either approach, and I enjoy both at times. What I do have a problem with is a person who prefers quiet worship going to a church that worships loud and complains the whole time. Just because someone doesn’t like a particular expression of worship doesn’t mean it’s wrong, or that the tech guys have failed.
You really can’t please everybody and it’s foolish to try. If your philosophy of worship is to not offend anyone, you will either end up offending everyone, or just doing a really poor job. It’s much like a football team that is playing to not lose; they rarely win. You have to decide who you want to be as a church and go all in with it. To do anything less is to squander the gift of uniqueness that God has given your congregation.
Figuring out who you are as a church takes a lot of work and prayer, but the payoff is so worth it. When people know what you stand for, they will lock arms with you and work tirelessly to advance the cause. But when you are wishy-washy and can’t articulate why you do what you do, people will come and go without any real buy in. Figure out who you are, and own it.
Well, at this point, I’ve probably offended more than a few people. But that’s OK. You can’t please everyone…