On Fri, 26 Sep 2014 14:15:32 -0700 (PDT)
Len Ovens <len@email-addr-hidden> wrote:
> The only thing I would like to see different in a2jmidi is the naming. (I am
> not sure how jack1 works) a2j opens as one client called a2j that when expanded
> has the alsa client name followed by the actual port name. This is hard to read
> and use. It is also confusing to new users who ask where the port is just
> because a2j has not been expanded. I would guess the best thing (from a user
> POV) would be for a2j to open a new jack client for each ALSA client with the
> ALSA name. I am not sure what other consequences this would have though :)
^ this ^
The existing arrangement makes it far from clear what the connections are.
-- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Sat Sep 27 04:15:04 2014
This archive was generated by hypermail 2.1.8 : Sat Sep 27 2014 - 04:15:05 EEST