How does worship presentation software communicate with stage lighting consoles?

Worship presentation software communicates with stage lighting consoles across local area networks or virtual MIDI bridges using protocols such as Open Sound Control (OSC) or MIDI. When an operator advances to a configured slide, the presentation software sends an outbound command that instructs the lighting console to trigger a specific cue or preset.

Which communication protocol is better for church lighting automation: MIDI or OSC?

Open Sound Control (OSC) is generally superior to MIDI because OSC transmits human-readable text commands over standard Ethernet networks and does not require manual channel or note-number tracking. However, MIDI remains widely compatible with legacy lighting boards and hardware controllers.

What happens if a worship leader skips a slide or changes the song order?

When an operator clicks a slide out of order, the presentation software instantly sends the cue mapped to that specific slide, causing the lighting console to shift directly to that scene. Setting up crossfade transition times between 1.5 and 3 seconds in the lighting software prevents sudden, jarring visual cuts when spontaneous slide jumps occur.

Can small churches automate stage lighting without expensive hardware consoles?

Yes, small churches can achieve full stage lighting automation using software-based lighting controllers such as Lightkey, QLC+, or D-Pro paired with an affordable USB-to-DMX interface. These software tools run on standard computers and accept MIDI or OSC commands directly over the local network.

← Blog

How to Automatically Trigger Stage Lighting Cues Based on Worship Lyric Changes

August 16, 2026

TL;DR

Churches can automate stage lighting cues by sending MIDI or Open Sound Control (OSC) network signals directly from worship presentation software during lyric slide changes. Attaching lighting commands to the first slide of each song section allows dynamic scene changes without requiring a dedicated lighting console operator. This setup streamlines AV workflows, reduces volunteer workload, and ensures visual cues align perfectly with musical dynamics.

Synchronizing stage lighting with worship music creates an immersive environment that helps congregations engage with every lyric and musical dynamic. However, smaller production teams often lack the personnel to assign a dedicated volunteer to both the presentation computer and the lighting console.

By establishing automated communication between church presentation software and stage lighting controllers, AV teams can trigger dynamic lighting scenes directly from lyric slide transitions. This guide outlines the essential protocols, hardware setups, and step-by-step workflows required to automate stage lighting cues reliably during Sunday services.

Why Automate Stage Lighting with Lyric Slides?

Manually firing lighting cues requires intense focus, precise timing, and thorough familiarity with every song arrangement. When volunteer resources are limited, lighting transitions frequently lag behind the music, creating visual disconnects during key moments of worship.

Automating lighting changes directly from lyric slides solves several operational challenges:

Eliminates Volunteer Strain: A single AV volunteer running projection can simultaneously control lyrics, background video, and stage lighting states.
Guarantees Perfect Timing: Lighting scenes shift precisely when the slide changes, ensuring high-energy chorus looks and subdued verse looks fire on the exact beat.
Reduces Service Distractions: Visual transitions remain smooth and predictable, preventing missed cues or incorrect color palettes during live ministry.

Understanding the Protocols: MIDI vs. OSC

Worship presentation software does not directly output DMX signals to lighting fixtures. Instead, presentation software sends control commands to a dedicated lighting console or software controller, which then outputs DMX, Art-Net, or sACN to the stage fixtures.

Two primary protocols handle this communication across church production systems:

1. MIDI (Musical Instrument Digital Interface)

MIDI has served as the production industry standard for decades. Presentation software sends MIDI Note On or MIDI Control Change (CC) messages across USB interfaces, standard 5-pin DIN cables, or local networks via Network MIDI (rtpMIDI on Windows or the native Apple MIDI Network Setup on macOS). MIDI values range from 0 to 127, requiring users to map specific slide actions to numerical note triggers.

2. OSC (Open Sound Control)

Open Sound Control is a modern, network-based protocol that sends human-readable text commands over standard Ethernet or Wi-Fi connections via UDP. OSC commands look like URL paths (for example, /lighting/cue/chorus/go). OSC offers higher speed, greater flexibility, and simpler troubleshooting than MIDI because the command strings clearly describe the target action.

Step-by-Step: Connecting Presentation Software to Lighting

Connecting presentation software to a lighting console involves three key stages: network configuration, software pairing, and slide cue mapping.

Step 1: Establish a Shared Network Connection

Ensure that the presentation computer and the lighting controller (such as Lightkey, Vista by Chroma-Q, GrandMA, ChamSys, or ETC Nomad) reside on the same local area network (LAN). Hardwired Gigabit Ethernet connections are strongly recommended over Wi-Fi to eliminate packet drops and latency during live services.

Step 2: Configure Inbound and Outbound Ports

In your presentation software settings, navigate to the communications or network triggers menu:

Select OSC or MIDI as your output device.
Enter the target IP address of the lighting computer.
Configure matching outbound and inbound port numbers (default OSC ports commonly use 8000, 53000, or 9000 depending on the lighting software).

Step 3: Map Lighting Cues to Song Sections

Rather than attaching a lighting trigger to every individual lyric slide, attach cues only to the first slide of distinct musical sections (e.g., Verse 1, Chorus, Bridge, Instrumentals, and Sermon Transition).

In your presentation software, right-click the first slide of a song section (such as the Chorus).
Select Add Action or Add Communication Trigger.
Choose your configured lighting connection.
Define the command (e.g., MIDI Note 60 on Channel 1, or OSC command /cue/chorus/activate).
In your lighting software, set the corresponding cue or preset to listen for that specific MIDI note or OSC string.

Best Practices for Slide-Driven Stage Lighting

Automating your lighting system creates enormous efficiency, but proper programming safeguards your service from abrupt or jarring visual shifts.

Program Gradual Fade Times: Ensure your lighting software applies a 1.5 to 3-second crossfade transition between presets. If an operator advances a slide slightly early, a gentle crossfade prevents a harsh visual flash.
Use Generic Default Cues: Program universal lighting looks (e.g., "Worship Warm Wash" and "Speaker Walk-Up") that can be recalled from standard macro buttons in case a song deviates from the planned arrangement.
Separate House Lights from Lyric Automation: Keep ambient house lighting and broadcast key lights on independent, manual faders so lyric slide misclicks never alter congregation visibility or camera exposure.

Streamline Your Worship Production

Automating stage lighting via lyric changes bridges the gap between high-end visual production and small volunteer teams. By allowing your presentation software to handle routine cue execution, your production team can maintain a distraction-free, beautifully lit worship service week after week.