companion VS AutoHotInterception

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

You can achieve that with Autohotkey and AutoHotInterception, which allows you to capture keypresses at a driver level from a specific input-device. I used that for turning a bluetooth numpad into a little macro pad.

I've had some good experiences with using Luamacros to intercept a second keyboard and forward the keypresses to autohotkey like this: https://miquelvir.medium.com/secondkeyboard-1c39e52e023b

Apparently there is also this: https://github.com/evilC/AutoHotInterception

AutoHotInterception might be a workaround for this. The docs cover how to do everything.

This may be what you're looking for: https://github.com/evilC/AutoHotInterception

I believe this is what you're looking for. Sorry, I haven't tried it yet.

I haven't used it yet, but I found AutoHotInterception which uses an "interception" driver to get you hotkeys with a lower level of keyboard interception - this will likely work for Dosbox, though it might be a bit excessive. I'll play around with it tomorrow and see how it works.

I would suggest using an alternative shortcut as CTRL+ALT+DEL is not something you generally want to mess with - but this library https://github.com/evilC/AutoHotInterception may help you achieve your goals, it is capable of blocking the input of ctrl+alt+del...

AHK can't differentiate between keyboards by itself. You need to use AutoHotInterception to find out which keyboard sent the data.

I used AutoHotInterception for making a cheap little bluetooth numpad into a macropad.