<br><br><div class="gmail_quote">On Sat, May 29, 2010 at 1:16 PM, Aaron Krister Johnson <span dir="ltr"><<a href="mailto:aaron@akjmusic.com">aaron@akjmusic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
It seems that I'm very confused by the whole jack MIDI system. Are<br>
there some docs to refer to, as in a tutorial? I'm confused why Julien<br>
needs to use so many Jack applications to set up a single MIDI<br>
connection...it's certainly less involved with aconnect. And I've<br>
certainly started jackd with -X and have access to alsa sequencers--so<br>
why the other timer and bridge apps, etc?<br><br></blockquote><div><br>the timing behaviour of the two -X options (seq and raw) are not very good. some might be sufficiently uncharitable as to call them "unusable".<br>
<br>a2jmidid (at least versions of it that are less than a year old) are much much better and for now its the recommended way to make ALSA sequencer ports show up in JACK. <br><br>some people (including julien) want JACK MIDI ports to show up as ALSA sequencer ports too, so he has an additional program for that (j2a_bridge).<br>
<br>finally, julien is running a program to generate MIDI clock messages.<br><br>--p<br><br></div></div>