Companion for video: a command and its vMix confirmation

Define the command before designing the button

Record the input to select, its mix and what Program should retain during preparation. Use identification content in a copied preset and a Companion configuration separate from the show for this example.

Companion modules have independent versions. Record the selected version in Connections and read its Help; updating Companion does not automatically update modules. Do not assume an imported configuration preserves every reference.

Connect to the correct workstation

Module 4.2.0 configuration identifies Target host and TCP Port; it refers to vMix TCP port 8099, not the Web Controller port. The vMix 29 TCP manual also documents 8099. When the applications run on different computers, localhost does not identify the other workstation.

Confirm host and control scope with the system owner. Connections status helps check the link; it does not establish the correct input target. Do not expose control to the Internet or change production ports to complete a check.

Prepare a Preview action with matching feedback

Module 4.2.0 documents Input - Send Input to Preview and Tally - Preview state. In a rehearsal configuration, select the same input and mix for both. Label the command clearly and distinguish state feedback from a cosmetic press color.

Review Press and Release: both can contain actions. Start with one Press action in the test configuration, without sequences or Program changes. Check which input reaches Preview in vMix and whether feedback follows when you select another input directly in the application.

Checks when the button does not match expectations

Keep before-and-after states and the observed result at the intended output. A success message or button color alone does not establish playback, audio or physical signal.

• Connected but the wrong input changes? Compare host, selected connection, input and mix. Review references after renaming or reorganizing the preset.
• The command works but color stays unchanged? Check feedback, target and incoming state. Some module information uses polling; not every confirmation is instantaneous.
• One press causes two changes? Inspect Press, Release, additional actions and triggers in the configuration copy to locate the second command.

Presentations: prepare Preview and resume manual control

Example workflow: during a presentation, the operator prepares slides in Preview and another person authorizes taking them live from vMix. The button prepares the input, while feedback shows which input is selected. Before the event, also check what each destination sees and hears.

Identify how to resume manual control in vMix if Companion stops responding. Test recovery in a copy of the preset, off air. If you add a physical control surface, the emulator or a second computer as a fallback, check that you can continue operating from that setup; having it available does not replace the rehearsal.

1. Record versions, module, host and action target without storing private keys.
2. Compare connection state, Preview and feedback after each command.
3. Record how manual control resumes and which tests remain pending.