In several of the threads I see lots of graphs from various testing applications. Many of which directly contradict others. If possible, would someone give me a compiled list of all the available software to test the sensors capabilities.
Enotus tends to displays max counts/speed without giving a true representation of where the sensor stars starts losing perfect tracking.
Outerspace's logger can graph, although it's not going to be exact. Mainly it's the the discrepancy between sensors and different CPI ranges.
Sujoy's hardware testing is based on the max CPI range of a sensor and Steelseries QcK surface. (He never published lower CPI test on mice other than the DA) Test that contradict others are likely using a different surface.
The problem with those programs is that they show data that computer receives from mouse. It means that even sensors with acceleration will show perfect tracking with no accel signs (example is adns-9500).
For accurate results you gonna have to build something like that: http://www.esreality.com/?a=longpost&id=1265679&page=3
We also use programs like Paint for jitter and prediction (this isn't accurate and we don't have any accurate way to measure degree of prediction) and Games for acceleration tests (e.g. quake live because it's free and has raw input).
Max tracking speed changes:
- on different surfaces, (CPI is also surface dependant so it will give not super accurate results in the software as long as we assume it is constant)
- with Lift off distance - usually with lower LOD we get lower tracking speeds, (CPI also might be different when thickness of feet will change)
- with different Firmwares.
- with different lens magnification.
This works for Audition 3, I have no idea about the newer versions.
This is all done on the left toolbar:
1) Click the Edit button
2) Hit the File tab, and pick Import File, choose Vx_Vy_NF.wav
3) Click Edit File
4) Click on the effects tab and pick Amplify/Fade (process)
5) Untick "View all setting in DB" and enter the amplification percentage (instructions for this are in the readme)
6) Right click on the right guide and choose Sample Values
7) Zoom with the mouse wheel until things look right.