26 Oct
2025
26 Oct
'25
4:21 p.m.
I've been having problems with connections between jack clients dropping
out.
I would like to have a program that monitors the state of connections.
I've worked out how to locate the end client ports, but I don't want to
have
poll the connections at frequent intervals. Is there any way I can get a
callback when either of the clients drops out?
I suppose I could set up links between by monitor and the two client ports
and activate those connections, but that seems like overkill. Is there
an easier way.
I'm actually using pipewire-jack but don't know enough about pipewire to
do it
directly.
Bill
--
+---------------------------------------------+
| Bill Purvis G8DIO |
|bill(a)billp.org |
+---------------------------------------------+
26 Oct
26 Oct
10:31 p.m.
I've been having problems with connections between
jack clients dropping out.
I would like to have a program that monitors the state of connections.
I use `watch jack_lsp -c`
If it is too inconvenient to see that much I filter it with grep.
Is that not possible or suitable?
On Monday, 10/27/25 at 04:22 Bill Purvis <bill(a)billp.org> wrote:
I've been having problems with connections between
jack clients dropping out.
I would like to have a program that monitors the state of connections.
>
I've worked out how to locate the end client ports, but I don't want to have
> poll the connections at frequent intervals. Is there any way I can get a
> callback when either of the clients drops out?
>
> I suppose I could set up links between by monitor and the two client ports
> and activate those connections, but that seems like overkill. Is there an easier way.
>
> I'm actually using pipewire-jack but don't know enough about pipewire to do
it
> directly.
>
> Bill
>
> --
> +---------------------------------------------+
> | Bill Purvis G8DIO |
> |
> bill(a)billp.org
> |
> +---------------------------------------------+
27 Oct
27 Oct
5:55 a.m.
Hi there!
You may find jack_plumb useful.
It monitors and makes connections "sticky".
If connections drops but then the client congress back again, it'll be
reconnected immediately.
I am not using pipewire, but I hope this can work normally there too.
Hope this helps.
Athanasios
On Sun, Oct 26, 2025, 23:31 Worik <root(a)worik.org> wrote:
I've been
having problems with connections between jack clients
dropping out.
I would like to have a program that monitors the
state of connections.
I use `watch jack_lsp -c`
If it is too inconvenient to see that much I filter it with grep.
Is that not possible or suitable?
On Monday, 10/27/25 at 04:22 Bill Purvis <bill(a)billp.org> wrote:
I've been having problems with connections between jack clients dropping
out.
I would like to have a program that monitors the state of connections.
I've worked out how to locate the end client ports, but I don't want to
have
poll the connections at frequent intervals. Is there any way I can get a
callback when either of the clients drops out?
I suppose I could set up links between by monitor and the two client ports
and activate those connections, but that seems like overkill. Is there an
easier way.
I'm actually using pipewire-jack but don't know enough about pipewire to
do it
directly.
Bill
--
+---------------------------------------------+
| Bill Purvis G8DIO |
| bill(a)billp.org |
+---------------------------------------------+
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user(a)lists.linuxaudio.org
To unsubscribe send an email to
linux-audio-user-leave(a)lists.linuxaudio.org
1:44 p.m.
On 26/10/2025 21:31, Worik wrote:
Thanks!
I'm currently doing a variant of that - using a bash script instead of
watch.
I append the source port name, and pipe the result through 'wc -l'.
There are actually
five source ports, so if all is well I get a value of 10 returned.
Anything less
suggests one or more of the connections has failed.
Just installed it on the organ this morning, and it looks to be working OK.
Currently it attempts to reconnect all five connections, I may refine it to
check the individual connections. If only one has dropped out the reconnect
script get several error messages to say it can't reconnect as it is already
connected!
I'm toying with using the jack_set_graph_order_callback to get an explicit
trigger to do the reconnect. That way I don't need to poll using jack_lsp
every 10 seconds. Needs a bit more experimenting to build the code to
do this.
Thanks also to Kjetil Matheussen who suggested this!
Bill
--
+---------------------------------------------+
| Bill Purvis G8DIO |
|bill(a)billp.org |
+---------------------------------------------+
I've been
having problems with connections between jack clients
dropping out.
I would like to have a program that monitors the
state of connections.
I use `watch jack_lsp -c`
If it is too inconvenient to see that much I filter it with grep.
Is that not possible or suitable? 
5:12 p.m.
Check out jack_evmon ....
On Mon, Oct 27, 2025 at 6:44 AM Bill Purvis <bill(a)billp.org> wrote:
On 26/10/2025 21:31, Worik wrote:
I've been having problems with connections
between jack clients
dropping out.
I would like to have a program that monitors the
state of connections.
I use `watch jack_lsp -c`
If it is too inconvenient to see that much I filter it with grep.
Is that not possible or suitable?
Thanks!
I'm currently doing a variant of that - using a bash script instead of
watch.
I append the source port name, and pipe the result through 'wc -l'. There
are actually
five source ports, so if all is well I get a value of 10 returned.
Anything less
suggests one or more of the connections has failed.
Just installed it on the organ this morning, and it looks to be working OK.
Currently it attempts to reconnect all five connections, I may refine it to
check the individual connections. If only one has dropped out the reconnect
script get several error messages to say it can't reconnect as it is
already
connected!
I'm toying with using the jack_set_graph_order_callback to get an explicit
trigger to do the reconnect. That way I don't need to poll using jack_lsp
every 10 seconds. Needs a bit more experimenting to build the code to
do this.
Thanks also to Kjetil Matheussen who suggested this!
Bill
--
+---------------------------------------------+
| Bill Purvis G8DIO |
| bill(a)billp.org |
+---------------------------------------------+
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user(a)lists.linuxaudio.org
To unsubscribe send an email to
linux-audio-user-leave(a)lists.linuxaudio.org
1:17 p.m.
On 26/10/2025 16:21, Bill Purvis wrote:
I've been having problems with connections between
jack clients dropping
out.
I would like to have a program that monitors the state of connections.
I've worked out how to locate the end client ports, but I don't want to
have
poll the connections at frequent intervals. Is there any way I can get a
callback when either of the clients drops out?
I suppose I could set up links between by monitor and the two client ports
and activate those connections, but that seems like overkill. Is there
an easier way.
I'm actually using pipewire-jack but don't know enough about pipewire to
do it
directly.
If I understand correctly what you are trying to achieve, I have used
the QJackCtl 'Patchbay' for this, especially in live situations where I
need to plug/unplug a midi (USB) controller in or (re)start a bunch of
applications like Yoshimi with a new state and/or Pd, etc.
This is a detailed explanation of how it works... Although admittedly I
often just set-up connections as needed and create a new patchbay based
on the current 'snapshot':
https://www.rncbc.org/drupal/comment/1743
In the past I have also used aj-snapshot [1] for a command-line approach
and embedded in scripts as it can also store/retrieve snapshots in
files. This only works with Midi connections (ALSA and/or JACK) (but
then many applications allow to 'auto-connect' audio ports, so YMMV)
Finally, it seems qpwgraph [2], connection manager for PipeWire has a
similar 'patchbay' functionality [3]. I haven't tried it much because
all pipewire 'managers' seem to ignore ALSA MIDI which I am still using
quite a lot, and the 'Midi Bridge' is not working at best on jack-midi
clients' sides..
Hope this helps,
Lorenzo
[1] https://aj-snapshot.sourceforge.io/
[2] https://gitlab.freedesktop.org/rncbc/qpwgraph
[3]
https://gitlab.freedesktop.org/rncbc/qpwgraph/-/blob/main/docs/qpwgraph_pat…
9:12 p.m.
On 10/27/25 5:17 AM, Lorenzo Sutton wrote:
On 26/10/2025 16:21, Bill Purvis wrote:
Just to clarify. aj-snapshot supports connecting audio ports with JACK.
We used this intensively for connecting Jacktrip clients using
aj-snapshot's daemon mode.
-- Nils
I've been having problems with connections
between jack clients
dropping out.
I would like to have a program that monitors the state of connections.
I've worked out how to locate the end client ports, but I don't want
to have
poll the connections at frequent intervals. Is there any way I can get a
callback when either of the clients drops out?
I suppose I could set up links between by monitor and the two client
ports
and activate those connections, but that seems like overkill. Is
there an easier way.
I'm actually using pipewire-jack but don't know enough about pipewire
to do it
directly.
If I understand correctly what you are trying to achieve, I have used
the QJackCtl 'Patchbay' for this, especially in live situations where
I need to plug/unplug a midi (USB) controller in or (re)start a bunch
of applications like Yoshimi with a new state and/or Pd, etc.
This is a detailed explanation of how it works... Although admittedly
I often just set-up connections as needed and create a new patchbay
based on the current 'snapshot':
https://www.rncbc.org/drupal/comment/1743
In the past I have also used aj-snapshot [1] for a command-line
approach and embedded in scripts as it can also store/retrieve
snapshots in files. This only works with Midi connections (ALSA and/or
JACK) (but then many applications allow to 'auto-connect' audio ports,
so YMMV)
Finally, it seems qpwgraph [2], connection manager for PipeWire has a
similar 'patchbay' functionality [3]. I haven't tried it much because
all pipewire 'managers' seem to ignore ALSA MIDI which I am still
using quite a lot, and the 'Midi Bridge' is not working at best on
jack-midi clients' sides..
Hope this helps,
Lorenzo
[1] https://aj-snapshot.sourceforge.io/
[2] https://gitlab.freedesktop.org/rncbc/qpwgraph
[3]
https://gitlab.freedesktop.org/rncbc/qpwgraph/-/blob/main/docs/qpwgraph_pat…
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user(a)lists.linuxaudio.org
To unsubscribe send an email to
linux-audio-user-leave(a)lists.linuxaudio.org
3:55 p.m.
On Sun, Oct 26, 2025 at 03:21:31PM +0000, Bill Purvis wrote:
I've been having problems with connections between
jack clients dropping
out.
Do you mean connections drop out without any reason while the ports
still exist ? This shouldn't happen unless something is doing this
explicitly. I've never noticed such a thing in +20 years of using
Jack. What I have seen is e.g. qjackctl's connection window showing
false information.
So the first thing to do would be to find out why this happens...
Jack also has a port_(dis)connect callback, it would be interesting
to see if this is called. All you'd need is a simple client that
using this callback and printing out its arguments.
Caio,
--
FA
5:32 p.m.
Hi Fons,
On 27/10/2025 14:55, Fons Adriaensen wrote:
On Sun, Oct 26, 2025 at 03:21:31PM +0000, Bill Purvis
wrote:
My current
thinking is that the U-DAC8 is occasionally restarting,
possibly a loose
USB socket. I've just switched to a Gigaport-eX, which has a USB-C
connector and will
keep an eye on it. I've now installed a rather crude monitor script that
attempt to reconnect
if it detects any such interruption, i.e. the connections dropping.
I've been having problems with connections
between jack clients dropping
out.
Do you mean connections drop out without any reason while the ports
still exist ? This shouldn't happen unless something is doing this
explicitly. I've never noticed such a thing in +20 years of using
Jack. What I have seen is e.g. qjackctl's connection window showing
false information.
So the first thing to do would be to find out why this happens... Jack also has a port_(dis)connect callback, it would
be interesting
to see if this is called. All you'd need is a simple client that
using this callback and printing out its arguments.
I'm currently playing about
with various jack callbacks, just need to be
careful
about what I do in the callbacks. I'm trying to avoid things like
qjackctl, qpwgraph,
as the system normally runs headless. Sticking with little bits of C
code and shell
scripts. I do use qpwgraph for debugging things as I do have the monitor
plugged in
then, but 'normal' usage is just to power up the PC and start the organ
software from
an autostart script.
--
+---------------------------------------------+
| Bill Purvis G8DIO |
|bill(a)billp.org |
+---------------------------------------------+
1
days inactive
2
days old
linux-audio-user@lists.linuxaudio.org
9 comments
7 participants
participants (7)
-
Athanasios Silis -
Bill Purvis -
Fons Adriaensen -
Lorenzo Sutton -
Nils Tonnätt -
Paul Davis -
Worik