6 Jan
2019
6 Jan
'19
4:24 a.m.
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 <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!!!
6 Jan
6 Jan
12:54 p.m.
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:
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
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 
2:42 p.m.
On 06.01.19 13:38, Jonathan E. Brickman wrote:
Didn't find jack_property -- but did find
jack_alias, this what you were
thinking of?
You're most probably running JACK2.
JACK metadata is only implemented for JACK1 as of today, but should be part of
next official JACK2 release [1].
[1]
https://github.com/jackaudio/jack2/commit/fed6f1e66dfb4b78f8b55467d5130e587…
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!!!
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
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 
3:32 p.m.
Am 06.01.19 um 11:53 schrieb hgn:
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).
jack_property is not installed with jack2, and was only recently
(2018-10) included in its repo as "example-client/property.c".
Unfortunately, it is still missing in packages for the latest releases
of jack2.
But if you build jack2 yourself, you'll find it in "build/example-clients".
Chris
7 Jan
7 Jan
1:03 a.m.
Got it! Thank you, Chris. Built using yaourt and package jack2-git on
Manjaro.
J.E.B.
On 1/6/19 7:32 AM, Christopher Arndt wrote:
Am 06.01.19 um 11:53 schrieb hgn:
--
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!!!
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).
jack_property is not
installed with jack2, and was only recently
(2018-10) included in its repo as "example-client/property.c".
Unfortunately, it is still missing in packages for the latest releases
of jack2.
But if you build jack2 yourself, you'll find it in
"build/example-clients".
Chris
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
3:08 p.m.
Christopher, would you mind giving a command-line example or two? I tried
many and also googled a bit, did not find a working way to use
jack_property to list or set anything :-) Just for starters, how do you
get the UUID of a process?
J.E.B.
On Sun, Jan 6, 2019 at 7:33 AM Christopher Arndt <chris(a)chrisarndt.de>
wrote:
Am 06.01.19 um 11:53 schrieb hgn:
--
Jonathan E. Brickman jeb(a)ponderworthy.com (785)233-9977
<(785)%20233-9977>
Hear us at ponderworthy.com -- CDs and MP3 now available!
<http://ponderworthy.com/ad-astra/ad-astra.html>
Music of compassion; fire, and life!!!
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).
jack_property is not installed with jack2, and was only recently
(2018-10) included in its repo as "example-client/property.c".
Unfortunately, it is still missing in packages for the latest releases
of jack2.
But if you build jack2 yourself, you'll find it in
"build/example-clients".
Chris
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
9 Jan
9 Jan
2:44 p.m.
Am 07.01.19 um 14:07 schrieb Jonathan Brickman:
Christopher, would you mind giving a command-line
example or two?
Setting a property:
jack_property --port system:midi_playback_3 -s prettyname "MIDAS MR18
MIDI Out"
(Gives an error, but seems to work)
Getting it:
jack_property -l --port system:midi_playback_3 prettyname
BUT: I don't think that using properties is the right approach. Instead
you could look if the MIDI ports opened by osc2midi have port name
aliases set:
jack_lsp -A
You can use my tool "jack-matchmaker" to automatically conenct JACK
ports based on port names/aliases:
https://github.com/SpotlightKid/jack-matchmaker
Chris
1934
days inactive
1937
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Christopher Arndt -
Hanspeter Portner -
hgn -
Jonathan Brickman -
Jonathan E. Brickman