Companion — Presentation Commander Server
ReleasedBitfocus Companion module: route outputs, recall scenes, blackout, send stage notes and drive next/previous slide from a Stream Deck.
Discipline
Our applications, on a Stream Deck button.
Bitfocus Companion is how a great many show-control surfaces actually get built: a Stream Deck, a rack of buttons and a piece of open-source software in the middle that knows how to talk to everything else in the room. A module is the piece that teaches it one more application.
Eleven of ours have one. They are small on purpose — each is a connection to an existing control interface the application already exposes, so there is nothing extra to install on the application side and nothing to go out of step when the app updates.
16 projects · 15 with builds to download
One per application, all MIT, all released.
Bitfocus Companion module: route outputs, recall scenes, blackout, send stage notes and drive next/previous slide from a Stream Deck.
Bitfocus Companion module for OSC control of the Presentation Commander client.
Bitfocus Companion module for OSC control of PDF Presenter.
Everything else with a module.
Bitfocus Companion module for animATEM.
Bitfocus Companion module for Atem Overseer fleets.
Bitfocus Companion module for the BlackMatrix crosspoint router.
Bitfocus Companion module for caspar-AV shows.
Bitfocus Companion module for flock decoder fleets.
Bitfocus Companion module for Kestrel — drive region-to-output routing from a Stream Deck.
Bitfocus Companion module for Analog Way LivePremier, driven by Mynah command syntax. One action takes any command, and a library of well over a hundred presets, plus a command builder, populates a Stream Deck with memory recalls, takes and stores.
Bitfocus Companion module for Analog Way LiveCore and Midra video processors.
Bitfocus Companion module for RFutils monitoring.
Bitfocus Companion module for OSC control of SimpleCue.
Bitfocus Companion module for the srt-router crosspoint.
Bitfocus Companion module for WebLinked.
A replacement operating system for the BirdDog PLAY that turns it into a Bitfocus Companion appliance: the Companion server, its admin interface on the unit's own HDMI output, and USB control surfaces plugged into its port. It is not a patch — it replaces the firmware, so the unit stops being an NDI decoder until it is flashed back. Only two partitions change, which leaves both recovery paths intact. 808 Companion modules ship in the image, so it works with no network on first boot.
None of these are in the official Companion module store — each is installed as a developer module, by pointing Companion at the checked-out repo. That is a distribution status rather than a quality one, and it is the first thing you need to know, so it is here rather than three clicks in.
It also means you can read exactly what a module does before you let it near a show. They are a few hundred lines each: the actions, the feedbacks and the variables, and a connection to a documented interface.
Because the control interface belongs to the application, not to the module. The presenter apps listen for OSC on their own ports and the master server exposes a JSON-RPC automation API over HTTP — those are the real interfaces, they are documented on the applications' own pages, and anything that can speak them can drive the app. The module is a convenience, not a dependency. Nothing here is the only way in.
The practical consequence is that a module cannot break the app it drives, and that if you would rather drive it from QLab, a show-control processor or a script, you are not locked out. The modules simply save you writing that yourself for the most common surface in the industry.
The whole catalogue
The full index carries every project at once, searchable and filterable by discipline, type and how finished it is — including the disciplines that don't yet have a page of their own.