woah... we're all on the same team. I'm trying to put together a miditest, and i'm just trying to figure out an easy way to test a lot of interfaces in a short amount of time. We all have the same problem....Crappy midi. We should all bond over this.
So...I just did a refresher on college stats, and standard deviation is not a bad way to describe the variance with a set of data points. What these jitter measurement from miditest means (i think) is that 68% of the measured data points vary by an average of .75 ms from the average of the measured times. 99% of your midi messages vary by 2.25ms from the average of the message time. This is just how standard deviation works.
I am working from the assumption that the measurements are the sum of bus latency and jitter. We cant get an exact measure of latency, so we average the message time. From there miditest uses standard deviation to get a variance measurement of the data points. again 68% of the messages have an average vary from the average latency by .75ms.
You're assumption that maximum jitter equals jitter is probably not accurate. I'm trying very hard not to be offensive.
I want to reduce both latency and jitter. I think the motu atp has a crappy latency and crappy jitter.
I friend of mine actually rates the attractiveness of women in std deviations.