16 Aug
2019
16 Aug
'19
12:37 a.m.
The JACK (1) page [0] references this mailing list for possible dialog
about jack usage.
I am using the jack2 daemon.
I am launching a jack aware application (OBS), but the connection to jack
is not being made automatically, so I use jack_connect to make the
connection between the two ports (system mic and OBS reader).
Is there a "jack_FOO" CLI tool that can be used to query what available
ports there are?
The reason being is I need to put a sleep into my script to connect the
jack ports:
/usr/bin/obs &
sleep 10
jack_connect system:out_1 OBS:jack_in
I'd like to eliminate the sleep command and poll jack to see if OBS has any
port available.
What do you think?
Thanks!
-m
[0] http://jackaudio.org/community.html
16 Aug
16 Aug
12:50 a.m.
Hello,
I think jack_lsp does what you need.
~Georg
Am 15.08.19 um 22:36 schrieb Matt Zagrabelny:
The JACK (1) page [0] references this mailing list for
possible dialog
about jack usage.
I am using the jack2 daemon.
I am launching a jack aware application (OBS), but the connection to
jack is not being made automatically, so I use jack_connect to make
the connection between the two ports (system mic and OBS reader).
Is there a "jack_FOO" CLI tool that can be used to query what
available ports there are?
The reason being is I need to put a sleep into my script to connect
the jack ports:
/usr/bin/obs &
sleep 10
jack_connect system:out_1 OBS:jack_in
I'd like to eliminate the sleep command and poll jack to see if OBS
has any port available.
What do you think?
Thanks!
-m
[0] http://jackaudio.org/community.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:09 a.m.
Am 15.08.19 um 22:50 schrieb Georg Krause:
Am 15.08.19 um 22:36 schrieb Matt Zagrabelny:
> Is there a "jack_FOO" CLI tool that can be used to query what
> available ports there are?
I think jack_lsp does what you need.
jack_lsp comes with jack, so is always available, but for more
convenience, you might want to try some third-party tools, that automate
the connection process.
One of these (written by me) is jack-matchmaker. You can also use it to
list all ports with their alias names and meta-data pretty-names:
$ jack-matchmaker --list-inputs --list-outputs \
--aliases --prettynames
Or shorter:
$ jack-matchmaker -ioan
The Github page has more information on the program and also lists
several alternatives at the bottom of the page.
https://github.com/SpotlightKid/jack-matchmaker
Chris
1:23 a.m.
Hey Christopher,
On Thu, Aug 15, 2019 at 4:09 PM Christopher Arndt <chris(a)chrisarndt.de>
wrote:
Am 15.08.19 um 22:50 schrieb Georg Krause:
Okay. Thanks for the tip.
Am 15.08.19 um 22:36 schrieb Matt Zagrabelny:
> Is there a "jack_FOO" CLI tool that can be used to query what
> available ports there are?
I think jack_lsp does what you need.
jack_lsp comes with jack, so is always available, but for more
convenience, you might want to try some third-party tools, that automate
the connection process.
One of these (written by me) is jack-matchmaker. You
can also use it to
list all ports with their alias names and meta-data pretty-names:
$ jack-matchmaker --list-inputs --list-outputs \
--aliases --prettynames
Or shorter:
$ jack-matchmaker -ioan
The Github page has more information on the program and also lists
several alternatives at the bottom of the page.
https://github.com/SpotlightKid/jack-matchmaker
Cool. I'll check out jack-matchmaker if I run into issues wit the stock
jack_ commands.
Cheers!
-m
1:43 a.m.
Am 15.08.19 um 23:21 schrieb Matt Zagrabelny:
Cool. I'll check out jack-matchmaker if I run into
issues wit the stock
jack_ commands.
jack_lsp/jack_connect do what they're supposed to do, but the advantage
of tools like jack-matchmaker, jack-plumbing etc, is that you don't have
to muck around with unreliable 'sleep' commands and fixed port names,
because they connect ports as soon as they appear and can match partial
port names and more.
Chris
1:08 a.m.
On Thu, August 15, 2019 3:36 pm, Matt Zagrabelny wrote:
Is there a "jack_FOO" CLI tool that can be
used to query what available
ports there are?
There is a group of tools known as jack example clients which may be useful.
Actually jack_connect is part of that, look in /usr/bin and see what other
jack* files exist, you probably already have them.
jack_lsp lists ports
jack_wait waits for various jackd events and then exits; see the help file
The reason being is I need to put a sleep into my
script to connect the
jack ports:
/usr/bin/obs &
sleep 10
jack_connect system:out_1 OBS:jack_in
Is jackd already running? jack_wait would be for waiting on jackd to
finish initializing in cases where obs quits out right after starting
because it cannot detect a jack server running.
I'd like to eliminate the sleep command and poll
jack to see if OBS has
any port available.
I'm not sure how difficult it would be to parse the output from jack_lsp,
but I think it should be possible, and if there are no obs ports when you
run the command, sleep 1 or 2 seconds and run again.
--
Chris Caudle
1:21 a.m.
Hey Chris,
On Thu, Aug 15, 2019 at 4:08 PM Chris Caudle <chris(a)chriscaudle.org> wrote:
Yes. I'm running jack2 as a systemd user service - so it starts as soon as
I log in.
Sure.
Thanks for the help!
-m
On Thu, August 15, 2019 3:36 pm, Matt Zagrabelny
wrote:
Yup. I looked around, but didn't run "--help" for each jack_ command.
Is there a "jack_FOO" CLI tool that can
be used to query what available
ports there are?
There is a group of tools known as jack example clients which may be
useful.
Actually jack_connect is part of that, look in /usr/bin and see what other
jack* files exist, you probably already have them.
jack_lsp lists ports
jack_wait waits for various jackd events and then exits; see the help file
Sounds promising.
The reason
being is I need to put a sleep into my script to connect the
jack ports:
/usr/bin/obs &
sleep 10
jack_connect system:out_1 OBS:jack_in
Is jackd already running? jack_wait would be for waiting on jackd to
finish initializing in cases where obs quits out right after starting
because it cannot detect a jack server running.
Hmmm... okay.
I'd like to eliminate the sleep command and
poll jack to see if OBS has
any port available.
I'm not sure how difficult it would be to parse the output from jack_lsp,
but I think it should be possible, and if there are no obs ports when you
run the command, sleep 1 or 2 seconds and run again.
1933
days inactive
1933
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Chris Caudle -
Christopher Arndt -
Georg Krause -
Matt Zagrabelny