Event control and automation
Stream Deck XL and Companion: build clear buttons and verify every action
Plan a clear control surface for cameras, playback and compatible systems. We can review your workflow while the event rundown is still provisional.
Model and scope
Stream Deck XL is a USB surface with 32 LCD keys. Companion runs on a host computer and uses connections and modules to control compatible devices; the keypad does not process or switch video itself. Do not confuse it with Stream Deck + XL.
Assign each action to an operator and a target device. Compatibility depends on the device, firmware, module and Companion version; a supported brand does not guarantee every function.
Connections and limits that matter
- Host and surface
- Record the operating system, Companion and module versions, USB connection and surface method. Direct connection, the Elgato plugin and Satellite are different architectures.
- Connections and access
- Identify target addresses, ports and control permissions. Use wired networking where practical; do not expose Companion administration to the Internet.
- Status and confirmation
- Feedback displays state received or calculated by its module. A key color does not prove a file was recorded or an audience received a stream.
Prepare the system in stages
- Export the working configuration and record versions, addresses and dependencies. Test recovery in a rehearsal environment; external images, media and target-device settings may need separate backups.
- Verify direct control of each target first. Then connect its module and assign specific actions, clearly distinguishing preview, cut, play, record and stop. Avoid ambiguous toggles with no state indication.
- Review press and release behavior and any action stacks or delays. Separate critical actions and label targets and states. Repeated presses should not be the automatic response to a delayed device.
- Rehearse the rundown with operators and verify video, audio and files at the actual destinations. Test disconnection and recovery off air; keep a manual control method and an approved configuration backup.
Example event preparation
For a proposed conference workflow, create separate camera-preview, title and playback buttons. Rehearse cue order with the director; an automated sequence does not replace the operator’s go cue.
When a button starts recording, confirm status at the recorder and play back a test sample. Identify button design, integration, rehearsal and live operation separately when defining the scope.
Troubleshooting: find the failing stage
If the table is wider than your screen, scroll it horizontally. You can also use the arrow keys with focus inside the table region.
| Symptom | What to check | How to verify the result |
|---|---|---|
| The surface is missing | Check USB, host and selected connection method; identify which application owns the surface. | Use a rehearsal key with no actions on live devices. |
| The key responds but the target does not | Check module connection, address, permissions and direct device control. | Run a reversible test action and confirm the change at the target. |
| The key indicates success but output is missing | Compare feedback with actual state and the signal or file path. | Check content at the receiver or play the rehearsal recording. |
Frequently asked questions
Does it work without a computer?
The XL surface needs a host and software. Companion must remain running on its host; Satellite supports remote surfaces but still needs that control instance.
Must Elgato software always be closed?
It depends on direct connection versus plugin operation. Choose a documented method for your versions and avoid two applications competing for the same surface.
Can one button perform several actions?
Companion supports stacked actions and delays. Check order, timing and failure behavior; module acceptance does not mean an operation has finished on the device.
Does feedback confirm a successful stream?
It confirms only the state reported or calculated by that connection. Also verify picture, audio, reception and any recording file.
Is a configuration export enough?
It is part of recovery. Also document module versions, addresses, external resources and target settings, then rehearse restoration.
What should I send for an initial inquiry?
Send the target devices, desired actions and who will operate each position. Start with connection photos, a signal list or a preliminary rundown; add the proposed computer, date and venue when known.