Hi, I have found a rather helpful workaround: use aconnect source destination to connect MIDI ports. It works even if You only know the name of the application (or the port) but not the actual port number. I am going to use aconnect from a script to connect my MIDI ports automatically to save some amount of clicking around with the mouse ;-) Regards, Crypto.l On Wednesday 24 September 2008 00:42:08 hollunder@xxxxxx wrote: > On Tue, 23 Sep 2008 23:31:22 +0100 > > andy baxter <andy@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > I have noticed the same bug, so you're not the only one. I use the > > alsa midi tab in qjackctl, but I guess this is no help if you're not > > running jack. > > You don't need to run jack to connect via qjackctl. > > Regards > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
