Companion is a control bridge
It lets one button trigger actions across ATEM, OBS, vMix, Zoom, media players, lighting, audio tools, and other network-controllable systems.
Control Knowledge
What is Bitfocus Companion, and when does it need a real hardware surface?
Companion is useful because it turns many separate production actions into repeatable buttons. The buying question is whether your team needs a simple macro helper, or a dependable control workflow for live operation.
Quick Answer
Companion connects actions. Hardware makes those actions usable during a show.
Macros need a visible surface
The software logic is powerful, but live operators need a physical layout they can trust under pressure.
Workflow matters more than button count
A good Companion setup maps the repeated moments of a show, not every command the software can technically execute.
Common Uses
Where Companion usually creates value
ATEM switching
Recall camera cuts, transitions, keys, supersource states, and repeatable show moments.
OBS or vMix production
Trigger scenes, overlays, recordings, stream actions, and utility commands from one surface.
Church and education
Give volunteers simple buttons for service start, slides, camera views, streaming, and recording.
Small studio shows
Run opening, talking-head, guest, break, and closing states without hunting through windows.
1234 Model
The risk is adding complexity before the workflow is proven.
Companion can control many things, but the first judgment should be simple: which repeated show moments deserve physical buttons because they reduce mistakes or save operator time?
- Start with the show flow: opening, camera cuts, slides, lower thirds, break, ending, and emergency states.
- Put the most repeated actions on the clearest buttons.
- Keep volunteer layouts simple; advanced operators can handle deeper pages and custom logic.
- Test the layout with the actual operator before adding more macros.
- Only expand the system after the basic weekly workflow is stable.
Product Direction
Choose the AVCLUE panel by workflow width
Good Fit
Use Companion when actions repeat every show.
- One operator must trigger several systems quickly.
- Volunteers need a simpler button layout than software menus.
- The same show sequence happens weekly or daily.
- ATEM, OBS, vMix, graphics, recording, and streaming need coordination.
Not First Priority
Do not build macros before the basics are stable.
- If camera signals are unreliable, fix signal flow first.
- If audio and streaming settings change every show, document the core workflow first.
- If there is no fixed operator role, the button layout will be hard to maintain.
- If basic ATEM switching is enough, start smaller.
Next Pages
Move from learning to setup choice
FAQ
Common Companion questions
What is Bitfocus Companion used for?
Bitfocus Companion is used to trigger actions across production devices and software from buttons, macros, and control surfaces.
Do I need Companion for ATEM?
Not always. ATEM can switch by itself, but Companion is useful when you want repeatable actions across ATEM and other tools such as OBS, vMix, graphics, recording, or streaming.
Is Companion only for Stream Deck?
No. Stream Deck is common, but Companion workflows can also benefit from dedicated production hardware when operators need a more robust or specialized surface.
Which AVCLUE controller fits Companion workflows?
KD50B fits focused ATEM + Companion workflows. KD50X fits mixed ATEM, vMix, and OBS workflows. KD60A2 fits wider production-control setups.