Hey Chris,
On Thu, Aug 15, 2019 at 4:08 PM Chris Caudle <chris@xxxxxxxxxxxxxxx> wrote:
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.
Yup. I looked around, but didn't run "--help" for each jack_ command.
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?
Yes. I'm running jack2 as a systemd user service - so it starts as soon as I log in.
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.
Sure.
Thanks for the help!
-m
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx https://lists.linuxaudio.org/listinfo/linux-audio-user
