Hi,

I think you need to simplify the vMix project. Last year I worked on a green-screen project with virtual sets. The main project included around 20 different Virtual Set inputs for the different camera views, image inputs for 4 different set designs as well as video content. When we got up to around 190 inputs, vMix was taking around 5 minutes to actually open the project and everything ran very slowly - the UI was lagging and outputs stuttering. So it was very clear that we needed to break up the project into separate projects for each set design. Next, anything that could be grouped into one input (different logos, backgrounds) were collected into a Photo slideshow input, and finally anything that could be offloaded to external playback was moved out of the project - video content was managed with external playback software and sent to vMix via SDI or NDI inputs. After that, things ran much more smoothly.

The fact that vMix can manage so many aspects of a project doesn't mean that it should. In hardware video productions, I've never seen anybody attempt to send 200 inputs to an AnalogWay or Barco switcher (even if they had that many inputs). Productions are broken down into manageable units and responsibility given to separate hardware/operators. In other words, delegate as much as possible to other systems so that vMix can use its resources for the cameras and virtual sets.

As to the Streamdeck - I don't use the internal vMix shortcut tool; instead I use the Bitfocus Companion software to manage the stream deck and it has been very reliable. Since it can communicate with other software/hardware on the network, it can also simplify complex switching by adding multiple commands to one button. For example, you can cue video content in your external playback software, send that input to preview in Vmix, unmute the audio on that input, and then hit take.

Oh, and finally, maybe see if you can simplify your virtual sets - do you need all the layers? Can any layers be reduced in resolution ? Each extra virtual set we added to the project added to the GPU load, so be careful with the number and complexity of those inputs too.

Hope that helps.

If you mean for video playback, then a second copy of vMix would be an obvious choice. Otherwise, there are many other software packages out there for video playback - PlaybackPro, ProPresenter, Qlab, etc. Personally, I like Mitti, although it's Mac only, so may not fit into your setup.

YOU can do the Following To reduce GPU Core & Memory Load when using too many inputs.
- Disable high performance inputs option in the settings page and increase your system RAM to to easily accommodate all those inputs. or use a newer RTX graphic cards with enough VRAM to accommodate all those inputs.
- you can load the video inputs in the project but don't put them on autopay mode and pause every one when not used.
- switch to using lower resolution project and inputs. 720p instead of 1080p.