Thanks Millions. I really should have taken pictures of the excess lube. It was even on the underside of the plate above the spacebar stabs 
1 Like
The problem you are describing still has to do with debounce delay and I really feel like youāre not understanding what I am saying. 8ms may be equal to 125 Hz, but that is completely irrelevant. There are two settings in the Core app, one for polling rate and one for input latency. Polling rate is given in Hz and you can choose 125, 250, 500, or 1000. In my experience, 250 Hz and above are good, but 125 Hz is a bit low. Completely separate from that is an input latency setting, give in ms, and you can choose 2, 8, or 16. This setting affects not just the input latency but also, unfortunately, the debounce delay. If you set this to 2 ms, you will get double inputs regardless of your polling rate. If you set it to 8 ms, you might be fine (regardless of polling rate). If that still doesnāt work for you, set it to 16 ms. The polling rate specifies how many times per second the computer will poll the device for a change of state; debounce delay, which is part of that input latency setting, specifies how long after an input is registered the keyboard should ignore inputs from the same switch before allowing new inputs.
2 Likes
Both myself and my partner got the GMMK recently and we have the issue with double presses.
I notice it mostly on e and space.
2 Likes
I understand the difference. And when I reported the issue and had the board RMAāed changing the debounce/input latency setting wasnāt an option. When I made my earlier adjustments it was using the only setting available at the time which was the polling rate.
My issue started up after a firmware update (I am assuming they adjusted the debounce setting). After reverting the board to the factory default firmware, the issue was mitigated somewhat, but after some testing it still showed the double/triple presses if you pressed hard enough on the key. Which is why I went the RMA route.
I added the 8ms = 125Hz in case people were curious on how one translates to the other.
I do greatly appreciate you letting me know that there is now a separate setting for the debounce delay!
Now, the discussion of how much effect changing the polling rate has on the performance of any given computer is a completely different matter (Long story short, in modern computers, probably not much )
2 Likes
so is the only resolution to lower ms and lower polling rate?
Iāve tried this and still had the same issues.
A quick google search seems to show ALOT of people having this issue.
I have it with two different GMMK proās and even on the lowest polling and debounce times it still occurs. I flashed one with QMK and it stopped happening.
This is an issue with the Glorious Firmware, they need to fix it. Itās not like itās something that occurs in frequently, as I typed this itās happened over 25 times on my tās, eās and spaces.
Interesting that mine has been occurring on the āeā key as well. Thatās several people in this thread that have identified the same key affected 
1 Like
Low debounce setting will increase the chances of the chattering. Start at the highest and check again. I had a little bit of chatter and was able to resolve it with 8ms debounce. But if you go lower it will qualify the press before the switch settles.
Iāve been experimenting more with this and realized that there is an asymmetrical debounce that uses eager for actuation and deferred for release. That is, when you press a key, it is sent immediately, then it ignores inputs for x ms until you release the key, then it waits x ms before sending the release. I suppose you could argue that this yields higher input latency for key release, but Iām not sure thatās really a problem many people care about. The end result is low latency for actuation, slightly higher latency for release, and similar accuracy to just using deferred debounce. Iām starting to think maybe this is the route Glorious should take.
I was in contact with the support team after I posted.
They confirmed they are aware of the issue and itās not just being treated on an individual device level.
I came here to say this myself. Iām double pressing spacebar recently and Iām not sure why. Need to switch out the keyboard for a bit 
This is pretty frustrating because itās making it hard to execute certain movements in games.
Iām on 1.0.24.
Iāve tried reinstalling everything. And Iām @ 8ms also happens on 16.
For reference in this thread, here are the standard troubleshooting steps we recommend when encountering this issue:
- Is your keyboardās latency currently set to 2ms? If yes, can you please try setting it to 8ms in the Glorious Core?
- Can you try cleaning the PCB and/or switch? This shouldnāt take long and can definitely help you eliminate the issue youāre experiencing.
CLEANING THE SWITCH - Please check the switchās prongs to ensure no debris is stuck to them.- You can use a clean, dry brush without any residue and gently wipe off the prongs. A gentle touch is needed to not bend the pins.
- If this doesnāt help, however you are sure the problem is the switch, you can also try opening said switch and checking and cleaning any debris inside. Again, a clean and dry brush should be used to avoid introducing any material to the lubricant inside the switch
CLEANING THE PCB - Kindly take the GMMK PRO apart and set the PCB separate from the rest of the PRO.
- You can use a Q-tip and the highest level of isopropyl alcohol available at your local grocery store (91% or higher). Simply dip the Q-tip into the isopropyl alcohol, squeeze out the extra liquid, and then gently wipe their PCB to clean it. Minimal liquid is needed. - It should dry almost immediately. Once the PCB is clean and dry, you can rebuild your GMMK PRO.
If you give these a shot and youāre still having issues, please reach out to support and they can assist you further. @Optional not sure if youāve already tried cleaning the PCB and switches, but if so definitely reach out to our CS team.
Iāve been running QMK on my keyboard for a while now and it hasnāt occurred at all. No cleaning/replacing switches etc. I swapped back today to double check and it happened straight away on all debounce settings and polling rates. Swapped back to QMK and instantly gone. I think Iāll stay on QMK until the issue is figured out. I lose RGB control but itās worth it not having to spend all the extra time removing extra characters and spaces.
Here is the guide from glorious on how to flash over to QMK.
Glorious really needs to fix this 
Kinda sucks having the rotary knob and not being able to use it unless I know how to code. Thankfully QMK is here as a temporary solution, but would be nice to have native software from the company.
Were you unable to get the rotary knob to function using our CORE software?
This continues to be an issue despite the suggested fixes and RMA. Seems like either the newest version of core or firmware made it so much worse. I went to QMK for the time being and havenāt had any issues this far