6 Jan
2019
6 Jan
'19
2:38 p.m.
Didn't find jack_property -- but did find jack_alias, this what you were
thinking of?
J.E.B.
On 1/6/19 4:53 AM, hgn wrote:
For a non-destructive solution you could set
metadata.
This is possible from outside the client, for example with the
commandline tool jack_property, included in jack(2).
Be advised that not all patchbays and connection tools display these
"pretty names". Sometimes you have to switch the display mode in the
tool, sometimes they don't have them implemented, in this case please
file a bug report.
hgn
Am 06.01.2019 03:24 schrieb Jonathan E. Brickman:
--
Jonathan E. Brickman jeb(a)ponderworthy.com <mailto:jeb@ponderworthy.com>
(785)233-9977
Hear us at ponderworthy.com <http://ponderworthy.com/> -- CDs and MP3
available! <http://ponderworthy.com/ad-astra/ad-astra.html>
Music of compassion; fire, and life!!!
I have a need to run three osc2midi clients (m2o)
on a single JACK
server. Is there a way to customize their JACK port names? I can
engineer to use osc2midi, osc2midi-01, and osc2mid-02, i.e., the
automatic JACK-given names, but I was hoping for something more
self-documenting. I took a look at jackdriver.c, but did not find
where I could insert a JACK port name string.
--
Jonathan E. Brickman jeb(a)ponderworthy.com (785)233-9977
Hear us at ponderworthy.com [1] -- CDs and MP3 available! [2]
Music of compassion; fire, and life!!!
Links:
------
[1] http://ponderworthy.com/
[2] http://ponderworthy.com/ad-astra/ad-astra.html
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev