CueBot PTZ Support

Five-minute Quick Start

1. Connect the iPhone or iPad and the OBSBOT camera to the same local network.
2. Open CONNECT and run discovery. Use Add by IP when automatic discovery is not enough.
3. Save the camera, select it and confirm the app reports the camera as available.
4. Start or confirm preview where supported, then open SETUP and frame the shot.
5. Save a preset and recall it from LIVE → PRESETS.

Finding, saving and reconnecting cameras

Camera and device must be on the same local network and subnet. Discovery can find supported cameras automatically; Add by IP lets you enter a known local address manually.

Saved cameras can be renamed, reordered, reconnected and removed. CueBot restores the active Show's saved-camera setup when possible, but network changes or a different camera IP may require reconnection or editing.

Preview and multi-camera monitoring

CueBot Lite and Pro support NDI® preview where it is available and correctly activated for the camera. Pro adds multi-camera monitoring. Preview performance depends on camera settings, local-network capacity, device performance and the number of active preview streams.

The primary preview follows the selected camera. The monitor rail can show additional saved cameras at a lower preview bandwidth. During a camera change, CueBot may briefly retain the previous frame while waiting for a fresh frame from the new source.

Presets, Scenes and LIVE operation

Presets

CueBot Lite provides one camera, one Show Profile and nine preset slots. CueBot Pro expands the workflow to multiple cameras, multiple Shows and P1–P27 per camera. Save only deliberate, tested camera positions and confirm each recall before relying on it during a show.

Scenes Pro

Scenes are a CueBot Pro feature. A Scene can assign one or more cameras and store the intended preset plus supported camera actions. Changes in the Camera Actions workspace are not committed until you choose Save to Scene.

During Scene execution, CueBot uses travel-safe behaviour around movement and applies the final programmed state after the camera move. Rapid Scene changes are handled as latest-Scene-wins so obsolete work does not continue after a newer cue is fired.

LIVE

The LIVE deck provides PRESETS, SCENES, LOCK, REC and MORE. Manual PTZ or PTZR control is available for rescue and reframing; manual movement can disable AI tracking on the selected camera to stop the controls fighting each other.

QLab, MIDI and remote control Pro

QLab

Configure the QLab workspace address and ports, then run verification. A saved configuration is not the same as a verified live connection. Command Centre should continue to request verification when the live QLab response has not been confirmed.

MIDI

Configure the mapping, then send a real MIDI message during verification. CueBot suppresses Scene firing while verifying so the test message confirms communication without accidentally running the production.

Bluetooth or keyboard-style remotes

Activate remote control for the Show, map the required buttons and verify the input. Clear any unwanted mapping before assigning a different command. Command Centre reports when the active Show contains remote mappings but remote control still needs activation or verification.

Show Profiles, backups and restore

CueBot Lite includes one Show Profile. CueBot Pro unlocks multiple named Shows plus backup, restore and transfer. Use a separate named Show Profile for each production. Show data can include saved cameras, presets, Scenes, mappings and other show-specific configuration.

Create a backup after important programming changes and before moving to a new device or app build. Store a copy outside the device. When restoring, verify cameras and external-control connections because network addresses and connected hardware may differ.

Command Centre and readiness

In Lite, locked Pro systems are shown as neutral Pro features and do not create warnings. In Pro, All Systems Go should mean the currently configured production dependencies are ready—not merely saved. Configured systems such as QLab, MIDI or remote control may require an explicit live verification before they can be reported as ready.

A warning such as Verify MIDI or Verify Remote is an instruction to complete the live check. It does not necessarily indicate that the saved configuration has been lost.

Support & Diagnostics

Use Support & Diagnostics to copy a Support Trace when an issue cannot be explained by a screenshot alone. A trace can include build information and recent operational context that helps identify camera, preview, Scene and external-control behaviour.

Review the trace before sharing it. Camera names, local IP addresses or show labels may appear because they are relevant to troubleshooting.

Troubleshooting

Camera does not appear

• Confirm camera and device are on the same local network and subnet.
• Allow Local Network access in iOS/iPadOS Settings.
• Disable or reconfigure any VPN that blocks LAN access.
• Try Add by IP with the camera's current local address.
• Power-cycle the camera only after confirming the network and address.

Camera is saved but offline

• Use Reconnect or Verify for that camera.
• Check whether the router assigned the camera a new IP address.
• Edit the saved camera if its address changed.
• Confirm the camera is not connected to a different isolated Wi-Fi network.

Preview does not appear or remains on Switching

• Confirm NDI® is available and activated for the camera.
• Check that the correct saved camera is selected.
• Reduce competing network traffic or preview load.
• Use the explicit Retry or Start control after the app reports a failed first-frame attempt.
• Switch to another camera and back only after the current recovery state has completed.

A Scene moves the wrong camera or reaches the wrong shot

• Open the Scene in SETUP and confirm assigned cameras and preset numbers.
• Confirm each camera's preset was saved on that physical camera.
• Use Save to Scene after editing Camera Actions.
• Check active Show and camera names before firing.
• Collect a Support Trace immediately after the failed recall.

QLab, MIDI or remote says verification required

• Run the verification for that system and send the expected live message or response.
• For MIDI, confirm the RTP or hardware route is actually connected—not just configured.
• For remotes, confirm remote control is activated for the active Show.
• Do not treat a previously saved verification as proof after the external connection changes.

Privacy policy

View the CueBot PTZ Privacy Policy.