Am Donnerstag, 24. Januar 2008 schrieb Nedko Arnaudov: > Miguel M <therevoltingx@xxxxxxxxx> writes: > >> > 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. > > Oh, ok, to it's the time source. I'm guessing it would be better to for > > applications to use the native jack midi that way the transport and MMC > > time can be in sync. I wonder if there are timing issues when using > > a2jmidid, or if it's better to use the -X seq option as suggested. > > Oh well, it's time to experiment a bit. > a2jmidid and -X seq should have same timing issues. In fact they are > almost same code. a2jmidid is there mainly to auto expose ALSA seq > clients when using -X raw > Some ppl use it to expose hardware ALSA seq port of card, different from > one used through different ALSA audio backend. After doing small tweak > in the code to disable fitering of hardware ports. I will probably send nedko a patch for that (and for switching off the debug) this weekend. ;-) Very handy tool, when you use the firewire-backends... Arnold -- visit http://www.arnoldarts.de/ --- Hi, I am a .signature virus. Please copy me into your ~/.signature and send me to all your contacts. After a month or so log in as root and do a "rm -rf /". Or ask your administrator to do so...
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
