27 Oct
2025
27 Oct
'25
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…