Change the Video Source#
A camera’s video can come from a file, a live camera (RealSense
or USB webcam), or an RTSP stream. The source is one field of the camera
in configs/cameras-pymavlink.yaml
(or cameras-uavsdk.yaml); detection, captioning, and overlay settings are
the same for all three.
Source |
Camera file |
REST start request |
Pipelines used |
|---|---|---|---|
Video file |
|
|
|
Live camera |
|
|
|
RTSP stream |
|
|
|
Set exactly one of video, device, or rtsp per camera. Then:
make check-cameras # validates the file; reports a missing video file, device node, or pipeline
make start-rtsp # or disarm/arm; the file is re-read at every arming
Notes per source#
Video file — the folder
resources/videosis mounted read-only in the container, so a new file is visible without a restart; a running pipeline switches to it at its next start. Files must be H.264; usescripts/convert_video.shfor anything else.Live camera — the device node must also be listed in
.env(CAMERA_DEVICE_1…CAMERA_DEVICE_4) so the compose file passes it into the container; recreate the container (make pymav-up) after changing it. Each node can be used by one camera only. See RealSense Camera.RTSP stream — used in UAV Mission Compute SDK mode, where the camera file is
configs/cameras-uavsdk.yamland{uav_id}is replaced byUAV_IDfrom.env. The manager starts a camera only once its stream can be read; a stream that is not available is skipped and retried. Any RTSP source without authentication works, not only the SDK’s.
For a pipeline started by hand through the REST API, the same values go in
the request’s parameters — see
Manage Pipelines — Start a pipeline.