On 09/28/2014 07:06 PM, Paul Davis wrote:
> patch from svn diff attached
>
i see that your patch only reads the pretty-names (metadata) if exists
at runtime and uses them as the "official" port-names instead.
so, who or what does the pretty-name setup? that is, who or what sets
the pretty-names of each port in the first place?
i was thinking about the user using the qjackctl client/port aliases
functionality already in place and use it eg. to run jack_set_property()
on each renamed client/port alias on jack server start (as read from
Qjackctl.conf file, on a per preset basis).
what you think?
-- rncbc aka Rui Nuno Capela rncbc@email-addr-hidden _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Mon Sep 29 00:15:02 2014
This archive was generated by hypermail 2.1.8 : Mon Sep 29 2014 - 00:15:02 EEST