At first I was confused at your comment about quantization noise at lower DPI, because qualitatively it would seem to present itself similarly in the MouseTester graphs. But if I am understanding it correctly now upon further contemplation, the difference is that smoothing is exhibited in the time domain due to averaging of frames while quantization noise is merely the random deviation at a given point in time that corresponds to level of precision in accordance with the DPI...?
yea by quantization noise i mean like
if you're moving the mouse at a speed corresponding to an average of 2.34567 counts every usb report for 400dpi, (ideally) the mousetester plot would ideally show it bouncing between 2counts and 3counts.
if you increase the dpi to 1600, the expected speed would be 2.34567*4 counts every usb report, and ideally mousetester would show it bouncing between 9 and 10 counts.
then if you plot the velocity, that involves dividing by the dpi, so this bouncing is less pronounced for higher dpi
the thing with smoothing is that i'm not completely sure how it works/what it's doing
Smoothing is just more difficult to detect and quantify in the polling data because of its subtlety (except in extreme cases), hence why we can only observe it during more abrupt changes in polling behavior like the two methods in this thread...?
yea and if the timescale is <1ms like for the am010 on g100s or g302/g402 @ >=2080dpi, it's pretty much invisible using these or similar methods.
maybe another way to see smoothing would be to put the sensor out of focus so that the sensor's data gets really noisy, and then compare mspaint lines