Chapter 6 · OpenQ User Manual

Remote control and network

6.1Remote devices

A second computer running OpenQ on the same network can follow the show and run it. This could be the stage manager's laptop or a tablet at the tech table. The computer running the show is the main device, and it does all the playback. The other device shows its cue list, playhead, running cues and meters, and sends GO and other commands to it.

Pairing a device

  1. On the main device, open Remote → Share this OpenQ, tick Let paired devices connect, and click Pair a new device…. A code such as C9XR-E9HJ appears.
  2. On the other device, open Remote → Connect to another OpenQ, click Search and choose the main device. If the search finds nothing, type its address, which is shown in the main device's Remote window.
  3. Enter the code and click Connect. After the first time, connecting needs no code.
Remote window on the main device showing a pairing code and a paired device list.
The main device while pairing. Paired devices are listed below the code, with their role.

Roles

RoleThe device can
View onlyFollow the show: cue list, playhead, running cues and meters.
ControlAlso press GO, stop, pause and resume, move the playhead, and start or stop single cues.
Control & editAlso edit the show. Changes are saved on the main device.

Set the role new devices get, and change any device's role, in the main device's Remote window. Changes take effect at once. Remove disconnects a device straight away, and it has to pair again to reconnect. When a device disconnects, it gets its own show back. Media files stay on the main device, so add them there.

Security

Connections are encrypted and authenticated. A pairing code works for 5 minutes and 5 tries, and someone who records the network traffic still can't work it out from the recording. After pairing, each device logs in with its own secret key. An address that keeps failing is blocked for 5 minutes. The Activity list shows connections and rejected attempts.

Network

Remote access uses TCP port 53200, and the search uses UDP port 53201. A firewall on the main device has to allow both. On guest Wi-Fi the search may find nothing; typing the address still works.

6.2OSC and network cues

Turn on OSC remote control in Settings → General. It listens on UDP port 53000 by default. Cues are addressed by their number.

AddressAction
/goGO
/stop · /panicStop all with the fade · stop all instantly
/pause · /resumePause all · resume all
/playhead/next · /playhead/previousMove the playhead
/playhead/4.2Put the playhead on cue 4.2
/cue/4.2/startAlso stop, pause, resume, devamp
/light/executor/2/level 0.5Executor 2's level; also go, release, flash (1 = press, 0 = let go). /light/grandmaster 0.8, /light/blackout, /light/release, /light/tap

A Network cue sends one OSC message to other gear. Set the host, port, address (for example /eos/cue/12/fire) and arguments. Arguments are separated by spaces: numbers are sent as numbers, and text in quotes is sent as text.