Loading...
RCP
This beta needs Companion 5.1 or later and Multicam RCP beta 261028 or newer (integration API 1.0-preview). The token screen in RCP comes in the beta after 261028.
127.0.0.1:5994. Existing saved ports are preserved.Tokens expire and can be revoked. Changing the active RCP project requires a token for that project. Old Socket.IO-only servers are not supported by this beta.
Controls use discovered camera IDs and available properties. Numeric increment/decrement runs against current server state, with the server's small/normal/big steps. User camera selection, routing, and PTZ/scene preset recall/store/clear use the same owners as the RCP app.
Continuous movement is unavailable in the API preview. Requests are rejected explicitly. PTZ preset recall remains available.
Tracing (recorded PTZ paths, RCP with tracing in the integration API): use the preset
actions in Tracing mode. Store starts recording the camera's path into the preset and a
second Store saves it; store on several cameras with one button to record them together,
so they play back in step. Recall plays the path from its start (a repeated recall
starts it again, it never stops it). The camera's Tracing speed control sets the pace
(1 = as recorded, 0 holds the head). Tracing: Speed (Several Cameras) sets one speed on
every chosen camera in one pass, so cameras recorded together stay in step: put its Up and
Down modes on a rotary encoder for a speed lever, or Set 0 before the recall so every
camera waits at its start. Tracing: Stop ends a playback; recalling a normal PTZ preset ends it too. The
Tracing: Camera State feedback and the camera_N_tracing_status, _preset,
_progress and _remaining variables show what each camera does. Camera readback is separate
from command admission; accepting a command does not prove that hardware completed it.
Follow (3D Tracing, RCP with Follow in the integration API): Follow: Start points a
camera where a leader camera's centre of picture meets a surface of the site (its surface ID
from the RCP's 3D Tracing page), or the level ground at a height. Zoom can stay with the
operator, keep a frame width in metres at the target, or match the leader's picture. Start it
again to change it; Follow: Stop, or any other move of the follower, ends it. Both
cameras need a position on the site. The Follow: Camera State feedback and the
camera_N_follow_status and _follow_leader variables show it.
Preset numbers are the ones the RCP shows: Preset 1 on a camera is preset 1 here (up to 999).
Values follow the camera's own definition. A control the camera reports shows a dash until
it has reported. A control with named steps (gain in dB, shutter speeds) shows the step's
name on its gauge and in a camera_N_<control>_text variable; the plain variable keeps the
number. When the camera does not take a control now (knee level while knee is on Auto), a
press is refused with the camera's reason in the log, and the Property: Not Available Now
feedback can grey the button.
Buttons made with 1.0 keep their actions and feedbacks. User: Select Camera and User: Clear Camera Selection now select a choice on the user's controller switcher in Multicam (its choice for that camera, or its choice with no camera), so the user needs a switcher there; without one, or without a matching choice, the press is logged as a warning. Controller: Select Choice is the general form. Presets are Companion 5 layered buttons, arranged in sections per camera, user and router with a group per control family. Every numeric control has a Gauge / rotary preset: a ring gauge with the live value that also carries the encoder's rotate actions, so the same preset serves a button, a Stream Deck + LCD segment or the encoder under it. Control gauges list the same tiles for every camera. A disconnected value shows a dash.
The look and the offered devices are chosen on the RCP under Setup → Companion buttons: ring, bar or plain gauges, colour per control group / one colour / monochrome, Companion's top bar on or off, and which cameras and routers get presets. Changes reach the preset list within a second; placed buttons keep working.
The Stream Deck +: <user> section is one page that follows the operator. Row 1 holds the user's camera choices (live image where the RCP links a video source; press to select). Row 2 picks a control bank: Gain, Gamma, Lift or Exposure. The four LCD segments show the bank's four controls of the selected camera as ring gauges with the active step size underneath, and the encoder under each segment turns that control by the user's step size. Pushing an encoder cycles the step size (fine, normal, coarse) and the gauges follow. Bank and step size live in this Companion connection per RCP user.
Text size, gauge style and colours come from the RCP's Setup → Companion buttons page.
The Live video · 16:9 section provides one preset per discovered video source. Each uses the whole key width, preserves 16:9 and leaves space for its label. Its image is a local value feedback; JPEGs are not saved into button configuration on each frame.
Defaults: 160×90, 10 fps, JPEG quality 65. Edit the Live video image feedback to choose 16–640 × 16–360 pixels, 1–15 fps and quality 20–90. Higher resolutions and rates consume more bandwidth and processing. Matching source/profile feedbacks share one subscription; the backend can share capture/decoding with other consumers. The final feedback being disabled or removed releases demand. Hidden-page behavior follows Companion's feedback lifecycle.
Images clear on disconnect or after two seconds without a new frame. Keep RCP and Companion clocks synchronized; images older than two seconds are discarded. Capture/source changes reconnect after a short delay. The first API preview accepts configured source IDs, not camera monitoring aliases or route-following crops.
Local acceptance on Companion 5 rendered about 10 fps for one animated native test source at 160×90. This is not a maximum supported source count, a real-camera benchmark or a new physical Stream Deck throughput measurement.
Select Multicam Cloud (preview) and enter the cloud API HTTPS origin, integration
client ID/secret, project ID and exact target instance ID. Use a project integration
client created through /control/v1/clients with monitor and the required control/
routing scopes. General organization API credentials are a separate credential type.
The module exchanges the secret for short-lived tokens and renews them in memory.
Revocation or loss of the selected instance disconnects the module; it never switches
targets automatically. Discovery, controls and gauges use the same API as local RCP.
Cloud live-video presets are unavailable until the cloud media transport is implemented.
Requires the matching cloud/RCP integration preview rollout; local fixture tests do not
establish production cloud readiness.
Multicam Systems
Community