my teensy+g100s: limited to 1000hz
((( will try to figure out why later.
first, lets look at my other mice
g302: limited to 1000hz yes i checked process parent, and underclocking to 125hz works. probably (unintentionally) firmware limited
logitech's intervals are always quantized to 1ms: http://i.imgur.com/JkQmzOI.png
. probably because there's stuff in the firmware that's like hardcoded to run every 1ms
finalmouse @ 4000 polling: http://i.imgur.com/jEUNbI9.png
finalmouse @ 2000 polling: http://i.imgur.com/5FxMCT9.png
torq x5: limited to 1000hz but unlike logitech's newer mice, the interval isn't quantized to milliseconds: http://i.imgur.com/Jjj2tgs.png
god damn my torqx5's clicks are nice.
kinzu v1: soo close. 2000hz: http://i.imgur.com/tMh8MkG.png
for instance, on my computer, the jitter doesn't differ between 1ms or 2ms polling
but in any program that prints out the hz (e.g. dimr, mouserate, mousemovementrecorder, etc...)
higher polling rates will always appear to have more jitter. this is an illusion due to how the function 1/x is not linear.
for instance if you have 15us jitter, at 1ms polling, mousemovementrecorder would show numbers between 1015 and 985. but with the same amount of jitter at 2ms polling, mousemovementrecorder would show between 496 and 504.
also, the sort of jitter does not affect the data coming out of the mouse at all because the timing of the usb communications is not affected by this. i've checked on my oscilloscope and the jitter of the usb timing there is on the order of nanoseconds, even for my laptop, with power saving and other stuff on which makes the mousetester interval plots look quite bad.