On Wed, 2008-01-23 at 14:52 +0100, hollunder@xxxxxx wrote: > On Wed, 23 Jan 2008 11:19:29 +0100 > jeremaja niko <jeremaja.niko@xxxxxxxxxxxxxx> wrote: > > > hi m > > > > 1. i think you need "aconnectgui" or "kaconnect", very simple tools > > to route your midi connections. there is "aconnect" as a command line > > tool. > > > > 2. as far as i know there is no difference between jack midi and alsa > > midi - jack is using alsa midi. > > > > hope this helps > > nikola > > 2. is true for older jack, however newer versions and the 0.109 release > also support jack midi where the big difference is, as far as I > understand it, that jack midi has the same time source as jack audio, > whereas alsa midi and jack audio have different time sources. > > They are not compatible by default, recent qjackctl and patchage can > manage both. There are little apps like a2jmidid that allow you to > connect alsa midi to jack midi ports. They _are_ compatible by default (to some degree) - just start jackd 0.109 with the '-X seq' command line parameters to the ALSA driver and all ALSA sequencer ports will appear as JACK MIDI ports. --ll
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
