Feature
Connections
On this page
The Connections page of Present's settings links Present with the rest of your gear in both directions. Send to other gear is the list of devices a slide can send a cue to: a lighting console, a switcher, a sound desk, vMix, Companion. Receive commands lets a MIDI keyboard, a lighting console or a Stream Deck drive Present.
Where to find it
Open Present, click Settings in the top bar, then Connections (under System). Sending works from the web app and from Tech Manager, because the booth computer makes the connection either way. Receiving commands only works in Tech Manager on the booth computer.
Add a device to send cues to
- In Present, click Settings, then Connections.
- Under Send to other gear, click Add device. The Add a device window opens.
- Under What is it?, click the tile for your gear: vMix, Bitfocus Companion, ProPresenter 7, Resolume Arena (two tiles: HTTP (REST) and OSC), X32 / M32, QLab, disguise, OBS Studio, Q-SYS Core, ATEM switcher, Ross switcher, MIDI device, Other OSC gear or Other web API. The tile knows how that gear talks and which port it usually listens on, so you never pick a protocol.
- Type a Name you will recognise, such as "Lighting desk". Leave it blank to use the product's name.
- Fill in the Address: the device's IP address or host name, and its port, already filled in with the usual one. The line under the box says what the device expects.
- OBS Studio has no address: it uses the booth's own OBS connection from the app's Settings.
- ATEM switcher: leave the address blank to use the ATEM the booth is already connected to.
- MIDI device: choose Connected by USB (a device on this computer) or Network (RTP-MIDI), then the Device (pick or type its name; blank uses the first) or the host and port, and the Channel.
- Click Test to send a harmless message. The window says whether the device answered.
- Click Add device. The device appears in the list with its address.
To change a device later, click Edit on its row: the same window opens as Edit device, with Delete and Save. Slide actions keep pointing at the device when you rename it or change its address. Test on a row sends a harmless test message at any time; the result shows under the row.
Fire a cue from a slide
In Present, right-click the slide that should fire the cue, point to Add action and choose Action palette… (or pick a device straight from Other gear in that submenu). The actions window opens, headed with the slide's number, and lists what already runs when the slide goes live, top to bottom.
The same Add action submenu also adds the common actions in one click, without the window: Clear, Audience look, Stage layout, Go to slide, Timer and Macro.
- In the actions window, click Add action. The picker has two groups: On the screens (Start timer, Stop timer, Stage layout, Clear layer, Go to slide, Run macro, Switch look) and Send to other gear, with each of your devices by name.
- Click the device. A new row opens with the device under Send to. If the device is not in the list yet, click Add a device…: the same Add a device window opens, and the new device is chosen for this row when you add it.
- Under Do, pick what the device should do, in plain words (for vMix, for example, Cut to input; for Companion, Press button), and fill in the boxes it needs. Gear Present does not know by name takes the raw message instead: an address and arguments for OSC, a path and body for a web request, a command for RossTalk. Open Request it sends to see exactly what will go out.
- Click Test now to send this one action to the device straight away. The row says whether it answered.
- Click Done on the row. Closed, the row reads as a sentence, such as "Press button 1 / 0 / 1", with the device's name under it and "sent by the booth".
- Click Done to close the window. Every change is saved as you make it.
A slide's actions run in the order listed. Drag a row by its handle to reorder it, or open the row's … menu for Move up, Move down and Delete action. A Go to slide action always stays last. Playlist items have Add action… in their right-click menu too. To change or remove an action later, right-click the slide and point to Edit action or Remove action: each lists the slide's actions as the same sentences.
Let other gear drive Present
In Tech Manager on the booth computer:
- In Present, click Settings, then Connections.
- Under Receive commands, open MIDI, OSC or HTTP and switch on what you need. Nothing listens until you do.
- Listen for MIDI: choose the Device (or Any device), then add a mapping for each key or controller. Each mapping is a Note or a Control change, a channel (or Any channel), the note or controller number, and the command, such as Next slide, Previous slide, Toggle blackout, Start timer or Run macro.
- Listen for OSC: set the Port (1024 to 65535). Turn on Accept from the church network to take messages from other computers; OSC has no password.
- Listen for HTTP: set the Port. Every request must carry the booth's Token as "Authorization: Bearer" followed by the token. New token stops every device using the old one. Accept from the church network lets other computers send, still only with the token.
- When a listener is running, its row says "Listening on" and its address.
The Command list shows the addresses: for example /wm/next, /wm/previous, /wm/cue/3 (go to slide 3), /wm/blackout, /wm/clear, /wm/timer/start/ followed by a timer's name, and /wm/macro/ followed by a macro's name. The same address works as an OSC address and as an HTTP path, so a Stream Deck or Companion button can send an HTTP request to it.
Press Companion's buttons from Present
Bitfocus Companion's web buttons can show inside Present's settings, so a Stream Deck page is a few clicks away without leaving Present. This is separate from sending cues to Companion from a slide (above).
- Go to Present, open Settings and click Connections. Scroll down to Companion.
- Type the IP address of the computer running Companion in the address box, check the port (8000 unless you changed it in Companion) and click Connect. In Tech Manager, a Companion running on this computer or found on the network is offered under the box (marked This computer or On the network), and Find Companion looks again.
- The dot beside the address turns green with a check when Companion answers, the line under it reads Connected to and the address, and Companion's buttons appear under it. Click a button to press it, the same as on the Stream Deck.
- To show only some of Companion's pages, rows or columns, click the gear at the bottom right of the buttons. Buttons view has Pages (Companion's own page numbers, such as 1, 1..3 or 1,4; empty shows every page), Columns and Rows (first to last, counted from 0 as Companion numbers them), Show page names and Reset to Companion's default. Click Back to return to the buttons. Showing fewer columns makes each button larger.
- Open in a window opens the same buttons in a browser window of their own.
The address is remembered on this computer only, not shared with the church. On the web app the buttons show inside Present in Chrome and Edge: the first Connect makes the browser ask to let this site reach devices on your local network; choose Allow. Use Companion's IP address there, not a computer name. Safari and Firefox cannot show Companion inside a web page, so there the button reads Open and Companion opens in its own window.
Let a web page on a slide go to other sites
A web page on a slide stays on its own site: a link to another site does nothing. To change that, in Present > Settings > Connections, under Web pages on slides, tick Allow any site. Point at its (i) for what it means: the audience sees wherever the page goes.
Troubleshooting
"Remote control listens on the booth computer."
You are in the web app. Open Present in Tech Manager on the booth computer to set up MIDI, OSC or HTTP commands.
"The booth did not save that. Try again."
The booth computer did not accept the last change, and the tab went back to what it had. Make the change again; if it keeps failing, restart Present.
A listener shows a warning instead of "Listening on"
The warning says why it could not start. If another program already uses that port, choose a different port between 1024 and 65535 and update the sending device to match.
The cue did not reach the device
Click Test on the device's row in Send to other gear, or Test now on the action's row. If the test does not arrive, check the address and port, and that the booth computer and the device are on the same network. Cues are sent by the booth, so the booth computer must be on with Tech Manager running.
An action says "Choose a device"
The row has no device yet. Open the row and pick one under Send to, or click Add a device… there.
An action says "The device this sent to is gone"
The device was deleted. Open the row and pick another device under Send to; the action keeps its message.
Companion says "Nothing answered"
Companion is not running, the port is not the one Companion's own window shows, or this computer is on a different network. Fix that and click Connect again.
Companion says Chrome is blocking this site from devices on your network
You did not allow the browser's local-network prompt. Click the icon at the left of the address bar, turn on local network access, then click Connect again.
The address box says it is a placeholder
A tile fills the address with a sample such as "the vMix computer's address". Replace it with the real IP address or host name of the computer the gear runs on.
Good to know
- These connections are separate from the switcher and camera control in Produce; the OBS Studio connection itself is set up in the app's Settings.
- A MIDI device on USB sends from the computer you are on; everything else is sent by the booth.
- Commands taken from other gear do exactly what the same click would, and the room's history records where each came from.
- In a room locked from another computer, this page is read-only, and commands from other gear to this computer are refused until the room is unlocked.
- A media clip can send cues too: in its inspector, the Macros tab lists what runs when the clip starts and ends, in the same sentences.
Was this helpful?
Still stuck?
Journey can look at your own setup once you are signed in, or you can call us.