Remote & API
Remote control and integrations
Run the show from a phone, Bitfocus Companion, a Stream Deck, MIDI or your own scripts.
Anyone on the church WiFi can run the show from a phone, and software such as Bitfocus Companion, a Stream Deck or your own scripts can control it. Nothing can connect until you turn it on.
Turning it on
Open Settings → Remote & sync (Ctrl+Shift+R) and turn it On. The page shows:
- a QR code and the address to open, such as
http://192.168.1.20:7380/. The phone must be on the same network as this computer. - the PIN. Every phone, tablet or program needs it once. New PIN makes another; devices already paired stay paired.
The first time, Windows may ask whether to allow Neopresenter on private networks: allow it. Every paired device is listed there, and Remove disconnects one at once.
The phone remote
Scan the QR code (it fills in the PIN), or open the address and type the PIN. Add it to the home screen to open it like an app. Its tabs:
- Control: big Next and Previous buttons, Logo, Black, Clear, the service list and messages to the stage.
- Stage: the current and next slide, the clock and timers.
- Lyrics: just the words, as large as fit.
- Chords: the words with chords, in the band's key, with transpose for a capo.
- Setlist: the service's songs for the band, each with its key and whole chart.
- Captions: live captions of the sermon, each phone in its own language.
Companion and Stream Deck
- Bitfocus Companion: add the Neopresenter module and type this computer's address and the PIN. Buttons light up with the live state. Companion's Generic TCP module works too, with the commands below.
- Stream Deck: install the Neopresenter plugin, set the address and PIN once, then drag keys such as Next, Previous, Go Live, Logo and Black onto the deck.
MIDI cues
Open Settings → MIDI (Ctrl+Shift+M) to let a playback rig, Ableton Live, a keyboard or a foot switch run the slides. + Cue listens for the next key, pad or button; then choose what it runs, such as Next slide, Preview to Live, Logo or Black. Neopresenter can also send MIDI to cue a lighting desk.
The local API
Neopresenter can be controlled from your own scripts on the same network:
- REST:
http://<computer>:7380/api/v1/…for one-off actions and reading state. - WebSocket:
ws://<computer>:7380/api/v1/wsfor live state pushed on every change. - TCP:
<computer>:7382, one command per line, for hardware controllers.
Pairing. Every request needs a token. Get one by pairing with the PIN:
POST /api/v1/pair
Content-Type: application/json
{ "pin": "482913", "name": "Pastor's phone" }
Send the token back on every request as Authorization: Bearer <token>.
State. GET /api/v1/state returns what is live and next, the service, the layers, the production state and the timers.
Actions. POST /api/v1/actions/<action>, with a JSON body for any arguments. Among them: next, previous, go-live, clear, logo, black, message ({ "text": "…", "style": "banner", "targets": "all" }), clear-message, and the countdown's countdown-pause, countdown-resume and countdown-add.
TCP commands. NEXT, PREV, GOLIVE, CLEAR, LOGO, BLACK, CLEARMSG, MESSAGE <text>, STATE and SUBSCRIBE, one per line.
From PowerShell:
$h = @{ Authorization = "Bearer <token>" }
Invoke-RestMethod -Method Post -Headers $h http://localhost:7380/api/v1/actions/next
Was this helpful?