5 Jun
2010
5 Jun
'10
11:19 p.m.
On Sat, Jun 5, 2010 at 2:07 PM, Ken Restivo <ken(a)restivo.org> wrote:
"at least relatively recent versions"
i rewrote the core of a2jmidid sometime earlier this year (or possibly
toward the end of last year). ironically, both of the 1-way clients
(a2j and j2a) were correctly designed and implemented, but a2jmidid
had been written in a different style. no more.
The issue is
not using ALSA MIDI. Its routing from JACK to ALSA MIDI. If
this is not designed and implemented correctly, it can end up with large
amounts of jitter (variable delays in how long it takes to actually deliver
MIDI data to its destination). a2jmidid (at least relatively recent
versions) is correctly designed and implemented in this respect.
Really? It's probably been a couple years since I used a2jmidid, but I recall it
having horrible jitter and latency (when using AZR3, which I used to use a lot) compared
to the -Xseq option in jackd.
-ken