keylight-control VS companion

10 sec of googling says: https://github.com/justinforlenza/keylight-control

environment.systemPackages = with pkgs; [ (appimageTools.wrapType2 { # or wrapType1 name = "Beeper"; src = fetchurl { url = "https://download.beeper.com/linux/appImage/x64"; sha256 = "sha256-9xQJb1yKgaTpXr0WdPH9pZbOkau4kHFMuhCrFiIz5os="; }; }) (appimageTools.wrapType2 { # or wrapType1 name = "keylight-control"; src = fetchurl { url = "https://github.com/justinforlenza/keylight-control/releases/download/v0.1.6/Keylight_Controller-x86_64.AppImage"; sha256 = "sha256-CM/yo9xzPUrfd+de2QhwbSk2LtcT8m9RT/AHTBKmr0Y="; }; }) ]

Or use Companion to control the Hyper Decks/ Ki Pros….

Still interested in other solutions, particularly a built-in function. I found this feature request on the Companion Github page. I'm not sure though if that is talking about using Companion buttons to trigger hotkeys, or the other way around (as the 2 linked issues seem to be about).

We use Companion on every show—can’t remember how I did one without it. As long as the gear you are using is supported, you can’t go wrong. Very easy to setup and use. Highly recommended.

Can probably do this with Companion. Often used with stream deck but works with a phone too afaik.

Companion is a great way to approach complex macros like these. Basically you'd stack several actions to your one button, like this:

I use a Stream Deck daily to control AV production gear using BitFocus Companion (https://bitfocus.io/companion). I am constantly surprised at the range of supported equipment.

Complex operations that used to take three people can be done by a single person.

For a basic example:

Audio operator fades out background music and brings up video playback audio channels

https://bitfocus.io/companion and a StreamDeck would be a fast/cheap solution. Integrates directly with ETC console so you can use tge existing cues and patching.

Good for macros and help making complex things easier with ATEM https://bitfocus.io/companion