I use BlindAssassin's "Blackheart" PCB. (This is called omnikey_bh in the QMK repositories). I've usually ran it with Soarer's firmware, because I like being able to change the keymap and build macros without installing AN ENTIRE FREAKING LINUX DISTRIBUTION AND CROSS COMPILATION TOOLCHAIN.
However, my KVM doesn't like it much. It seems like it was dropping keystrokes, and it was definitely ignoring its built-in hotkeys, so I tried QMK looking to find workarounds or at least a different implementation which was less corner-casey.
QMK does seem to be more reliable-- I can put it into 6KRO only mode and then it recognizes the hotkeys fine, and it doesn't seem to be as prone to dropping keys. But what's odd is how much brighter the lock LEDs are than on Soarer's firmware. I suspect that Soarer's firmware probably strobes the LEDs at less than 100% duty cycle or something.
While there's a billion options for light adjustment, they seem to be mostly for the ornamental lighting-- the basic lock lights feel like an afterthought. It looks like the common implementations literally just turn on a bit on the controller output, so of course it's nuclear-bright. Is there a more subtle alternative available? It looks like the docs mention PWM-LED controls, which could potentially be used to control brightness, but there's no clear way to independently control several such LEDs.
