Record a baseline
Write down the camera name, cable, port, negotiated link, capture format and application. Verify a stable single-camera recording first. Saving this baseline prevents a later driver or automatic exposure change from being mistaken for a topology improvement.
Separate transport from processing
Dropped capture frames with a bus overload point toward transport; a smooth preview followed by a stuttering encoded recording may indicate a processing bottleneck. Monitor both capture and encoder statistics where your software exposes them. Compressed input can reduce USB demand while increasing decoding work.
Build the final topology from evidence
- Move high-payload cameras first when balancing verified independent paths.
- Use a short known-good data cable with the correct supported speed.
- Check that another application has not opened the same camera.
- Confirm hub power capacity for all devices.
- Retest all streams simultaneously for the duration of the intended session.