Signal, not spectacle: my approach to live production
The tech should be invisible. If people notice it, it has already failed at its job. Here's how I keep the stream out of the way of the message.
When I first started running live streams for worship and events, I made the classic mistake: I treated the broadcast like a TV show. Cameras everywhere, graphics flying in, transitions on every cut. It looked impressive for about ten seconds — and then it got in the way.
The principle
The goal of a stream is never the stream. It's the clarity of what's being carried. Audio that's intelligible. A frame that's lit. A cut that happens when it should, not when it looks cool. I call this 'signal, not spectacle' — and it now governs every setup I build.
What that looks like in OBS
- One primary programme scene, not twelve.
- Audio routed and gain-staged before the service, not during it.
- A volunteer-proof run sheet so the person on the console isn't an engineer.
Why it matters
Most church and creator tech breaks under pressure because it was built for the demo, not the Sunday. Build for the volunteer at 9am on no sleep, and the signal takes care of itself.