Care to help me analyse my MIDITest results for MIDI timing?

Care to help me analyse my MIDITest results for MIDI timing?


MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 01:01:23
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: yes
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: no
Note on: no
Key aftertouch: no
tController: no
Program change: no
Channel aftertouch: no
Pitchbend: no
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: no
Tune request: no
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078


MIDI Input: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 444.57 ms 67893.95 ms 68338.53 ms
Message MaximumTime: 0.12 ms 189.51 ms 189.53 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 2.17 ms 2.19 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 14 14
1 - 2 ms: 0 18533 18245
2 - 3 ms: 0 10470 10652
3 - 4 ms: 0 2221 2327
4 - 5 ms: 0 6 6
5 - 10 ms: 0 1 1
10 - 20 ms: 0 1 1
20 - 50 ms: 0 0 0
50 - 100 ms: 0 1 1

100 ms: 0 3 3

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 2.19 ms Total time: 94.437 sec
Message jitter: 1.97 ms
Message max deviation: 187.34 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 59428.80 ms
Byte MaximumTime: 189.53 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 1.90 ms

< 1 ms: 5450
1 - 2 ms: 15604
2 - 3 ms: 8371
3 - 4 ms: 1815
4 - 5 ms: 4
5 - 10 ms: 1
10 - 20 ms: 1
20 - 50 ms: 1
50 - 100 ms: 0

100 ms: 3

Byte count: 42412

Byte latency: 1.90 ms
Byte jitter: 2.00 ms
Byte max deviation: 187.63 ms

What do you want to know?
I see you only test stuff in relation to syncing and transport, any reason for that?

About timing (message latency, jitter and deviation) it isn’t super tight. MIDI can do better.
The Message Maximum RCV Time of 189.51 is something to look in to, maybe do another test to see if this peak persists.

You could also run the test again with timestamping off, to see if it will make a difference.

Quicker I thought, since I’m really only concerned with timing. I’ll run it with everything next time.

I did but didn’t post it, it was 3am and I had reached the point of diminishing returns

I’ll run two more with everything turned on but toggle the timestamping.

I also ran a simple loopback test using a 1/4 note kick for 7 minutes and there was a noticeable timing issue that appeared to stay within a 125 sa,ples at 48k; it wasn’t consistent and was spot on only a few times over the 7 minutes so using any kind of fixed compensation wouldn’t solve the issue but it’s so negligible

Does the test only turn up something after 7 minutes of loopback? If nobody in the rest of the world notices anything because they are too busy creating masterpieces then they will be unlikely to need to run (these regular little)benchtests every other day just so we can say BOO! to the company for there being a few ticks off the midi timing.
:laughing:
Seriously. Why? Do you have a specific issue yourself?

The person who provoked this particular post is forever “hidden” from me so there’s no need for it and I’ve decided to delete it since it was a distraction from the topic.

Back to the topic at hand…

This is with MIDI Timestamping on. I see it indicates no errors and the byte latency, byte jitter, byte max deviation is significantly lower but, again, I’m not sure how to interpret much of this to real world performance.


\

MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 12:53:48
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: yes
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078


MIDI Input: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 1591.94 ms 59433.23 ms 61025.17 ms
Message MaximumTime: 54.10 ms 3.68 ms 55.59 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.05 ms 1.90 ms 1.95 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31249 7 6
1 - 2 ms: 0 23370 23154
2 - 3 ms: 0 7866 8081
3 - 4 ms: 0 7 8
4 - 5 ms: 0 0 0
5 - 10 ms: 0 0 0
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 1 0 1

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 1.95 ms Total time: 94.890 sec
Message jitter: 0.40 ms
Message max deviation: 1.90 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 27057.86 ms
Byte MaximumTime: 18.53 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 0.87 ms

< 1 ms: 25986
1 - 2 ms: 4489
2 - 3 ms: 774
3 - 4 ms: 0
4 - 5 ms: 0
5 - 10 ms: 0
10 - 20 ms: 1
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 79092

Byte latency: 0.87 ms
Byte jitter: 0.44 ms
Byte max deviation: 17.67 ms

Ah okay, if note and CC data are important to you, I would suggest to run it with Note off, Note on, Key aftertouch, Controller, Program change, Channel aftertouch & Pitchbend. And leave the rest unticked.

Well as you might know MIDI is never spot on. If every message is within <1ms deviation your MIDI is as tight as MIDI can be.
The majority of your midi messages are between 1-2ms. That’s pretty normal for a non-directmusic device, and I would not worry about it that much. Strange though is the fact it fluctuates between <1ms and <4ms with peaks to >20.

As you have the big peak in the MIDI loopback test, and the timing issue in Cubase I would also run a DPC test. Because faulty Kernel device drivers can causes excessive latencies of DPCs.

I would also check with another cable, just to be sure.

And 6000 samples @ 48Khz is a lot (125ms), are you sure?

Another question, Is you mobo’s PCI port direct or a bridged PCI-E?

Another observation, I noticed a lot of the people with MIDI timing issues are using AMD Phenom II CPU’s.
Coincidence?

Edit

Our posts crossed.
The 2nd test is a lot tighter. The majority of the messages is within <3ms. I think for a device without native directmusic drivers it’s pretty average. Not super tight, but workable.
There are some delayed events though >10ms and even a few >100ms. That’s not normal and could be annoying enough to dig a little deeper to what’s causing it.

And with no timestamp it actually gets better. I wonder how relevent these measurements are since it isn’t testing directmusic ports, only MME which I don’t use.


\

MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 13:23:13
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: no
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078


MIDI Input: Delta AP MIDI
Description: M-Audio Delta AP 192
Provider: M-Audio
DriverDate: 12-21-2011
DriverVersion: 5.10.0.5078



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 290.98 ms 56786.32 ms 57077.29 ms
Message MaximumTime: 0.18 ms 3.05 ms 3.06 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 1.82 ms 1.83 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 9 9
1 - 2 ms: 0 31146 30681
2 - 3 ms: 0 93 558
3 - 4 ms: 0 2 2
4 - 5 ms: 0 0 0
5 - 10 ms: 0 0 0
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 0 0 0

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 1.83 ms Total time: 93.784 sec
Message jitter: 0.12 ms
Message max deviation: 1.82 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 25323.34 ms
Byte MaximumTime: 2.04 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 0.81 ms

< 1 ms: 28188
1 - 2 ms: 3059
2 - 3 ms: 3
3 - 4 ms: 0
4 - 5 ms: 0
5 - 10 ms: 0
10 - 20 ms: 0
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 79038

Byte latency: 0.81 ms
Byte jitter: 0.36 ms
Byte max deviation: 1.23 ms

I’m aware and a little concerned about the AMD thing, yes. So the second one without timestamping has fixed the delays you mentioned. Everything seems tighter, yes? Seems odd that turning off timestamping would be more accurate but I’m not going to complain. I’ll do a loopback test without it and see what happens. Thanks again, your comments have helped me understand what to look for here.

Oh, and my calculation was waaay off. It’s 125 samples, not 6000. :blush:

Changing it now.

Indeed the 3rd test, looks pretty okay.

When you test API as “kernel streaming” the directmusic port will be tested.
But beware, your card needs to have a native DirectMusic driver. Not emulated. Because emulated will be handled by the same API as Windows MIDI. And will most likely add latency because of the emulation. But you could always test it.
The quality of the results will be highly depending on how well the DirectMusic driver is written.

125 samples @ 48Khz is indeed more consistent with your test in Cubase compared to the MIDI test tool (2,6ms). :wink:

I can’t get kernel streaming to work. MidiTest locks up when I try it so I can’t test for the directmusic ports. Looking at the Drum Editor in Cubase, however, it’s clear that directmusic is capturing the MIDI events more accurately, i.e., closer to where I inaccurately played them.

(Inaccurate playing + MIDI jitter + plus VST latency) x (grasp - reach) = quantize + swing :wink:

I’ve posted as attachments the logs for my two Midisport 8x8 interfaces if anyone should be curious. The aggregates appear remarkably similar when comparing the two devices for timestamped and non-timestamped performance respectively. Overall performance seems to favor non-timstamping, however. I may never know about the directmusic performance, perhaps the dev may be willing to offer some insight if I contact him.

Quite an interesting afternoon. Niles, thanks for the help.
Midisport 1 mtresults_24Aug2012_172303.txt (3.18 KB)
Midisport 1 mtresults_24Aug2012_170712.txt (3.18 KB)

… and logs for the second Midisport.
Midisport 2 mtresults_24Aug2012_171716.txt (3.18 KB)
Midisport 2 mtresults_24Aug2012_164706.txt (3.18 KB)

:unamused: Only on this forum do you get this sort of condescension to a reasonable question and a mild ribbing. So insecure.
I’m actually trying to help you. :unamused: I also find most timing problems hackneyed for the sheer ignorance of posters trying to look like they know something they don’t and getting all shirty when a one-liner makes sense of two pages of drivel and tests nobody needs to waste time doing.
I get to be employed by a lot of people because I get the job done by doing it and not by looking for excuses not to.
A problem? Don’t stand there moaning! Get it fixed and get on with the job.
But it’s a faulty component. We’ve still got a job to do so fix it and then write the report.

Stop reading my other posts that don’t concern you. :mrgreen:

As Niles says midi timing is not exact. I’m saying the same thing plus don’t bother yourself with breaking it down to the nth degree of timing. Cubase is a recording medium and not an exact scientific instrument.
And any timing tests should be addressed to the soundcard maker (first) as well as the DAW that uses it. Pointless any other way unless you are pretty certain the job is just a quick fix. This is what NONE of the timing related posts have done on this forum. Their feet seem glued to the floor here.

Things like this: http://www.soundonsound.com/forum/showflat.php?Board=PCMus&Number=918351

are more relevant to timing problems. And a good example of how to run a thread. A little disagreement without self-righteous "How dare you…!?"s prancing about.

Then I would stick with that. When it feels/works good it’s good, regardless the fact you can’t test it.

If you are interested in the technology behind DirectMusic and Windows Midi this is an interesting read to understand both concepts.

No problem, I’m always fascinated by these kind of tests and I think it’s fun and useful to know what the limits of a system are to understand why certain things are happening to eventually learn to work with it or solve it.

Unfortunately, anyone unregistered wanting to view this page from the outside would have to register to see the attachments and I know how much I dislike having to register at websites just to get some info so I’m pasting the results from the attachments.


Precisely, Niles. I was fortunate enough to receive some early mentoring from a few veterans who came up during a different era of audio production. One of them from a time before most gear could be bought off the shelf. He built the console for one of the era’s higher profile studio owners in the mid-sixties. Back then being hired as the studio engineer for a new facility meant you could very well be tasked with designing the room, building the console, perhaps some of the outboard gear, wiring at all together then, finally, troubleshooting it all before recording the first client. I learned how important testing, retesting and understanding the resulting details is to being able to confidently start work and avoid tail chasing. I can’t afford the kind of top end gear used at work for my home rig but I can troubleshoot thoroughly enough to know what can and can’t be fixed, it’s exact limitations and how, exactly, to work around them.

With a little insight at times from good folk like yourself, of course. :smiley:


The aforementioned attachments, cut and pasted, for our unregistered friends:

Midisport interface #1 no timestamp:


MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 17:23:00
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: no
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: 3- MIDISPORT 8x8/s Out 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available


MIDI Input: 3- MIDISPORT 8x8/s In 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 449.46 ms 139378.25 ms 139827.71 ms
Message MaximumTime: 0.03 ms 5.94 ms 5.95 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 4.46 ms 4.47 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 5 5
1 - 2 ms: 0 3 3
2 - 3 ms: 0 1731 1730
3 - 4 ms: 0 6998 6999
4 - 5 ms: 0 22466 22466
5 - 10 ms: 0 47 47
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 0 0 0

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 4.47 ms Total time: 177.137 sec
Message jitter: 0.59 ms
Message max deviation: 4.46 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 59759.42 ms
Byte MaximumTime: 3.97 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 1.91 ms

< 1 ms: 10
1 - 2 ms: 24095
2 - 3 ms: 5695
3 - 4 ms: 1450
4 - 5 ms: 0
5 - 10 ms: 0
10 - 20 ms: 0
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 78627

Byte latency: 1.91 ms
Byte jitter: 0.56 ms
Byte max deviation: 2.06 ms




Midisport interface #1 with timestamp:


MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 16:59:55
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: yes
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: 4- MIDISPORT 8x8/s Out 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available


MIDI Input: 4- MIDISPORT 8x8/s In 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 440.29 ms 145215.11 ms 145655.40 ms
Message MaximumTime: 0.02 ms 6.47 ms 6.48 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 4.65 ms 4.66 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 6 6
1 - 2 ms: 0 4 4
2 - 3 ms: 0 1611 1602
3 - 4 ms: 0 5693 5664
4 - 5 ms: 0 16159 16046
5 - 10 ms: 0 7777 7928
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 0 0 0

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 4.66 ms Total time: 177.420 sec
Message jitter: 0.78 ms
Message max deviation: 4.65 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 62144.72 ms
Byte MaximumTime: 4.92 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 1.99 ms

< 1 ms: 13
1 - 2 ms: 23707
2 - 3 ms: 6025
3 - 4 ms: 755
4 - 5 ms: 750
5 - 10 ms: 0
10 - 20 ms: 0
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 78767

Byte latency: 1.99 ms
Byte jitter: 0.65 ms
Byte max deviation: 2.94 ms




Midisport interface #2 no timestamp:

\

MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 17:17:14
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: no
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: 4- MIDISPORT 8x8/s Out 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available


MIDI Input: 4- MIDISPORT 8x8/s In 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 445.92 ms 139801.48 ms 140247.40 ms
Message MaximumTime: 0.06 ms 5.95 ms 5.96 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 4.47 ms 4.49 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 8 8
1 - 2 ms: 0 1 1
2 - 3 ms: 0 1668 1668
3 - 4 ms: 0 6780 6778
4 - 5 ms: 0 22735 22737
5 - 10 ms: 0 58 58
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 0 0 0

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 4.49 ms Total time: 177.492 sec
Message jitter: 0.59 ms
Message max deviation: 4.47 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 59768.77 ms
Byte MaximumTime: 3.99 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 1.91 ms

< 1 ms: 9
1 - 2 ms: 24043
2 - 3 ms: 5749
3 - 4 ms: 1449
4 - 5 ms: 0
5 - 10 ms: 0
10 - 20 ms: 0
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 78813

Byte latency: 1.91 ms
Byte jitter: 0.56 ms
Byte max deviation: 2.08 ms



Midisport interface #2 with timestamp:

\

MidiTest Results




================ Info ====================================================

Date: 24 Aug 2012
Time: 16:47:00
AppVersion: 4.11.251
OS: Home Edition, Service Pack 1 (Build 7601)
Processor(s): AMD Phenom™ II X6 1100T Processor
Speed: 3800 MHz
Number: 6
API: MultiMedia Extensions (MME)
Test type: Advanced
Use timestamp: yes
Errors: 0
Last error: None



================ Tested Message Types ====================================

Note off: yes
Note on: yes
Key aftertouch: yes
Controller: yes
Program change: yes
Channel aftertouch: yes
Pitchbend: yes
System exclusive: no
MIDI time code quarter frame: yes
Song position pointer: yes
Song select: yes
Tune request: yes
MIDI clock: yes
MIDI tick: no
Start: yes
Continue: yes
Stop: yes
Active sensing: yes
System reset: yes
System exclusive mixed with realtime messages: no



================ Ports ===================================================

MIDI Output: 3- MIDISPORT 8x8/s Out 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available


MIDI Input: 3- MIDISPORT 8x8/s In 8
Description: Not available
Provider: Not available
DriverDate: Not available
DriverVersion: Not available



================ Results Per Message =====================================

MESSAGES Snd Rcv Snd+Rcv

Message TotalTime: 450.28 ms 145452.40 ms 145902.68 ms
Message MaximumTime: 0.04 ms 6.23 ms 6.26 ms
Message MinimumTime: 0.00 ms 0.00 ms 0.00 ms
Message AverageTime: 0.01 ms 4.65 ms 4.67 ms
SysexTime: 0.00 ms 0.00 ms 0.00 ms
SysexAverage: 0.00 ms 0.00 ms 0.00 ms

< 1 ms: 31250 7 7
1 - 2 ms: 0 2 2
2 - 3 ms: 0 1399 1388
3 - 4 ms: 0 5883 5850
4 - 5 ms: 0 16188 16114
5 - 10 ms: 0 7771 7889
10 - 20 ms: 0 0 0
20 - 50 ms: 0 0 0
50 - 100 ms: 0 0 0

100 ms: 0 0 0

Message count: 31250 Sysex count: 0
Sysex size: 0 Sysex passed: 0

Message latency: 4.67 ms Total time: 175.810 sec
Message jitter: 0.76 ms
Message max deviation: 4.65 ms



================ Results Per Byte ========================================

BYTES

Byte TotalTime: 62388.54 ms
Byte MaximumTime: 4.90 ms
Byte MinimumTime: 0.00 ms
Byte AverageTime: 2.00 ms

< 1 ms: 11
1 - 2 ms: 23313
2 - 3 ms: 6141
3 - 4 ms: 1130
4 - 5 ms: 655
5 - 10 ms: 0
10 - 20 ms: 0
20 - 50 ms: 0
50 - 100 ms: 0

100 ms: 0

Byte count: 78770

Byte latency: 2.00 ms
Byte jitter: 0.65 ms
Byte max deviation: 2.91 ms

Windows 7 and Vista OS is the cause of MIDI jitter.

Midi is tight enough in XP (64 and 32 bit), and Mac OS (all versions).

http://www.gearslutz.com/board/electronic-music-instruments-electronic-music-production/693456-windows-7s-midi-out-jitter-disaster.html

So are you saying these numbers are bad? Good? Mediocre? Utter rubbish? Forty-two?