ProPresenter Integration

Two supported ways to show OmniWord captions in ProPresenter 7. Use one path per room unless you intentionally run both.

Path	Best when	Where to configure
ProPresenter Direct	You want captions in a ProPresenter Message template ({Lang1} / {Lang2}), or you run ProPresenter on macOS	Account → Settings → Screens & Broadcast
Prop Web Object	You prefer a transparent webpage Prop on Windows (same idea as OBS Browser Source)	Account → Settings → Screens & Broadcast → Web Overlay URL

macOS — Prop not supported

Prop Web Object does not work reliably on macOS (ProPresenter’s web layer often fails to refresh live captions). If you operate ProPresenter on a Mac, use ProPresenter Direct only. Prop remains an option on Windows.

If you have not selected languages or opened Screens & Broadcast yet, start with the On-Site Captions overview.

---

ProPresenter Direct

OmniWord pushes paced captions from the operator browser to ProPresenter on the same computer via the local Message API (http://127.0.0.1). The OmniWord server never talks to ProPresenter directly.

Requirements

• Open the OmniWord Live (operator) page on the exact same PC that runs ProPresenter
• ProPresenter Network / Message API enabled (note the port — often 50001)
• One Message template with tokens named exactly Lang1 and Lang2 (case-sensitive)

Lang1 receives Live Translation 1; Lang2 receives Live Translation 2. Font, color, and position are controlled only inside the ProPresenter Message template — OmniWord only fills the token text.

Setup in ProPresenter

Do this once on the ProPresenter computer before wiring OmniWord.

1. Enable Network / Message API

1. Open ProPresenter → Preferences (Windows: File → Preferences; macOS: ProPresenter → Settings).
2. Open the Network tab.
3. Enable Network / Enable Network Link (wording varies by ProPresenter 7 build).
4. Note the Port (commonly 50001 — use whatever ProPresenter shows).
5. Apply / OK, and restart ProPresenter if it asks you to.

2. Create a Message

1. Open the Messages window (toolbar Messages control, or View → Messages).
2. Click + / Add to create a new Message.
3. Give it a clear display name you will type into OmniWord later — for example Live Translator or OmniWord.
4. Keep this name handy; Screens & Broadcast matches by exact Message name (or UUID).

3. Add text boxes and tokens

1. In the Message editor, add a Text object (or edit the default text box).
2. Place the text where captions should appear (often a lower-third strip).
3. Insert a token whose name is exactly Lang1 (case-sensitive). In the template it usually appears as {Lang1}.
4. For a second on-screen language, add another Text object and insert a token named exactly Lang2 → {Lang2}.
5. Do not rename tokens to lang1, Language1, OmniWord1, etc. OmniWord only writes to Lang1 and Lang2.

One Message, two tokens

Use a single Message that contains both {Lang1} and {Lang2} text boxes. OmniWord fills both tokens in one trigger. You do not need two separate Messages for Target 1 / Target 2.

4. Style the Message

In the Message editor / Inspector, set font, size, color, alignment, and shadow the way you want captions to look on the audience screen. OmniWord does not control styling — only the token text updates live.

5. Smoke-test in ProPresenter

1. Trigger / show the Message from ProPresenter’s Messages UI.
2. Confirm {Lang1} (and {Lang2} if used) appear in the right place on the look / audience screen.
3. Clear the Message when done testing.

When the Message name, port, and tokens are ready, connect OmniWord.

Setup in OmniWord

1. Go to Account → Settings → Screens & Broadcast.
2. Select Room for the service you will run.
3. Under ProPresenter Direct, enable Local ProPresenter API.
4. Set Port to match ProPresenter (default 50001). Host is always 127.0.0.1.
5. Enter the Message display name you created above (e.g. Live Translator) or its UUID.
6. Click Test — OmniWord should connect and can trigger a sample caption into {Lang1} / {Lang2}.
7. Click Save.

Same computer required

Browser security only allows HTTPS pages to call http://127.0.0.1. If the operator opens OmniWord on a different machine from ProPresenter, Direct will fail — move the operator browser to the ProPresenter computer. On Windows only, you can alternatively use Prop Web Object. On macOS, stay on Direct and keep the operator browser on the same Mac.

Sunday morning

1. Launch ProPresenter with Network enabled and your OmniWord Message ready.
2. On Live, set Live Translation languages before Start translation.
3. Confirm ProPresenter Direct status shows ready for Target 1 / Target 2.
4. Start translation — captions stream into {Lang1} / {Lang2} as speech is translated.
5. Show / clear the Message on the audience screen as you would any other ProPresenter Message layer.

Settings are per room: campus A and campus B can use different ports or Message templates.

---

Prop Web Object

Windows only

This path is for Windows ProPresenter. On macOS, skip this section and use ProPresenter Direct instead.

Keep overlays in a reusable Prop so captions ride above every slide. Buttons and labels mirror the ProPresenter 7 Props tray — adapt wording if your build updates its UI.

Copy each Target URL from Account → Settings → Screens & Broadcast → Web Overlay URL (not from Live).

1. Props library → Add Prop

Click the Props icon (three stacked rectangles) along the narrow media toolbar near the Libraries column, choose a collection (Default Collection unless you segregate overlays), then press the large centered + · Add Prop chip to instantiate a transparent shell.

Screenshot: Props tab active (blue toolbar icon) · tap the oversized + control to mint a blank prop thumbnail.

2. Edit the prop

With the translucent checkerboard thumbnail selected, tap the pencil (Edit) to launch the Prop editor canvas + Inspector pairing.

Screenshot: tiny checkerboard thumbnail = empty prop awaiting layout; pencil opens the authoring surface.

3. Insert a Web object

Name the Prop in its Inspector pane for recall (examples: LiveTranslator / OmniWord). On the inset toolbar above the canvas, tap the globe icon (Web Object) to insert a webpage layer into the Prop.

Screenshot: globe injects the HTML layer—you'll position it in the caption area next.

4. Place it in your caption area

You don't need to stretch the web object across the whole canvas. Drag the white handles so the box covers only where you want subtitles—often a lower-third strip at the bottom of the slide. Captions anchor to the bottom of that box, so sizing the region is enough.

Screenshot: position the web object only where captions should appear; subtitles align to the bottom of that region.

5. Paste URL + tune Fill ▸ Web

Leave the Web object selected inside the Objects list (Web highlighted). Inspector → Shape ▸ Fill ▸ Web → paste the HTTPS Target link from Screens & Broadcast (you can paste before or after resizing—the bounding box controls where pixels land on air).

Screenshot: Fill enables Web subtype; OmniWord URLs often show only the trailing /overlay parameters after ProPresenter trims the hostname—overwrite with the clipboard copy if PP leaves the field truncated.

6. Second on-screen language

You can show two overlay languages at once—for example English in a lower-third and Japanese at the top. On Live, select both Live Translation 1 and Live Translation 2. In Screens & Broadcast, copy Target 1 and Target 2 separately. In ProPresenter, add a second web object in another region of the Prop; the lang= parameter in each URL selects which language appears there.

Screenshot: two web objects in one Prop, each sized to its caption region and filled with a different lang= overlay link from Screens & Broadcast.

Sunday morning

Enable or clear this Prop alongside other broadcast layers so translators stay synced without editing each worship slide individually.