It has a mechanism to reduce it, quite probably adding some latency. But better always 8ms of latency than random jitter between 1ms to 8ms.
This will also help with WiFi + rtpmidi and bluetooth.
From the (oldish) midi.org article[1]:
The Universal MIDI Packet format adds a Jitter Reduction Timestamp mechanism. A Timestamp can be prepended to any MIDI 1.0 Protocol message or MIDI 2.0 Protocol message for improved timing accuracy.
Well, there should be a sample timestamp in there, so that's ONE benefit a high-level async protocol provides.
The delivery timing does not correlate to the playback timing, and so this will reduce the need for real-time determinacy of the data-streams transport.
Comments
does midi 2 suffer from MIDI timing jitter? Using modular (eurorack) now and that issue made midi unusable for me
It has a mechanism to reduce it, quite probably adding some latency. But better always 8ms of latency than random jitter between 1ms to 8ms.
This will also help with WiFi + rtpmidi and bluetooth.
From the (oldish) midi.org article[1]:
1: https://www.midi.org/articles-old/details-about-midi-2-0-mid...
Well, there should be a sample timestamp in there, so that's ONE benefit a high-level async protocol provides. The delivery timing does not correlate to the playback timing, and so this will reduce the need for real-time determinacy of the data-streams transport.
make sense?