The Controlling a live production article set out a four-layer framework: the surface the operator touches, the middleware that orchestrates, the generic protocols and the AV-specific protocols. This second part zooms in on the two top layers, the ones you actually build for an operator setup: the surface and the automation. They are what decides real comfort in operation, far more than the number of devices being driven. The question is not “how many machines can I command”, but “does the operator trigger the right action, at the right moment, with reliable state feedback”.
The operator surface: what you touch
The surface is the visible part of control. Its role is simple: to offer a command that stays readable in a live situation, where a full software interface would be too slow or too dense. The need comes before the choice of object. Several families exist: programmable button surfaces, touch interfaces, PTZ joysticks and control keypads. Among the tools commonly seen: Stream Deck, X-Keys, Loupedeck or TouchOSC.
The operator’s need points toward one family of surface rather than another.
| Operator need | Suitable surface |
|---|---|
| Trigger simple, visible actions | Programmable button surface |
| Drive variable parameters | Surface with dials or a MIDI controller |
| Build a custom interface | Touch tablet or web interface |
| Manually follow a PTZ camera | Dedicated PTZ joystick |
| Critical, long-duration operation | Dedicated hardware panel or a redundant solution |
The strengths of these surfaces are well known: reasonable cost, fast deployment, dynamic buttons, multiple pages, macros and visual feedback. Their limits are less so. Most depend on a computer and a host application, the quality of modules or plugins varies, and robustness does not always match a dedicated broadcast panel. A consumer surface fits a light set or a demonstration perfectly; a critical, long-duration operation deserves a redundant approach or a hardware panel designed for it.
The middleware: the layer that orchestrates
A surface, on its own, does nothing. A button only has value if it triggers something, and it is the automation that turns that press into a sequence of actions across heterogeneous equipment: change an input, recall a preset, start a recording, switch a router. This is the layer the operator does not see, but the one that makes the system coherent. Many users see the surface as the solution, when it is only the visible tip.
Among the automation tools commonly seen: Bitfocus Companion, often used with Stream Deck surfaces in live and AV environments; Central Control, more oriented toward global show control; Chataigne, strong on interactive and creative installations; as well as Node-RED or QLab. These tools do not all depend on a physical surface: several offer an emulator or web buttons usable on a touchscreen, and can be triggered via OSC, TCP, UDP, HTTP, WebSocket or Art-Net. The detail of those protocols is the subject of the third part of the series.
It helps to separate two notions that are often confused. A macro chains actions in a fixed order. Automation adds logic: conditions, variables, state feedback, timings, different scenarios depending on context. This nuance explains why a simple programmable button is not always enough for reliable live operation, and why the middleware layer deserves as much attention as the surface.
Live software APIs: the target of the commands
Modern live production software often exposes a network API. It is through this API that an automation tool changes a scene, starts a recording, retrieves a state, drives an overlay or triggers a production action. The surface sends the intent, the automation translates it, the software’s API executes it.
As for examples, OBS is automated via WebSocket, vMix exposes an HTTP API and a TCP API, and mimoLive relies on its built-in web server and its HTTP API. Ports, authentication methods and available functions should always be checked in each software’s documentation and in the version actually used. For how these tools position relative to one another, see the Live production software article. These APIs are powerful, but they open network access into the heart of the control room: securing them is not optional, and is covered in a dedicated section below.
Macros and state feedback: the real subject
This is where the difference plays out between a setup that works in a test and a solution that is usable live. A macro is a button that chains several actions: change an input, recall a preset, start a recording, turn on a tally. That is already comfortable. But the decisive point lies elsewhere: state feedback.
A good button does not just send a command, it reflects the real state of the machine or the software. The record button lights up when the recording is actually running, not when it was pressed. The scene button shows which scene is on air. Without that feedback, the operator works blind, and the slightest desync between what they believe and what is happening becomes a risk in a live show. This is exactly the value automation tools add on top of a plain macro: variables, visual feedback, states reported back from the equipment. The trap raised in the previous article, “it responds” is not “usable live”, takes on its full meaning here: a button that fires blind is not the equal of a button that knows.
A concrete build example
Let us return to the training room mentioned in the pillar article. A button surface is connected to an automation tool, which drives both the live software and a PTZ camera. A single “start” button recalls the camera preset, switches to the right scene, starts the recording and turns on the tally. The operator, often a trainer with no technical background, sees only one button.
The point is not just to save steps. The other buttons reflect the state of the system: at a glance you can see whether the recording is running, which scene is active, whether the camera is on its preset. The day the person changes, handover stays possible because the interface says what is happening. This is the logic to aim for, regardless of the brands chosen: a readable surface, an automation that orchestrates, and state feedback that reassures.
Implementing it cleanly
A reliable operator setup is built like a real control room, not like a hack that happens to work on demo day. A few principles come back every time: a dedicated control network, ideally on a VLAN separate from the video network; fixed IP addresses or DHCP reservations so the machines find each other again after an outage; clear documentation of the ports and protocols used; and serious testing before every live show. Behaviour after a reboot deserves a specific check: do sessions and connections re-establish on their own, or does everything have to be relaunched by hand?
Security closes the list, and it is often neglected. Control interfaces are protected like the rest: limited access, passwords when the equipment allows it, and no direct exposure to the Internet. For remote access, go through a dedicated VLAN or a VPN, never through a port opened to the outside.
Finally, a simple reflex avoids many cold sweats: backing up profiles, button pages, mappings and automation configurations makes it possible to quickly restore an operator setup in case of a computer change or a failure.
In short
The surface is the visible part of control, automation is the layer that holds it all together. But neither is worth anything without two things: the protocols they drive and reliable state feedback. A successful operator setup always starts from the field need, chooses the surface accordingly, hands orchestration to an automation tool, and checks that every button reflects the real state of the machines.
That leaves the most technical layer, the control protocols themselves. VISCA, OSC, NDI® PTZ, ONVIF and the others are covered in the AV control protocols reference guide, in the Support area.
In this series
- Controlling a live production: the 4 layers of AV control
- Control surfaces and automation: from button to action in live production
- AV control protocols: VISCA, OSC, NDI® PTZ, ONVIF and the rest
To connect this operator setup to a production type, see the Solutions pages (broadcast, corporate, sport, education). To identify the right configuration for a project and the matching equipment, the Where to Buy page helps find a reseller, or get in touch for a technical discussion.