What causes latency when synchronizing church slides across multiple campuses?

Slide latency between campuses occurs because live video streams and slide commands travel across separate network pipelines with different processing speeds. While standard video streaming protocols like RTMP or HLS introduce 5 to 30 seconds of encoding and distribution delay, slide control commands transmit over IP networks in milliseconds, creating a noticeable visual mismatch if not deliberately buffered.

What is the best protocol for sending slide triggers to remote satellite church campuses?

Open Sound Control (OSC) and MIDI over IP (RTP-MIDI) routed through encrypted mesh networks like Tailscale are the most reliable protocols for remote slide triggering. These protocols transmit lightweight command packets of less than 1 kilobyte per transition, offering sub-100-millisecond transmission speeds across standard internet connections.

Should satellite church campuses render slides locally or receive them as a video feed?

Satellite campuses should render slides locally on dedicated presentation computers rather than receiving them as a video stream. Local rendering reduces internet bandwidth requirements, avoids video compression artifacts, and allows satellite venues to customize slide formatting, aspect ratios, and stage confidence monitors to match their specific room layout.

How do church technical directors align remote slide transitions with delayed video feeds?

Church technical directors synchronize slide transitions by routing video over Secure Reliable Transport (SRT) to establish a predictable 1-to-2 second latency, and then applying an equivalent software delay buffer to incoming slide control triggers using automation tools like Bitfocus Companion before sending the cue to the local presentation software.

← Blog

How to Sync Church Slide Displays Across Multiple Campuses Without High Latency

August 17, 2026

TL;DR

Multisite churches achieve low-latency slide synchronization across campuses by running presentation software locally at each venue and transmitting lightweight control protocols—such as MIDI over IP, OSC, or WebSockets—over secure virtual private networks. By pairing local slide rendering with calibrated delay buffers that match low-latency SRT video streams, church AV teams keep scripture passages and sermon slides perfectly synchronized with the preaching pastor.

Running a multisite church requires delivering a unified worship experience across every campus, but video lag and slide delays frequently break the illusion of real-time connection. When a teaching pastor at the broadcast campus quotes a scripture or advances a sermon point, satellite campuses often experience awkward multi-second delays between the live speaker feed and the accompanying visual slides.

Achieving seamless slide synchronization across remote locations does not require enterprise-grade broadcast budgets. By replacing inefficient video-rendered slide feeds with lightweight network trigger protocols and calibrated latency buffers, technical directors can keep visual presentations perfectly aligned across every satellite sanctuary.

The Real Cause of Multi-Campus Slide Desynchronization

Slide desynchronization occurs primarily because presentation software commands and live video streams travel over separate delivery pipelines with drastically different latency profiles. Standard RTMP (Real-Time Messaging Protocol) and HLS (HTTP Live Streaming) video delivery platforms introduce between 5 and 30 seconds of inherent encoding, distribution, and decoding delay. If a slide trigger executes instantly over a local network or cloud database while the broadcast video lags by 15 seconds, remote attendees see slide points long before the pastor speaks the words.

Conversely, sending slides as a pre-mixed video overlay inside the main camera stream eliminates remote display customization. Baking slides into the video feed prevents satellite campuses from formatting lyrics to fit unique aspect ratios, adjusting text size for smaller auditoriums, or using native stage confidence monitors.

Method 1: Local Slide Rendering via Lightweight Control Protocols

Local slide rendering is the most bandwidth-efficient method for multisite church synchronization. In this architecture, each satellite campus runs its own presentation machine hosting identical slide decks, Bible databases, and lyric libraries.

Instead of streaming high-bandwidth graphic video feeds across the internet, the broadcast campus transmits lightweight command payloads to trigger slide advances on remote machines. These control signals require less than 1 kilobyte of data per transition.

Technical teams deploy three primary protocols for remote triggering:

OSC (Open Sound Control): A network protocol that sends detailed text and numeric arguments over UDP (User Datagram Protocol), allowing precise slide targeting by slide index and bank name.
MIDI over IP (RTP-MIDI): A standardized protocol that translates slide cues into musical note-on and control change commands transmitted across virtual private networks.
WebSocket / REST APIs: Presentation platforms like ProPresenter and modern cloud presentation tools support HTTP/WebSocket API calls to trigger specific slides directly across network endpoints.

To bridge local networks securely between campuses, AV engineers use software-defined mesh networks such as Tailscale or WireGuard. These tools create encrypted peer-to-peer tunnels without requiring complex firewall port forwarding on campus routers.

Method 2: Calibrating Trigger Buffers to Match SRT Video Latency

For multisite congregations streaming live sermons from a central hub, Secure Reliable Transport (SRT) has replaced RTMP as the broadcast standard. SRT delivers broadcast-quality 1080p60 video over the public internet with predictable, end-to-end latency between 500 milliseconds and 2.5 seconds.

Because the video feed arrives with a fixed latency, slide triggers sent over direct network protocols must be artificially delayed at the remote site to match the video buffer.

Church technical teams calibrate this synchronization using control software such as Bitfocus Companion or broadcast automation controllers. When the broadcast campus operator triggers a slide advance:

The control command reaches the satellite campus network in 30 to 80 milliseconds.
The satellite automation controller holds the incoming command in a time-delay buffer equal to the measured SRT video decoding latency (e.g., 1,450 milliseconds).
The automation controller releases the trigger to the local presentation software at the exact millisecond the corresponding video frame renders on the sanctuary screens.

Calibrating slide trigger buffers to match SRT video decode latency eliminates visual spoilers and ensures scripture overlays appear in lockstep with the preacher's voice.

Method 3: Cloud-Synchronized and Timecode-Driven Engines

Modern presentation systems increasingly utilize network timecode synchronization (SMPTE LTC or MIDI Timecode) embedded directly within the broadcast stream. When the broadcast video feed carries embedded timecode metadata, the satellite presentation software reads the stream's presentation timestamp (PTS) and fires pre-programmed slide markers automatically.

Additionally, cloud-native worship software platforms synchronize global service rundowns across campuses in real time. These systems distribute presentation assets before the service begins, ensuring that remote campuses only exchange lightweight sync markers during live production rather than streaming heavy media files on Sunday morning.

Ensuring Failover Security for Satellite Services

Network disruptions on Sunday morning can isolate a satellite campus from the central broadcast hub. A robust multisite AV infrastructure must include local manual override capabilities.

Satellite AV operators should always have a physical control interface—such as a stream deck or MIDI controller—configured to instantly switch the presentation machine from remote listening mode to local operator mode. If an internet outage disconnects the remote trigger stream, the local volunteer can continue advancing sermon points and scripture passages without interrupting the service.

Unifying the Multisite Worship Experience

Multi-campus slide synchronization succeeds when technical teams separate visual rendering from trigger transmission. By running presentation software locally at each campus, securing low-latency network tunnels, and tuning trigger buffers to match low-latency SRT video pipelines, multisite churches can eliminate awkward slide lag and provide an immersive, distraction-free worship experience across every campus location.