Video and replay

Select an aircraft and open Video. Its module publishes the camera stream to SRS. Terminal requests authorized WebRTC signaling from Mainframe, then receives media from SRS. Camera, lens, zoom, gimbal, and recording controls appear only when the provider supports them and your account has access.

The Video Wall shows several feeds together. More viewers and higher bitrates increase server egress. Hidden panels can suspend browser-side streams; continuous recording is governed by Mainframe’s recording policy, not whether a panel is visible.

Enter replay

Use Timeline to choose an earlier time. The map, telemetry, charts, and recorded video follow the replay playhead. Event and alert navigation can help you locate a moment worth inspecting. Return to live before sending commands.

A recording becomes available after SRS closes a segment and the media indexer converts, uploads, and registers it. With one-minute segments, the latest moment will usually lag live video. A missing interval is a gap; the player should not pretend that unrelated footage covers it.

What the recordings mean

Mainframe’s media index ties each segment to an entity and a time range. The actual MP4 object lives in the private bucket. Access checks still apply when replaying it. Keeping the bucket and database together is essential for recoverable history.

The staging configuration keeps media for 30 days and state history for 90 days. This means older telemetry can remain after its video has expired. Ask the deployment administrator before changing retention because continuous multi-camera recordings grow quickly.

If live video works but replay does not, check the indexer’s failed segments, recent manifest timestamp, and S3 uploads. If signaling succeeds but live playback fails, check the SRS WebRTC candidate and UDP reachability.