4 active video devices limit?

gtaksa

New Member
I am on OBS 27.2.4. After a lot of troubleshooting after being unable to get a 5th camera working I found that if I check "de-activate when not showing" on at least 2 of the video capture devices in the device properties, the 5th camera works fine. It makes sense that it must be 2 devices because when I tried checking that for only 1 device then when switching to that camera it goes over the limit of 4 and there's no display. When I switch to one of the cameras that only becomes active when showing, it takes about 1 second for the display to show up. I use the plugin "Auto Scene Switcher" and stream myself djing - this 1 second delay for the display to turn on does not look good - it really detracts from the experience.

Is this a known limit or is there something I can do to fix this? I have a X570 motherboard (ASUS ROG Strix X570-e gaming) and an AMD 5900x CPU - I doubt it's a bandwidth limitation. But just to check I did unplug a USB hub with a few devices connected to it and that didn't have any impact. Some of the cameras are plugged into a different USB hub - I have not tried plugging them all into direct USB ports as opposed to the hub but my troubleshooting didn't lead me to think that would make a difference, plus it would be a major pain to try that as the cords are behind a heavy desk against a wall.
 
Soo,
your cameras use:
MJPEG - 70 Mb/s (typing value i’m not sure)
or
NV12 - 711 Mb/s

1920*1080*30*12 = 746496000 bits = 711 Mb/s per camera, but reserve litte more data bus in system.
resolution fps bits
You can use 10 more device MJPEG like NV12.
 
USB Root Hub limitations are a well discussed limitation on many systems
USB Root Hub related
And then there is the basic reality that real-time video encoding is VERY computationally demanding. Doing that for 4X cameras is that much more demanding. The limit is your computer. I recommend monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization [for ex. using Task manager’s Performance tab and/or Resource Monitor] to see if your system is being maxed out with your settings. Though not all bottlenecks are easily visible, especially when issue may be within a chipset
If you aren't doing real-time monitoring, you are doing the equivalent of driving blind-folded... bumping/crashing into things is to be expected in that scenario.

And don't overlook possibility that it may be a USB camera driver 'challenge' issue, (ie poor driver outright, or a combination of driver and settings)
 
Back
Top