28 Jan
2019
28 Jan
'19
12:25 p.m.
Hi dear list,
http://jackaudio.org/faq/persistent_connections.html
mentions that there is a way for persistent connections without using a
GUI program. The page says about this way to do it that
"The semi-automatic, script-based one is described in another FAQ."
but I can't seem to find it. What could be meant here?
Thanks!
P
28 Jan
28 Jan
1:31 p.m.
On 2019-01-28 11:25:49 (+0100), Peter P. wrote:
http://jackaudio.org/faq/persistent_connections.html
mentions that there is a way for persistent connections without using a
GUI program. The page says about this way to do it that
"The semi-automatic, script-based one is described in another FAQ."
but I can't seem to find it. What could be meant here?
Things like aj-snapshot
[1] or njconnect [2] (there might be more).
[1] http://aj-snapshot.sourceforge.net/
[2] https://sourceforge.net/projects/njconnect/
--
https://sleepmap.de
2:06 p.m.
* David Runge <dave(a)sleepmap.de> [2019-01-28 12:31]:
On 2019-01-28 11:25:49 (+0100), Peter P. wrote:
Thanks David! I went with
jack-plumbing from jack-tools for now.
http://jackaudio.org/faq/persistent_connections.html
mentions that there is a way for persistent connections without using a
GUI program. The page says about this way to do it that
"The semi-automatic, script-based one is described in another FAQ."
but I can't seem to find it. What could be meant here?
Things like aj-snapshot
[1] or njconnect [2] (there might be more).
[1] http://aj-snapshot.sourceforge.net/
[2] https://sourceforge.net/projects/njconnect/ 
29 Jan
29 Jan
5:37 a.m.
jack.plumbing
jack_connect
On Mon, Jan 28, 2019 at 3:26 AM Peter P. <peterparker(a)fastmail.com> wrote:
Hi dear list,
http://jackaudio.org/faq/persistent_connections.html
mentions that there is a way for persistent connections without using a
GUI program. The page says about this way to do it that
"The semi-automatic, script-based one is described in another FAQ."
but I can't seem to find it. What could be meant here?
Thanks!
P
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
7:19 a.m.
An application I've been using is called aj-snapshot. In my script I use
where I start jack I also run aj-snapshot. Whenever an application or
device is connected if it's had previous connections before. My connections
get re-connected.
On Mon, Jan 28, 2019 at 8:17 PM Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
jack.plumbing
jack_connect
On Mon, Jan 28, 2019 at 3:26 AM Peter P. <peterparker(a)fastmail.com> wrote:
Hi dear list,
http://jackaudio.org/faq/persistent_connections.html
mentions that there is a way for persistent connections without using a
GUI program. The page says about this way to do it that
"The semi-automatic, script-based one is described in another FAQ."
but I can't seem to find it. What could be meant here?
Thanks!
P
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
11:44 a.m.
Paul, Elijah, everyone,
thanks for your suggestions! I went with jack_plumbing.
Can anyone confirm that jack_plumbing will need to be started before the
applications which it is about to manage? It does not manage connections
already made? I am on the lookout for a way to start jack, jack_plumbing
and a jack-aware application on the command line and restart each of
them should they crash/die and restore connections no matter in which
sequence the three come up again. It seems jack_plumbing needs to be
started after jackd but before applications it is supposed to manage.
I am afraid I have to write a script using jack_connect then.
For handling of jack connections on headless machines/command line, I am
looking for the best way to make connections once an application has
been started or restarted. It would be great if applications could
generally honor environment variables like
$ JACK_PORTS=system:playback_1 mediaplayerapp
but I suppose that implementation is up to the application programmers.
* Elijah Abdul Rahman <elijahjuanye(a)gmail.com> [2019-01-29 06:19]:
An application I've been using is called
aj-snapshot. In my script I use
where I start jack I also run aj-snapshot. Whenever an application or
device is connected if it's had previous connections before. My connections
get re-connected.
Thanks Elijah, will look into aj-snapshot in comparison to
jack_plumbing
as well.
cheers, P
7:15 p.m.
On Tue, 29 Jan 2019, Peter P. wrote:
thanks for your suggestions! I went with
jack_plumbing.
Can anyone confirm that jack_plumbing will need to be started before the
applications which it is about to manage? It does not manage connections
already made? I am on the lookout for a way to start jack, jack_plumbing
and a jack-aware application on the command line and restart each of
On the command line or from a script? From what I see below, it seems from
a script is really what you want. The CL is still a user interface and not
automated. Then in scripts there are scripts that run whatever the command
line can do and there are scripts that can talk to libraries, like python.
them should they crash/die and restore connections no
matter in which
sequence the three come up again. It seems jack_plumbing needs to be
started after jackd but before applications it is supposed to manage.
I am afraid I have to write a script using jack_connect then.
Jack always has to be first. While some applications will start jack for
you, that generally leads more to confusion and breakage rather than help.
On my system I have chmod -x jackd and use jackdbus instead. I don't
suppose it matters much as jackdbus runs from session start here anyway.
There is nothing that auto restarts jack if it crashes that I know of, but
all the jack* utilities should error out if jack goes away. So a simple
script starts one of these and restarts jack on error might work for
you... but then writing a python script with the jack lib would be better
anyway. I understand that python scripts are more programing that a bash
script, but there is a crossover point where it gets so complex to do
something in bash that it is easier to use python.
For handling of jack connections on headless
machines/command line, I am
looking for the best way to make connections once an application has
been started or restarted. It would be great if applications could
generally honor environment variables like
$ JACK_PORTS=system:playback_1 mediaplayerapp
JACK_DEFAULT=system:playback_9,system:playback_10 would be nice. In fact
it would be nice to have that as part of jack. Instead each jack
application need to be set noautoconnect. I use connect=no for pulse for
example. The problem with that is on restart. more complex programs like a
daw you want to reconnect everything just like it was becasue there might
be 100s of connections. So it ends up best with both and having the user
decide :)
There was some amount of work on session managers in the past, but almost
all of them have fallen to bitrot and are not used. The recomendation
seems to be NSM. NSM has also not been touched for a while, is not in the
debian and derivitives repos and so to use it you need to download the
source and build it.
in the end, a headless system will require some work and new learning.
--
Len Ovens
www.ovenwerks.net
7:22 p.m.
I use jack-matchmaker which I believe is based on one of the above
mentioned or something similar. It can be started before or after and will
automatically re/connect any connections and check any newly created ports
against the argument's given. You can also just assign one port and it will
make all possible connections , or multiple specific connections per pair
of arguments if you use regular expressions well
On Tue, Jan 29, 2019, 02:02 Peter P. <peterparker(a)fastmail.com wrote:
Paul, Elijah, everyone,
thanks for your suggestions! I went with jack_plumbing.
Can anyone confirm that jack_plumbing will need to be started before the
applications which it is about to manage? It does not manage connections
already made? I am on the lookout for a way to start jack, jack_plumbing
and a jack-aware application on the command line and restart each of
them should they crash/die and restore connections no matter in which
sequence the three come up again. It seems jack_plumbing needs to be
started after jackd but before applications it is supposed to manage.
I am afraid I have to write a script using jack_connect then.
For handling of jack connections on headless machines/command line, I am
looking for the best way to make connections once an application has
been started or restarted. It would be great if applications could
generally honor environment variables like
$ JACK_PORTS=system:playback_1 mediaplayerapp
but I suppose that implementation is up to the application programmers.
* Elijah Abdul Rahman <elijahjuanye(a)gmail.com> [2019-01-29 06:19]:
An application I've been using is called
aj-snapshot. In my script I use
where I start jack I also run aj-snapshot. Whenever an application or
device is connected if it's had previous connections before. My
connections
get re-connected.
Thanks Elijah, will look
into aj-snapshot in comparison to jack_plumbing
as well.
cheers, P
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2130
days inactive
2131
days old
linux-audio-user@lists.linuxaudio.org
7 comments
6 participants
participants (6)
-
Ace Path -
David Runge -
Elijah Abdul Rahman -
Len Ovens -
Paul Davis -
Peter P.