Skip to content
LogosPilot
Request private preview

LogosPilot for religious broadcasting

The most technical audience on this site, and the one where the boundary matters most. LogosPilot coordinates your production software. It does not replace any part of it.

The environment

A broadcast team already owns the hard parts — encoding, switching, routing, monitoring. What they usually do not have is a reliable way to get Scripture on the program feed at the moment it is spoken.

That is the gap LogosPilot fills, and it is the only gap it claims to fill.

Certification here means something specific. Both vendors were tested at named versions, running simultaneously, on one machine — with rendering confirmed on pixels by window capture rather than by an API reporting success.

The full certification scope, including the five cases that were not performed, is published.

Relevant workflows

One workflow dominates here, and everything else supports it.

Workflows that matter most here
WorkflowWhat it does here
Service with broadcastProgram content is delivered to your production software. If that connection drops, the local presentation continues unaffected and the failure is reported to the operator, not the audience
Service with recordingIndependent audio capture, finalized with a checksum, alongside whatever your production chain records
Manual presentationDirect operator control of the display path when automation is not wanted

Applicable capabilities

These are the same capabilities every LogosPilot install has. Nothing below is specific to this environment — only the emphasis is. The capability list is defined here.

  • Certified broadcast integration. OBS Studio and vMix at the exact versions below, tested end to end.
  • Multi-display output. Congregation, stage, confidence and a livestream-facing output can each carry independent content.
  • Independent failure. A broadcast integration failure does not affect the room. Each subsystem fails alone.
  • Audio recording. Captured with markers and a timeline, finalized with a checksum.

Certified integrations

These are the certified versions. Certified means tested at that version, end to end — not compatible, not supported.

Certified vendors and versions
VendorVersionProtocolTransport
OBS Studio32.1.2obs-websocket 5.7.3WebSocket 4455
vMix29.0.0.48—TCP 8099

21 of 21 certification cases passed

See what certification covered, and what it did not

What LogosPilot does not do

This audience will check these claims, so they are stated precisely. Every item below is a deliberate boundary, not a missing feature.

LogosPilot drives your production software. It does not replace it.

It is not an encoder, not a production switcher, and not a broadcast automation system. It does not do playout scheduling. Encoding, switching and streaming stay in the software your team already runs.

LogosPilot is not a routing platform.

It does not route video between devices, manage an NDI fabric, or act as a matrix. Content is delivered to a configured output; routing is your infrastructure.

LogosPilot records your service. Editing happens in your editor.

Recordings are captured with markers and a timeline so they are ready to work with, and finalized with a checksum. LogosPilot hands you the file; it does not edit it.

LogosPilot controls what is displayed, not what is filmed.

Camera movement, switching and PTZ control remain with your production team and their equipment.

LogosPilot is a Windows application.

It runs on a machine in your production chain, not in a browser.

Read all ten boundaries

Where to go next

Related

Test it against your own production chain

The 30-day trial includes both certified integrations. Connect it to the software you already run before committing to anything.

Request private preview View system requirements