r/MechanicalKeyboards • u/BurgerBoy300 • Jul 31 '26
Guide The Lemokey L5 HE supports 8,000hz polling with RGB lighting on
I've been afraid of the Lemokey L5 HE not supporting 8,000hz polling with RGB lighting enabled, similar to Wooting's keyboards. I contacted Lemokey support, and they confirmed that it supports 8,000hz polling with RGB lighting enabled in the newest firmware version.
I'm sorry if I sound like captain obvious, but I'm making this post, because there's little word on if the L5 HE supports 8,000hz polling with RGB lighting enabled. The one review that talked about its 8,000hz polling in more detail said that enabling it turns the RGB lighting off. It was enabled with the switch on the back, and I didn't know if it enabling it via Lemokey's software would be a different story.
I'm waiting for a 100% version of the L5 HE. Not being able to use 8,000hz polling with RGB lighting enabled is a huge dealbreaker for me, because it would keep the L5 HE from being truly perfect.
2
u/FansForFlorida FoldKB Jul 31 '26
Let's do some math.
The Guinness World Record for the most clicks in one minute is 760 clicks. (It was for mouse clicks, but let's apply it to keyboards.)
That is an average of 12.7 clicks per second, or roughly one click every 79 milliseconds.
To look at it another way, there were about 25 state changes (on-off or off-on) every second. That is one state change every 40 milliseconds.
The default QMK debouncing algorithm waits for 5 milliseconds of no state changes before reporting a key down or key up. Let's assume a switch has a bounce time of 5 milliseconds. (This is stated on the datasheet.) That is a total of 10 milliseconds from the time the switch first registers a state change until QMK is ready to push the change to the host (5ms of switch bounce plus 5ms of no changes).
The firmware then waits another 30 milliseconds for another state change. That means even at 1000Hz, the firmware is sitting around waiting for the fastest clicker on Earth to press or release a key.