Production Truck: What you can operate

What you can operate

• A compact scene browser shows six scenes per page, searches full OBS names and marks preview/program selections. Hide/show the scene list without concealing overlay or audio controls; the browser remembers this choice. Repeated generated scene prefixes are shortened for display only; hover or assistive labels expose the full name.
• Preview and program scenes independently; cue a truck camera, cut live, or take a Fade/Cut transition.
• Use the truck's existing camera registry, custom scenes, graphics and stable event overlay URLs. Download the current Hub OBS scene collection and import it through OBS.
• Edit camera-to-scene/source mappings locally, with RTSP/SRT/RTMP network URLs or NDI sender names. Create network camera inputs and scenes in OBS. USB/capture-card inputs are set up in OBS and then mapped to a truck slot here.
• Mute/unmute audio and adjust input volume; start/stop the program recording, broadcast and OBS replay buffer. Save recent program clips.
• Paired trucks apply their assigned SRT or RTMP/RTMPS production output to OBS while off air and verify it by readback. Local productions can configure SRT or RTMP/RTMPS in Engineering. Encoders, audio monitoring, recording folders and replay duration remain in OBS.
• Produce any local event without a Hub truck: name it, add camera mappings and use your existing OBS scenes. The event does not need teams or a sport.

The preview/program panels are periodically refreshed confidence images, not full-motion low-latency video monitors. Keep OBS's program monitor available for critical motion/audio checks. Replay and recording controls capture the program output, not independent camera ISO recordings. Camera inclusion flags from Sports Hub are retained in the configuration; they do not enable separate camera recording engines. Camera PTZ/motor control is not implemented.