Skip to content

How It Works

Controll3r separates observation from control. The operator sees the target's real video output through a capture device and sends keyboard and pointer input through the Controll3r Interface, which the target sees as ordinary USB input hardware.

Controll3r connection diagram

The Operator Side

The operator computer runs the Controll3r Windows application. It owns the live console, capture settings, audio monitoring, screenshots, recordings, macros, snippets, saved sessions, and optional REST API.

The installer is self-contained. A separate .NET installation is not required.

The Video Path

The target's HDMI, SDI, or other supported video output is connected to a compatible capture device. Controll3r supports common standards-compliant USB/UVC capture devices and a native Blackmagic DeckLink path when Blackmagic Desktop Video is installed.

Video and supported audio are received by the operator computer. Controll3r can display the live feed, take PNG snapshots, record MP4 files, run OCR against selected regions, and measure target-input-to-captured-frame latency.

The Input Path

The Controll3r Interface connects to the operator computer on one side and the target computer on the other. The target sees ordinary USB keyboard and pointer devices, so control works before the target operating system is running and without installing a target driver.

Live operation uses relative mouse movement for natural control. Automation uses an absolute pointer device for exact clicks and repeatable macro playback.

Visual Anchor Automation

Recorded macros can use fixed positions or Visual Anchors. A Visual Anchor is a small image captured from the target screen. During playback, Controll3r searches the current target image for the anchor and acts at the matched location.

This allows automation to wait for screens, choose paths, repeat work, and stop safely when expected visual conditions are not met.

Local-First Operation

Core workflows run locally on the operator computer. The target does not need a Controll3r account, target network connection, or target-side service. The optional API runs on the operator computer for local or LAN automation.