Broadcasting, Featured House of Worship
Anyone with more than one kid knows life doesn't get busier by addition, it multiplies. Tech pastors running more than one campus know the same thing. One campus can already get complicated. Five to ten is an entirely different job.
This post is for anyone juggling multiple satellite locations. Your problems look different from a single-site tech pastor's, and your fixes need to work from miles away, as if you were standing in the room.
Here's a practical list of the audio problems that show up most across multi-campus churches, and the fix for each one. Let's get into it.
Audio Quality That Doesn’t Always Travel
Last Minute Volunteer Cancellations
You Need to Take a Break, Sometimes
Great Variety in Various Sites
Audio That’s Not NSYNC
Final Thoughts
Your mix leaves your main campus sounding great and arrives at your other campuses sounding like a fast food drive-thru speaker. You spent the week getting the broadcast mix right, and at campus three, it sounds like someone threw a blanket over it.
The problem: Audio traveling alongside your video stream gets encoded, usually to AAC at whatever bitrate the workflow defaults to. That's lossy compression: fine for a talking head, but not always good enough for a full band and a room of people expecting the mix to feel like it does at your main campus. In other words, you’ll probably feel this pain point more if your worship feed is included in what you send to your satellite campus.
The impact: You lose high frequency detail first, then stereo image, then intelligibility. Cymbals turn to hiss, the low mids smear together, and consonants get soft in exactly the sermon moments where clarity matters most.
The fix: Start with the cheapest lever: bitrate. Find out what your audio is actually encoded at, and raise it if there's headroom. Then check whether your transport protects packets or just drops them; a protocol like SRT or BoxCast Flow uses error correction to recover lost data instead of letting it fall on the floor, which matters more than people realize on a Sunday morning network.
If you want genuinely uncompressed audio between buildings, that means Dante over a properly managed network, and it's worth being honest: that's a bigger infrastructure project, not a quick checkbox.
10 p.m. Saturday night texts aren't fun for tech directors. Polite and apologetic or not, your best volunteer just dropped out for tomorrow morning, and now you're scrambling to reach a backup. At a satellite location, that gets even trickier.
The problem: Satellite campuses usually run on a thin bench in the audio world: one volunteer who knows the board, and a backup who's watched them do it a few times.
The impact: Multisite churches depend on audio and video being reliable, and a service twelve hours away with nobody to run sound puts a sub-par experience in front of hundreds, maybe thousands, of attendees.
The fix: Remote in and mix it from wherever you are.
This is the single biggest change multi-campus audio has seen in the last few years. Somebody at the campus still needs to power things up and get mics on the right people, a job you can teach in an afternoon; the mixing itself no longer requires a body in the room.
That turns a staffing emergency into a scheduling note. Your Saturday night text goes from "we have a problem" to "no worries, I've got it."
Your best audio person is on a beach, and unfortunately, everybody can hear it. Good tech staff are supposed to take vacation and get sick occasionally, same as anyone else.
The problem: Your most experienced operator can't cover 52 weeks a year, and nobody should ask them to. But when they're out, their skill often goes with them, and it's hard to hand that off to whoever's next in the batting order.
The impact: Keeping quality consistent gets hard. Worse, small problems your veteran would fix in 30 seconds turn into service-long problems, because whoever's in the seat doesn't know it's fixable, or how.
The fix: Build remote access into your workflow, so your next-best mixer can take full control, no matter which campus they're at.
You can go further and give your most experienced person full access to every location on a given weekend, so they can drop in wherever trouble comes up. That doesn't mean running every campus the whole service, just long enough to fix the problem and hand control back.
The same mix played in five rooms can produce five different outcomes. A broadcast suite, a 900-seat auditorium, a movie theater, and a portable rig in a middle school cafeteria are four different acoustic problems, and no single mix solves all of them.
The problem: Room dimensions, wall treatment, ceiling height, and PA design vary wildly between campuses. A mix built for one room does not always translate to another.
The impact: What sounds dialed in at the broadcast location shows up muddy at one campus and harsh at another. And it's not a mistake anyone made, it's just physics.
The fix: This fix has two parts, and the second one is the one that usually gets skipped.
First, send a neutral mix rather than a finished one, something reasonably flat and easy to adjust, so the campus that needs less low end can take some out without fighting decisions baked in 20 miles away. Pair that with the ability to hop in remotely when a volunteer gets stuck, since "make this sound less boomy" is much easier to do than to explain over the phone.
Second, standardize the parts that actually matter. This is where mismatched gear quietly drives up your ticket volume. When every campus runs a different console, a different mic locker, and a different channel order, every problem is a brand-new problem, and neither you nor your volunteers can build a fix once and reuse it.
You don't need identical rooms, and you won't get them. You need identical logic. Sticking with the same console family helps, since matching channel numbering, naming, and starting scenes remove the guesswork. Then a remote operator opening campus four already knows where everything lives, and the only thing left to solve is the room.
Standardizing gear is also the cheapest performance upgrade most churches have available, and it usually doesn't require new purchases. If that's you, we've written a whole piece on getting more out of the gear you've already got.
When lips and words stop agreeing, it's tearing up my heart, and plenty of attendees will be ready to say bye, bye, bye. (Yes, I'm a Millennial. It was always gonna be me.)
But seriously: nothing empties a room's attention faster than a bad audio experience. It's close, but out-of-sync audio and video will frustrate viewers even more than a picture that suddenly drops to standard-definition quality.
The problem: Video takes longer to process and encode than audio does. Whether this is happening locally or with your streaming service, if those paths aren't kept aligned end to end, they arrive out of step.
The impact: The speaker's mouth doesn't match the speaker's voice, and everything else you did well that morning stops mattering. Congregations have effectively zero tolerance for this.
The fix: Be honest with yourself about whether this is a one-off or a pattern.
A one-off usually traces back to a specific device or setting, and you can chase it down. A recurring pattern points to a platform problem, and that's not something to manage around every week.
What you're looking for is a delivery path that handles packet loss without breaking sync. That means retransmitting lost data and reassembling it in the correct order rather than skipping ahead, plus keeping audio and video locked together across the whole chain, not just at the encoder. There are even devices and switchers that will add a slight delay to your audio so it matches up with your video perfectly, so you have options here.
Multi-campus streaming conversations tend to be entirely, or at least mostly, about video: resolution, bandwidth, uptime, failover. All of that matters, and it's often what people complain about on the drive home.
But they'll complain about audio more. Often, audio at scale isn't really a gear question: it's a question of whether the right person can get their hands on the right board at the right moment. Notice how many of the fixes above land in the same place: remote access, someone who isn't in the room, logging in and solving it in minutes, or even seconds.
Driving between campuses on a Sunday morning to troubleshoot doesn't work. Even when the timing lines up, you've just pulled your most skilled person away from your sending site, the one place you genuinely can't afford a problem. You solved campus four by putting campus one, and everything it supports, at risk.
Remote audio mixing is still newer technology, and plenty of teams haven't worked it into how they operate. For multi-campus churches, we'd argue it's already essential.
It's also why we describe BoxCast as a live production platform, not just a streaming company. Streaming is the delivery; production is everything you need to get right before and after it. That's why we built Mixing Station Anywhere. We work with thousands of churches, and we saw that giving remote audio control to ministries, especially multi-site ones, solved problems traditional methods couldn't touch.
If the problems, and more importantly, the solutions, in this article sound familiar, it's worth taking a few minutes to see how Mixing Station Anywhere could change how your multisite ministry runs.
