Re: midi port names

Rui Nuno Capela <rncbc <at> rncbc.org> writes:

> that's the original issue with the jack-midi alsa backend, not
> qjackctl's: it puts all midi ports under the common 'system'/'alsa_pcm'
> client name, instead of separating it by proper application clients, as
> you and i agree it would be righter. unfortunately it's not the way
> jack-midi alsa backend sorts it and i, as qjackctl's author, am just
> helpless about it :(

I "workarounded" this issue in lpatchage, when operating over a2jmidid,
the out of server variant of "-X seq". As can be seen in this screenhost:

http://nedko.arnaudov.name/tmp/ladi-patchage-20080802-a2jmidid-integration.png

lash_synth is ALSA seq application, as opposed to non-sequencer and
system midi ports that are native JACK MIDI.

--

-- 
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org