Connecting Multiple Camera

Hi ​@HOW TO CONNECT MULTIPLE CAMERA! Good username - it’s a tech support request all in itself 😆

So, multi-camera detection and tracking is supported in the Voyager SDK. The key is, don't start a second pipeline per camera. Instead, pass multiple sources into one pipeline. A second pipeline will try to claim the Metis device already in use, which could well be why you see an error.

If that doesn't sort it, can you share the exact error message, how you launch each camera, your camera types (USB/RTSP/MIPI), OS, host system, SDK version etc.

he team's right — don't run a second pipeline, that's what throws the error because it tries to claim the device that's already busy. Feed all cameras into one pipeline instead.
In the pipeline YAML the video field takes a list, so just add all your streams there:
video:
  - /dev/video0
  - rtsp://user:pass@192.168.1.50:554/stream1
  - rtsp://user:pass@192.168.1.51:554/stream1
One pipeline, one inference, the streams are demuxed automatically and you get detections for all of them. If your cameras are all RTSP that's exactly the same syntax, just more URLs.
A couple of gotchas I hit myself:
- USB cameras on the same bus can saturate the host — I'd use RTSP over network if you have more than 2 USB cams, otherwise you'll see the "2nd camera error" come back as a bandwidth issue instead.
- Make sure each source has its own stream_id if you want to tell detections apart (or use the --source-info flag in the run script).
What error exactly do you get when the 2nd camera starts? If it's device already in use or similar, it's the pipeline issue. If it's a v4l2 timeout, it's bandwidth.

Checking back in — did the single-pipeline multi-source setup work with
your cameras? If the second camera still throws an error, post the exact
message: as mentioned it's usually either "device busy" (pipeline issue)
or a v4l2 timeout (USB bandwidth), and the fix is different for each.