Skip to content

Frequently asked questions

Is Controll3r remote desktop software?

No. Remote desktop software depends on a running, cooperating target operating system. Controll3r controls real USB input hardware and watches the target's real video output.

Does anything need to be installed on the target?

No. The target sees ordinary USB keyboard and pointer devices plus its normal display connection.

Does the target need a network connection?

No. Local operation needs no target network. The optional API runs on the operator computer.

Can it control BIOS, UEFI, and boot menus?

Yes. Those are primary use cases because input and video do not depend on the target operating system.

Which Windows versions are supported?

Windows 10 version 1809 (build 17763) or later and Windows 11, x64. This compatibility floor does not extend Microsoft's support lifecycle for a particular Windows edition.

Do I need to install .NET?

No. The MSI is self-contained and includes the required runtime.

No. Controll3r supports common standards-compliant USB/UVC capture devices. DeckLink is an additional native path for operators who need its signal support and lower-latency characteristics.

Will every USB capture device work?

No universal guarantee is possible. The device's Windows driver must expose a compatible source format. Latency and supported modes vary by model, firmware, driver, USB controller, and source.

How much latency should I expect?

On our reference bench (a DeckLink card capturing 4K30), the live picture typically trails the target by roughly 20-30 ms, and the built-in Latency Test — which measures from a sent input to the change appearing in the captured frame — commonly reports medians in the 60-130 ms range. Treat these as reference points, not guarantees: your results depend on the capture device, its driver, the operator GPU, the target hardware, and the signal mode. USB capture devices vary widely. Every install includes the Latency Test, so you can measure your own setup in minutes instead of trusting ours.

Native DeckLink access depends on Blackmagic Desktop Video for Windows. Its driver/runtime is supplied and licensed by Blackmagic and is not redistributed inside Controll3r.

Usually not. Capture hardware commonly permits one active client. Close Media Express before using the card in Controll3r.

Can I use Controll3r without the Controll3r Interface?

You can inspect compatible video and some local tools, but target keyboard and pointer control require the Controll3r Interface.

What is the default way to release captured input?

Hold Left Ctrl and Left Alt together. The chord is configurable and is shown on screen when capture begins.

Why is the automation pointer separate from the live mouse?

Live driving benefits from low-latency relative movement. Macros need exact, position-independent clicks, so they use a separate absolute pointer device.

Does Paste use the target clipboard?

No. Controll3r translates text into real keyboard input. This works even when the target clipboard or operating system is unavailable.

What happens to characters the target layout cannot type?

Typographic punctuation is normalized where possible. Other untypable characters are skipped by default and reported without stopping the entire paste. Strict stop-on-untypable behavior is optional.

Does OCR run in the cloud?

No cloud service is required. OCR uses the Windows OCR capability on the operator computer.

Are macros just recorded coordinates?

They can use fixed coordinates, but the main automation feature is Visual Anchoring: Controll3r captures a small image and searches for it during playback.

Does Visual Anchoring recognize color?

Yes. Matching uses color evidence, not only grayscale brightness.

Will a Visual Anchor macro work at another resolution?

Not automatically in version 1. The playback capture resolution and format must match the recording context. Restore that context or recapture the affected anchors.

Can a macro wait forever?

A wait can: a wait timeout of 0 means no timeout, by design, so a macro can watch for a condition indefinitely. Use a positive timeout and timeout recovery while developing unattended workflows. Repeat blocks are governed separately — they always carry safety limits so a looping macro cannot repeat endlessly by accident.

Can a person intervene during a macro?

Use a Wait For Operator block. It pauses automation, returns deliberate control, and resumes after confirmation.

Can Wait For Operator run headless?

No. A headless process has no person or UI to answer the prompt, so that macro is rejected.

Can I share macros?

Yes. Each .c3rm is a portable bundle containing the macro and its Visual Anchor images. It may contain recognizable target-screen content, so review it before sharing.

Can the API run over a LAN?

Yes. LAN mode uses HTTPS with a local self-signed certificate and requires a bearer token on every endpoint except health.

Is the API enabled by default?

It is disabled by default in normal UI mode. Headless mode forces the API on because it is the control surface for the background host.

Can I run the UI and headless mode simultaneously?

Not as independent hardware owners. The UI can take over from headless mode, then optionally restart the previous headless launch mode when the UI exits.

Where are screenshots and recordings saved?

By default, snapshots go to Pictures\Screenshots and recordings go to Videos. Both can be changed in Preferences.

Does uninstall remove my macros and settings?

Preserve is the default. The current installer's optional delete action removes the local-data folder containing macros, snippets, shortcuts, logs, and webserver files. Roaming settings and saved sessions under %AppData%\Controll3r remain and must be removed separately if a complete cleanup is required.

Is macOS or Linux supported?

Not as an operator platform in the current release. The shipping application is Windows x64.

Is Controll3r open source?

No. The application is proprietary and All Rights Reserved. Third-party components remain under their own included licenses.

Where should I report a problem?

Use the seller-provided support channel for the release you purchased. Include the version, copied diagnostics, relevant log excerpt, hardware/driver details, and exact reproduction steps. Support contact: [email protected].

Is the Controll3r Interface included with a purchase?

Packaging details are coming soon. Target control requires the Controll3r Interface and a compatible capture path.

Is there a trial or evaluation version?

Evaluation and trial terms are coming soon. Contact [email protected] if you are evaluating Controll3r for a lab, deployment, recovery, or firmware workflow.

How many target machines can I control?

One target at a time per operator setup — the Controll3r Interface and capture device connect to one machine. Macros make repeating the same work across many machines fast: move the two cables, run the same macro. Multi-seat licensing terms are coming soon.