Re: qjackctl prettyname (metadata) patch (was: Bridging alsa and jack midi)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



jack_property uses the JACK metadata API to set values for the pretty-name key.

any other application could do the same thing.

On Sun, Sep 28, 2014 at 2:43 PM, Rui Nuno Capela <rncbc@xxxxxxxxx> wrote:
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@xxxxxxxxx

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux