companion VS input-leap

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

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.

I'm already using waynergy with input-leap as my main way to control the laptop when it is docked. It is amazing.