We run a two-operator setup for live sports: one person switching on vMix, one handling instant replay. Splitting the roles was a big improvement, but the mouse turned out to be the sticking point. The replay operator needs it to select and trim events (a StreamDeck alone can't multi-select, as far as we can tell), and the director needs it constantly - so we were taking control from each other mid-show.

What we ended up doing: each operator has their own mouse and keyboard with independent cursors on the same Windows desktop (we use MouseMux for that part). Same vMix instance, the replay operator works in the replay window on their own monitor, and the director never loses their pointer. No second machine, no NDI round trip, and the whole chain gets tested in rehearsal.

Curious how others here handle it:

- Two machines with the cameras NDI'd across? Most threads seem to point that way, but it doubles the failure surface and the camera routing gets fiddly on a smaller budget.

- StreamDeck + Companion only, no mouse? Is anyone genuinely happy trimming replay without a pointer?

- Anyone else running two cursors on one box - what falls over for you when you add operators?

The reason I'm asking: we'd like to add a third operator for audio, and I'd rather learn where this stops scaling from someone who's already hit the wall than find out during a live show. If you've been down this road, what would you do differently?