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
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
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:
For a non-destructive solution you could set metadata.
This is possible from outside the client, for example with the
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
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]
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
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