Joined
·
1,450 Posts
Interesting!
guess what?about this whole smoothing thing: perhaps it is possible to measure.
i have been measuring input lag by colliding an unwired mouse into my g100s and recording videos at 1000fps. example: https://www.youtube.com/watch?v=IA0T_o9qQVc
if you look frame by frame, it's pretty evident that the g100s reaches its maximum speed essentially instantaneously (~1ms or less). this owes to the rigidity of the plastic shells of the mice; if i used a rubber ball or something soft to hit the g100s, the transfer of momentum would occur over a much longer timescale.
by looking at a mouse's raw output and plotting vs time, it may be possible to detect smoothing
see this diagram for what I mean:
![]()
here is a real plot with MouseTester. i held down mouse1 lightly while slamming another mouse onto the g100s' side.
![]()
it's not perfect though as the mouse could malfunction during the impact. for example, my logitech m100 (a serious piece of ****) shows the following in mousetester:
http://i.imgur.com/L2QSh6i.png
If you want to measure something you have to at least define it.
The main consensus around OCN (Or so it seems) is that Smoothing is best defined as post-processing with noticeable delay in tracking. Common in modern sensors to push such high DPI settings.Originally Posted by FreeElectron
If you want to measure something you have to at least define it.
What i think is a proper definition for smoothing delay is a mouse movement delay that might be caused by excessive processing that may result in abnormal mouse movement.
But that definition is not definitive enough to be able to measure it.
maybe measuring is the wrong word... but what the graph shows is this: http://en.wikipedia.org/wiki/Moving_average#Simple_moving_averageOriginally Posted by FreeElectron
If you want to measure something you have to at least define it.
What i think is a proper definition for smoothing delay is a mouse movement delay that might be caused by excessive processing that may result in abnormal mouse movement.
But that definition is not definitive enough to be able to measure it.
only other mice i have are g100s, wmo, ime3.0, g302, g303, and aurora. the aurora's shell is too soft to get meaningful results (flexes by ~1mm easily, which corresponds to ~2ms of contact time). the rest always respond instantaneous. logitech says g302 has 1ms smoothing above 2000dpi, but you can't really see that as usb polling is 1ms
it's because of framerate/usb polling mismatch. lower dpi has more quantization noise of course, so these periodic spikes are kind of hidden.You can see as DPI increases, so does the distinctiveness of the polling pattern changes that occur after the blips.
yea by quantization noise i mean likeAt 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 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.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...?