Vmix | Utc Controller Top

What do you want to automate? (Scorekeeping, lower-thirds, audio mixing?)

In the fast-paced world of live streaming and broadcast production, efficiency is everything. Whether you are switching a church service, a sports event, or a multi-camera corporate webinar, your ability to execute actions without looking away from the program feed defines the quality of your show. This is where hardware control surfaces come into play. Among the most popular and ergonomic choices for vMix users is the .

: UTC can monitor vMix inputs/outputs via NDI and manage XML data sources, making it a hub for dynamic content like live scoreboards. Key Components (The "Building Blocks") Button Widget vmix utc controller top

: Ideal for one-person productions to handle technical direction, graphics, and replays simultaneously. Centralized Control

When compared to native web controllers or alternative external layouts, vMix UTC stands out for several reasons: What do you want to automate

: It uses official vMix API commands (shortcuts) to trigger functions like switching inputs, starting/stopping recordings, and updating data in titles. External Data Handling

Click connect; a green status indicator confirms a successful link. Step 2: Designing Your First Layout This is where hardware control surfaces come into play

Automatically swap to a corner bug once the timer hits zero. No Coding Required

It abandons generic grid constraints. You can place color-coded, labeled interactive modules exactly where you need them. This helps you match the physical visual layout perfectly to your specific event's mental map. The Top Building Blocks: Essential UTC Widgets

The interface of vMix UTC is a grid-based canvas where you add interactive components called widgets. Right-click anywhere on the canvas to add them. Button Widget

| Limitation | Workaround | | :--- | :--- | | vMix API latency (~10-50ms) | Pre-roll triggers by 100-200ms for critical cuts. | | Windows system clock drift | Use high-precision NTP with 1-second sync intervals. | | No built-in UTC scheduler | Use external script (Python, Node-RED, or Bitfocus Companion's scheduler). | | Timecode input limited to LTC | Convert NTP to LTC using a dedicated device or software (e.g., LTCgen ). |