Depending on your version of jack or qjackctl ALSA MIDI and JACK MIDI application can communicate peacefully by going under Settings and under midi driver selecting alsa seq or on the command line by using the --midi=seq switch.<br>
Now all your midi aware applications (regardless if it&#39;s Jack or Alsa) will appear in the same tab.<br><br>Miguel<br><br><div class="gmail_quote">On Thu, Feb 21, 2008 at 9:49 AM, M-.-n &lt;<a href="mailto:nostromo@arkaos.net" target="_blank">nostromo@arkaos.net</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
After successfully implementing the audio connection of my tracker with<br>
jack, I&#39;m not trying to have the midi part running. It seems fairely easy<br>
from what I got however I&#39;m facing a connection problem to be able to test<br>
it properly:<br>
<br>
In qjackctl, the midi connection I create appears correctly in the midi tab.<br>
However, all synth I&#39;ve tried (amSynth/rtsynth) create their midi input from<br>
alsa and the connection appears in the alsa tab without any apparent way of<br>
connecting my output to their input. Is that normal ? Is there really two<br>
&#39;categories&#39; or midi connection and does that mean I should use alsa driver<br>
instead ? I was kind of liking the apparent audio/midi syncronisation jack<br>
was providing...<br>
<br>
If anyone knows of a synth that uses jack for midi, it&#39;d be nice too<br>
<br>
Thanks<br>
Marc<br>
<br>
_______________________________________________<br>
Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org" target="_blank">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</blockquote></div><br>