Controlling Presentations Inside a vMix Production

vMix presentation control is the part of a live broadcast that most switcher operators dread: a slide deck running as an input, and someone needing to advance it without touching the wrong window or stealing focus from the program bus. Most productions solve it the same way, a second person sat next to the operator with their hand on the arrow keys, hoping nobody bumps the mouse.

There is a cleaner way to do it, and it does not involve sharing a keyboard mid-broadcast.

Why slide control breaks inside a vMix production

vMix runs your whole show: cameras, overlays, audio, replay, and often the slide deck as a capture input. The operator is already juggling scene cuts and transitions. Handing them a clicker too means every slide advance competes for their attention with the actual switching.

The usual workarounds:

• A second operator with a keyboard, sitting close enough to reach, breaking focus every time a slide needs to move.
• The presenter walks to the booth, which does not work for remote speakers or big rooms.
• A hardware clicker aimed at the wrong machine, because the deck is running on the production PC, not the presenter's laptop.

None of these scale past a one-camera, one-operator setup, and all three add a point of failure that has nothing to do with the actual content of the show. The fix is not a better clicker, it is giving the presentation a control path that does not depend on being in the same room as the switcher.

Native vMix control, not keyboard simulation

Cliqer's desktop app talks to vMix directly through its COM API on Windows, so a presenter's click sends a real command (NextItem, PrevItem, SelectIndex) rather than a simulated key press. If the API call fails for any reason, Cliqer falls back automatically to simulating the Left and Right arrow keys, so control keeps working either way. See the vMix integration docs for the full command list.

That distinction matters in a live show: a direct API call does not depend on which window happens to have focus, so the operator can be mid-transition in vMix while a presenter or remote speaker advances their own slide independently.

How to set it up

Bringing remote guests into the mix, not just slides

A vMix production often needs more than slide advance. Remote panellists, Q&A guests and hybrid speakers all need to get into the program feed cleanly. Cliqer's Studio window turns the desktop app into a compact vision mixer: displays, cameras, NDI sources and callers all become inputs you stage on Preview and cut to Program, then send to vMix over NDI, one source per caller, exactly like a local camera. In Cliqer 3, Studio adds a full mixer with routing, running in 32-bit floating point so nothing clips inside the mix: add your own Groups and Returns on Pro and above, and each NDI output picks any bus by name, so vMix can take a dedicated caller mix while the room hears its own. Cliqer 3 also keeps Program frame rate, GPU and CPU load in view in the status line, so you can watch the feed you send to vMix as it runs.

That means the same Cliqer room that advances your speaker's slides can also deliver a remote guest's camera and mic into your production, without a separate video-call rig for panel discussions. For the timer overlay, the same NDI output that feeds callers also carries the countdown clock.

Keyboard sharing vs native control

Who this actually helps

Native vMix presentation control shows up differently depending on the size of your crew:

• Solo presenters running their own vMix rig can control scene transitions and slide advance from their phone while presenting, with no separate operator at all.
• Multi-camera productions can free the switcher operator entirely from slide duty, so they only handle camera cuts, lower thirds and overlays.
• Touring crews running the same show across several venues get a control path that does not depend on a specific clicker being in the truck.

Combine vMix control with multi-host setup and you get a second control station ready to take over on a mission-critical broadcast, not just a backup slide clicker but a genuine second host that can drive the same room if the primary machine has a problem.

Troubleshooting a production day

If vMix is not being detected, confirm it was running before Cliqer started, and that either the 32-bit or 64-bit build (vMix.exe or vMix64.exe) is installed correctly, since Cliqer checks for both. If commands stop responding mid-show, the fallback keyboard mode still needs vMix to have window focus, so check nothing else has grabbed it, and confirm no other application is holding exclusive access to the COM object.

For crews already running a Stream Deck or Bitfocus Companion at the desk, slide advance, timer control and caller cuts can sit on the same panel as your scene buttons, so vMix control stops needing its own separate tool. Teams running the same rig across rental and staging jobs get the added benefit of one setup that travels between venues instead of a bespoke bridge per show.

FAQ

Try it on your next production

If your team is still passing a keyboard back and forth during a live show, download Cliqer free and test native vMix control on a rehearsal before it matters on air. For productions that need pooled seats across a touring rig, compare Pro, Max and Ultra, or see how AV crews run the whole show from one tech table.