You are not logged in.

#1 2024-01-04 16:51:06

Roark
Member
Registered: 2023-11-30
Posts: 7

Elgato Stream Deck Pedal mystery inputs

Hey there. I did a new Arch install yesterday. The install was straightforward and things are up and running smoothly; it's not my first Arch install as I ran it as my daily driver during college. I have a post-install question that I'm hoping to get some assistance with. It's a pretty niche problem that I've not experienced on other OSes/distributions, so I'm not even sure really where to look.

For full(-ish) context, my setup is configured as follows:

  • 1TB NVMe SSD with unencrypted boot partition and encrypted BTRFS partition.

  • Other hardware is AMD 5800X3D CPU, AMD 7900XTX GPU, 64GiB memory if that matters at all.

  • I'm running KDE Plasma/Wayland.

I use an Elgato Stream Deck Pedal for push-to-talk in Discord. I wrote a really simple program for binding the different buttons to different keys and generating those keypresses via a virtual input which then gets routed to Discord through KDE's Xwayland support. I noticed that when using the pedal on Arch Linux each button generates "UNK248" when not running my own program, which appears to be KEY_MICMUTE. When running my program, it is KEY_MICMUTE + whatever else I have bound. I cannot for the life of me figure out where that key mapping is actually coming from. Is there any way to determine if a separate program is generating those presses or if it's somehow coming from just the pedal itself? It's not the end of the world if it stays that way since I can work around that, but ideally I can get rid of those extra presses altogether.

Any help is appreciated!

Offline

#2 2024-01-07 00:00:23

Roark
Member
Registered: 2023-11-30
Posts: 7

Re: Elgato Stream Deck Pedal mystery inputs

One additional installment to this mystery. I updated the firmware for the pedal via a Windows VM. When I then went to use it on my Fedora machine, it was also sending key code 248. This happened because my systemd service for sending the key codes I want crashed when the firmware updated (somewhat expected). When I restarted the service it began sending the correct key codes. It seems like on Arch that it is still sending the default key code and the mapped key code no matter what, and that's what I cannot figure out.

Offline

Board footer

Powered by FluxBB