If your church streams, you probably already live in OBS, vMix, or a similar switcher. Worship Manager can send its output over NDI so lyrics, Scripture, and media show up as a network video source — no HDMI loop or window capture required.
NDI (Network Device Interface) shares video across your LAN. With Worship Manager’s NDI output active, your streaming PC can add that source next to cameras and lower thirds.
Typical setup:
Use Stop when the stream ends, and Refresh if status looks stale.
The status panel also shows useful diagnostics: SDK version, sender/source name, resolution, frame rate, connections, and any last error. That is the first place to look if OBS cannot see the feed.
Exact menus vary by OBS version and NDI plugin, but the flow is:
vMix and other NDI-aware tools follow the same idea: add an NDI input and pick the Worship Manager source.
You can run the local PRESENT display for the sanctuary projectors and NDI for the stream at the same time. Operators still work from Preview / Program as usual — NDI mirrors the display content your stream needs.
If NDI fails to start (for example the NDI runtime is missing), Worship Manager surfaces a warning instead of crashing. Install/fix NDI support on that machine, then Start again from Settings.
| Use NDI when… | Prefer a local display when… |
|---|---|
| You mix Worship Manager into a stream program | You only drive sanctuary projectors |
| You want clean frames without capturing a window | You need the simplest possible Sunday setup |
| Multiple destinations need the same output | One machine / one screen is enough |
NDI turns Worship Manager from “the projector app” into a proper source in your production graph — same lyrics the room sees, ready for the stream.