filco majestouch2 keyboards polling rate

[adsfpoi]

hello geek hacks

I was so curious about do all filco's majestouch 2 keyboard support 1000hz polling rate?

so I just signed up to ask this question..

do all filco's majestouch 2 keyboards support 1000hz polling rate? or only pink edition and the camflouge edition. (trying to figure out so i can buy the ninja version)

i assume ps/2 will be 125 but i want know the usb polling rate!

thank you so much for reading this I hope I get an clear answer and proof!

p.s I know it's gimmick for keyboards it's just my preference guys..

[frosty]

they all should iirc, and polling rate above 500hz does not matter _in my opinion_

you won't really feel the difference that you would feel between an 500hz and 1000hz mouse (yet the difference for this case is really minuscule)

[Bucake]

i think the easiest way to find out would be to get confirmation from an official / a representative. (dunno where you'd have to go to find one, though.)
most filco owners probably don't have the means to test their keyboard for report rate themselves.
there's a driver ("sweetlow hidusbf") that can "overclock" your usb port, but whether it works or not still depends on the keyboard. it's safe to try, but you'd still need something to test if it's working or not )

[tp4tissue]

i think the easiest way to find out would be to get confirmation from an official / a representative. (dunno where you'd have to go to find one, though.)
most filco owners probably don't have the means to test their keyboard for report rate themselves.
there's a driver ("sweetlow hidusbf") that can "overclock" your usb port, but whether it works or not still depends on the keyboard. it's safe to try, but you'd still need something to test if it's working or not )

Just because the cpu polls the board,  doesn't necessarily mean the board will respond at that rate.



But,  before we go down this rabbit hole..


The important fact remains,  Games do not care..

[Tactile]

If you're going to be slicing things so fine as to be worried about polling rate you should just buy a Topre keyboard.

Every Cherry MX board, and others with mechanical switches switch contacts, have de-bounce time programmed into the controller. This will be a minimum of 5 ms and could be a much longer time. And you'll have a very difficult time getting that info from any manufacturer.

Topre keyboards have no de-bounce since it's not needed due to the type of switch.

[Bucake]

Just because the cpu polls the board,  doesn't necessarily mean the board will respond at that rate.

that's what i said

Topre keyboards have no de-bounce since it's not needed due to the type of switch.

but it might be reporting at 125hz. it depends on the firmware, not the tech. the specs don't seem to mention what rate it's reporting at (hhkb / realforce)

edit: debouncing / release times aren't OP's concern i think, he just wants the key press to register as soon as possible, which would mean he wants 1khz report rate and not necessarily low debounce times

[adsfpoi]

If you're going to be slicing things so fine as to be worried about polling rate you should just buy a Topre keyboard.

Every Cherry MX board, and others with mechanical switches switch contacts, have de-bounce time programmed into the controller. This will be a minimum of 5 ms and could be a much longer time. And you'll have a very difficult time getting that info from any manufacturer.

Topre keyboards have no de-bounce since it's not needed due to the type of switch.

so you are saying realforce topre keyboards have 1000hz polling rate? and better responsiveness? than cherry? if this is true, i'll get it right away!

[Tactile]

debouncing / release times aren't OP's concern i think, he just wants the key press to register as soon as possible, which would mean he wants 1khz report rate and not necessarily low debounce times

What I'm saying is that it's nonsensical to consider polling rate & not also consider de-bounce time. Let's say a keyboard has a 1000 hz polling rate, and a completely plausible de-bounce time of 8 ms. That keyboard is now effectively a 125 hz keyboard. No matter the polling rate, no keypresses will be reported any faster than 125 hz because the keyboard sits twiddling its thumbs for 8 ms at each keypress.

...anyway... Happy Labor Day to folks in the US and happy Monday to everyone else...

...seeya

[Rayoui]

What I'm saying is that it's nonsensical to consider polling rate & not also consider de-bounce time. Let's say a keyboard has a 1000 hz polling rate, and a completely plausible de-bounce time of 8 ms. That keyboard is now effectively a 125 hz keyboard. No matter the polling rate, no keypresses will be reported any faster than 125 hz because the keyboard sits twiddling its thumbs for 8 ms at each keypress.

While this is true, you can still have added delay from a slower polling rate since polling happens on a set interval. Assume a keyboard with a polling rate of 125 hz registers a keypress (after an 8 ms debounce delay) 1 ms after the CPU last polled. You now have to wait an additional 7 ms for the next polling cycle with a total delay of 15 ms. In this case, a 1000 hz polling rate would have effectively halved the delay of the keypress.

Whether or not this would even be noticeable to the user remains up for debate. Once you factor in other delays (i.e. I/O, display response time, etc) it becomes even less of an issue. But, I digress.