Loading...
ChurchTranslator.AI
Run live sermon translation from the booth: start and stop the service, pause translation, and set the language the speaker is preaching in — with the buttons lit from the real state of the service.
This module talks to your own ChurchTranslator.AI church. You need an account at churchtranslator.ai and a capture token.
In the ChurchTranslator.AI dashboard, open Connected devices → Booth control and click Mint a "Booth Stream Deck" token. Use a dedicated token so you can revoke the deck without touching the computers that stream audio.
In Companion, add the ChurchTranslator.AI connection and fill in:
| Field | Value |
|---|---|
| Server URL | From the Booth control card — https://api.churchtranslator.ai for most churches |
| Capture token | The token you just minted |
| Session name | Sunday unless support told you otherwise |
| Status refresh | How often to poll, in seconds (default 3) |
Open Presets → ChurchTranslator.AI and drag the buttons you want onto your pages. The language buttons are generated from the languages your church actually uses, so there is nothing to delete.
If the connection turns red with "Capture token rejected", the token was revoked — mint a new one on the same dashboard card.
| Action | What it does |
|---|---|
| Start service | Tells listeners to expect audio and asks your capture app to start streaming — it picks this up within a few seconds if it is open and signed in. |
| Pause translation | Mutes translation. Listeners stay connected and billing stops. |
| Resume translation | Unmutes. |
| Toggle pause / resume | One button for both, driven by the live state. |
| Stop service | Ends the service; the capture app stops streaming. |
| Set speaker's language | The language being preached, from a dropdown your server fills in. Tick "Switch the running service now" to change a service already streaming (a few seconds' pause); otherwise it applies to the next service. |
| Refresh status now | Forces an immediate poll. Rarely needed. |
The language dropdown supports Companion's expression mode, so it can be driven from a variable or trigger without a separate action.
status, running, paused, starting, listeners, source_language,
source_language_label, scheduled_source_language, engine,
languages_translating, last_error.
Companion prefixes variables with your connection's label, not a fixed
name. If you name the connection ct, you write $(ct:status); if you name
it Woodmark, you write $(Woodmark:status). Presets you drag in are
rewritten to your label automatically.
The deck can also say how the service is doing, not just whether it is on. Problems are shown by exception: a healthy deck looks the same every Sunday, so the one button that changes colour is the one to look at.
level), and set the element's three options to the
expressions $(local:level).mode, $(local:level).lit and
$(local:level).hold. The Input meter preset comes wired up this way.
A meter key placed with module 1.3 or earlier loses its bar from 1.4.0 —
drag the preset again. So does a meter key copied to another Companion
through Import / Export (Companion doesn't carry an element's connection
across an import); drag the preset there too.total_listeners, on_air (42:13, blank when not live),
input_peak_db, input_state (live / paused / off / nosound /
nofeed / unknown), and for each of your languages listeners_<code> and
health_<code> (translating / idle / stalled / unavailable) — e.g.
$(ct:listeners_ru).The meter moves ten times a second over a WebSocket that is opened only while a service is live, not paused, and an Input level feedback is on a button. If that connection is blocked, the meter still moves at the status refresh rate.
Against a ChurchTranslator.AI server older than the read-out (before 2026-10-02) none of this appears: the variables are not created, the presets are the earlier ones, and no WebSocket is opened.
The translation engine takes the speaker's language when it opens its connections at the start of a service, and it cannot be re-pointed mid-stream. So:
If your services always run in the same order, you can skip the buttons entirely: set the speaker language per service under Service schedules in the dashboard, and the server switches it when capture starts.
Speaker-language support was added to ChurchTranslator.AI after start/pause/stop. Against a server that predates it, this module logs one warning, keeps the connection green, and everything except the language buttons works normally.