Thanks
Though with these rigs, it's far from flooding my bandwidth, nor any of the resources while recording/streaming by Manycam 7.5.1.5, I can't afford manycam for each rig 8( heh plus manycam doesn't have a night mode 8P nor does it have a backend to mod like OBS.
It shows preview presets from all 5 monitors on both GPU0 and GPU1 to switch between with another 7 presets of follow cursor, or locked area's of displays being showed (no matter the GPU their using) on designated monitors and HDMI capture card feed.
All showing nicely thru Manycam's video preview from the all monitors GPU0, GPU1 and capture card, and not even breaking a 20% utilization on CPU, CPU-MEM, GPU0, GPU1 & their MEM. I only hit 90% when running multiple windows of programs, and resource hog games do i crack 90%, and still unable to see signs of slowing down to the eyes, while recording and streaming.
So either manycam is doing voodoo magic, or obs needs to take notes from manycams hardware abstraction layer methods for copying memory around.
Thanks for the reply, BF
I believe that Manycam does its rendering/composition in system RAM by CPU, with minimal (if any) capability to overlay or add multiple sources to a composited scene; OBS handles everything in VRAM instead with GPU acceleration, which scales MUCH better in a situation that may have truly massive numbers of sources and effects to layer and composite. OBS has to do this, because it can do so much
more than Manycam.
Also, not saying that they couldn't add support, or that it would affect your rig. Mine would be fine too. But the guy trying to stream from a U-variant i3 (or Pentium) laptop with an Intel IGP? Yeah, it'll mess him up but good. And generate more support requests/hassle, because
when it messes him up, he won't know why. For a very niche segment of the user-base (multi-gpu systems, aside from laptops)? They just have larger features to address and add that will benefit a wider part of the total OBS community, and an already-overfull plate of those.
Up side, OBS is open source! If you've got the spoons to get this implemented, I'm sure that Jim and the rest of the dev team would be happy to see a pull request adding it as a feature. Until then, OBS may simply not be the tool you need, even if it is the free alternative.
Side-option/workaround, you can run a second copy of OBS in Portable Mode on the second GPU at the same time (ignore the 'obs is already running!' warning), install the obs-ndi plugin on both, then assign NDI Output filters on each display-cap on the OBS PM instance for the second GPU, then catch them with NDI Sources on the main OBS instance for integration and inclusion into your scene. Since it's all on-system loopback and not over the network, impact really should be minimal. With OBS, creative use of existing features can get you far. :)