9 Feb
2025
9 Feb
'25
10:19 a.m.
Hi list,
I am running an Edirol UA-25 audio interface under jackd2. When I
disconnect the device with jackd running, it will print
ALSA: capture device disconnected
JackAudioDriver::ProcessAsync: read error, stopping...
Jack: JackPosixThread::ThreadHandler : exit
but will not exit, forcing me to kill jackd from the terminal.
Is this intentional behavior? Can I solve this problem and have jackd terminate?
Thanks!
Peter
Here is the full console printout:
$ jackd -v -t2000 -dalsa -r44100 -p512 -n2 -Xseq -D -Chw:UA25 -Phw:UA25 -i2 -o2
jackdmp 1.9.21
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2022 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: capture device hw:UA25
Jack: playback device hw:UA25
Jack: apparent rate = 44100
Jack: frames per period = 512
Jack: JackDriver::Open capture_driver_name = hw:UA25
Jack: JackDriver::Open playback_driver_name = hw:UA25
Jack: Check protocol client = 9 server = 9
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 512
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:UA25|hw:UA25|512|2|44100|2|2|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackSocketServerChannel::Open
Jack: JackServerSocket::Bind : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackSocketServerChannel::BuildPoolTable size = 1
Jack: JackEngine::Open
Jack: JackClientSocket::Connect : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackEngine::ClientInternalOpen: name = freewheel
Jack: JackEngine::AllocateRefNum ref = 1
Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_freewheel val = 0
Jack: JackEngine::NotifyAddClient: name = freewheel
Jack: JackDriver::ClientNotify ref = 1 driver = system name = freewheel notify = 0
Jack: JackDriver::ClientNotify ref = 0 driver = freewheel name = system notify = 0
Jack: JackConnectionManager::DirectConnect first: ref1 = 1 ref2 = 1
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 1 ref2 = 1
Jack: JackDriver::SetupDriverSync driver sem in flush mode
Jack: JackGraphManager::SetBufferSize size = 512
Jack: JackAlsaDriver::Attach fBufferSize 512 fSampleRate 44100
Jack: JackEngine::PortRegister ref = 0 name = system:capture_1 type = 32 bit float mono
audio flags = 22 buffer_size = 512
Jack: JackGraphManager::AllocatePortAux port_index = 1 name = system:capture_1 type = 32
bit float mono audio
Jack: JackConnectionManager::AddOutputPort ref = 0 port = 1
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fCapturePortList[i] 1
Jack: JackEngine::PortRegister ref = 0 name = system:capture_2 type = 32 bit float mono
audio flags = 22 buffer_size = 512
Jack: JackGraphManager::AllocatePortAux port_index = 2 name = system:capture_2 type = 32
bit float mono audio
Jack: JackConnectionManager::AddOutputPort ref = 0 port = 2
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fCapturePortList[i] 2
Jack: JackEngine::PortRegister ref = 0 name = system:playback_1 type = 32 bit float mono
audio flags = 21 buffer_size = 512
Jack: JackGraphManager::AllocatePortAux port_index = 3 name = system:playback_1 type = 32
bit float mono audio
Jack: JackConnectionManager::AddInputPort ref = 0 port = 3
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fPlaybackPortList[i] 3
Jack: JackEngine::PortRegister ref = 0 name = system:playback_2 type = 32 bit float mono
audio flags = 21 buffer_size = 512
Jack: JackGraphManager::AllocatePortAux port_index = 4 name = system:playback_2 type = 32
bit float mono audio
Jack: JackConnectionManager::AddInputPort ref = 0 port = 4
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fPlaybackPortList[i] 4
Jack: Clock source : system clock via clock_gettime
Jack: JackServer::Start
Jack: JackThreadedDriver::Start
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackThreadedDriver::Init real-time
Jack: JackPosixThread::AcquireRealTimeImp priority = 10
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackSocketServerChannel::ClientCreate socket
Jack: JackSocketServerChannel::BuildPoolTable size = 2
Jack: JackSocketServerChannel::BuildPoolTable fSocketTable i = 1 fd = 16
Jack: JackRequest::Notification
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackEngine::ClientNotify: no callback for notification = 4
Jack: JackEngine::ClientNotify: no callback for notification = 4
(here I unplug the usb interface)
ALSA: capture device disconnected
JackAudioDriver::ProcessAsync: read error, stopping...
Jack: JackPosixThread::ThreadHandler : exit
(jackd keeps running)
9 Feb
9 Feb
10:20 a.m.
(following up on my own mail just sent to this list)
For completeness sake, here is the console printout after killing jackd:
Jack: JackServer::Stop
Jack: JackThreadedDriver::Stop
Jack: JackPosixThread::Stop
ALSA: channel flush for playback failed (No such device)
Cannot stop driver
Jack: JackPosixThread::Stop
Jack: JackRequest::Notification
Jack: JackRequest::Notification kQUIT
Jack: JackSocketServerChannel::Execute : JackQuitException
Jack: JackPosixThread::ThreadHandler : exit
Jack: JackEngine::ClientNotify: no callback for notification = 15
Jack: JackEngine::ClientNotify: no callback for notification = 15
Jack: JackServer::Close
Jack: JackServerSocket::Close /dev/shm/jack_default_1000_0
Jack: JackClientSocket::Close
Jack: JackAudioDriver::Detach
Jack: JackEngine::PortUnRegister ref = 0 port_index = 1
Jack: JackEngine::PortDisconnect ref = -1 src = 1 dst = 65535
Jack: JackGraphManager::DisconnectAllOutput port_index = 1
Jack: JackConnectionManager::RemoveOutputPort ref = 0 port_index = 1
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::PortUnRegister ref = 0 port_index = 2
Jack: JackEngine::PortDisconnect ref = -1 src = 2 dst = 65535
Jack: JackGraphManager::DisconnectAllOutput port_index = 2
Jack: JackConnectionManager::RemoveOutputPort ref = 0 port_index = 2
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::PortUnRegister ref = 0 port_index = 3
Jack: JackEngine::PortDisconnect ref = -1 src = 3 dst = 65535
Jack: JackGraphManager::DisconnectAllInput port_index = 3
Jack: JackConnectionManager::RemoveInputPort ref = 0 port_index = 3
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::PortUnRegister ref = 0 port_index = 4
Jack: JackEngine::PortDisconnect ref = -1 src = 4 dst = 65535
Jack: JackGraphManager::DisconnectAllInput port_index = 4
Jack: JackConnectionManager::RemoveInputPort ref = 0 port_index = 4
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackEngine::ClientNotify: no callback for notification = 10
Jack: JackDriver::Close
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Jack: JackGraphManager::DisconnectRefNum cur_index = 1 ref1 = 0 ref2 = 0
Jack: JackEngine::ClientInternalClose ref = 0
Jack: JackEngine::ClientCloseAux ref = 0
Jack: JackGraphManager::RemoveAllPorts ref = 0
Jack: JackDriver::ClientNotify ref = 0 driver = freewheel name = system notify = 1
Jack: JackPosixThread::Stop
Released audio card Audio2
audio_reservation_finish
Jack: JackDriver::Close
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 1 ref2 = 1
Jack: JackGraphManager::DisconnectRefNum cur_index = 1 ref1 = 1 ref2 = 1
Jack: JackEngine::ClientInternalClose ref = 1
Jack: JackEngine::ClientCloseAux ref = 1
Jack: JackGraphManager::RemoveAllPorts ref = 1
Jack: JackEngine::Close
Jack: JackClientSocket::Close
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: JackPosixThread::ThreadHandler : exit
Jack: Succeeded in unlocking 107341340 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: ~JackDriver
Jack: Succeeded in unlocking 1196 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
4:38 p.m.
On Sun, 9 Feb 2025, Peter P. wrote:
I am running an Edirol UA-25 audio interface under jackd2. When I
disconnect the device with jackd running, it will print
A long time ago, when jackd was designed, there were audio interfaces that
would fit in one of the mother board slots. They were called ISA slots.
These audio cards could only be removed when the beast was powered down.
Jackd is a manually set up utility, it is told the device name at start
and as such, it has no idea what to do when that device vanishes. It is
possible with the tools supplied to tell jack to change it's device or
backend while running via dbus. I have had varying amounts of success
doing this after the USB device has been pulled. I would guess that
because it is possible to change the device like this, jackdbus continues
to run in hopes something else will happen.
Basically, a device vanishing in an audio context is a system failure. USB
might be designed for hot plugging but jackd is not.
--
Len Ovens
www.ovenwerks.net
5:08 p.m.
Hi,
Long-time lurker, first time posting ...
On 2/9/25 10:38 AM, Len Ovens wrote:
On Sun, 9 Feb 2025, Peter P. wrote:
I use JACK in the (US) broadcast industry, mostly with Rivendell radio
automation (https://rivendellaudio.org/).
After being frustrated at the "hot plug" nature of USB and the lack of
it with JACK I came up with a (pretty kludgy) workaround: using udev
rules and a simple shell script to add and remove jack clients from the
graph.
With a rule like the one below for example (watch the wrap):
# Focusrite Scarlett 4i4: 1235:8212
ACTION=="add", ATTR{idVendor}=="1235",
ATTR{idProduct}=="8212",
ENV{JACK_PROMISCUOUS_SERVER}="audio",
RUN+="/usr/local/bin/jack-reconnect -v -v USB Scarlett4i4-1"
and the ZSH script at
https://github.com/opensourceradio/ram/blob/master/usr/local/bin/jack-recon…
one can "automatically" have one's Scarlett 4i4 (with USB ID 1235:8212)
connect and be inserted into the jack graph each time it is plugged in.
In case it's not obvious, this works only on Linux with a working udev
installation.
~David Klann
I am running an Edirol UA-25 audio interface under jackd2. When I
disconnect the device with jackd running, it will print
A long time ago, when jackd was designed, there were audio interfaces that
would fit in one of the mother board slots. They were called ISA slots.
These audio cards could only be removed when the beast was powered down.
Jackd is a manually set up utility, it is told the device name at start
and as such, it has no idea what to do when that device vanishes. It is
possible with the tools supplied to tell jack to change it's device or
backend while running via dbus. I have had varying amounts of success
doing this after the USB device has been pulled. I would guess that
because it is possible to change the device like this, jackdbus continues
to run in hopes something else will happen.
Basically, a device vanishing in an audio context is a system failure. USB
might be designed for hot plugging but jackd is not.
--
Len Ovens
www.ovenwerks.net
_______________________________________________
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
6:12 p.m.
* David Klann <dxklann(a)pm.me> [2025-02-09 18:08]:
Hi,
Long-time lurker, first time posting ...
On 2/9/25 10:38 AM, Len Ovens wrote:
Thanks David, nice to be reading your (first) post to this list! Your
solution looks intriguing! I did not know that one can add devices to
existing jack graphs, always thought that only software clients can
connect to it(?).
best, P
On Sun, 9 Feb 2025, Peter P. wrote:
I use JACK in the (US) broadcast industry, mostly with Rivendell radio
automation (https://rivendellaudio.org/).
After being frustrated at the "hot plug" nature of USB and the lack of
it with JACK I came up with a (pretty kludgy) workaround: using udev
rules and a simple shell script to add and remove jack clients from the
graph.
With a rule like the one below for example (watch the wrap):
# Focusrite Scarlett 4i4: 1235:8212
ACTION=="add", ATTR{idVendor}=="1235",
ATTR{idProduct}=="8212",
ENV{JACK_PROMISCUOUS_SERVER}="audio",
RUN+="/usr/local/bin/jack-reconnect -v -v USB Scarlett4i4-1"
and the ZSH script at
https://github.com/opensourceradio/ram/blob/master/usr/local/bin/jack-recon…
one can "automatically" have one's Scarlett 4i4 (with USB ID 1235:8212)
connect and be inserted into the jack graph each time it is plugged in.
In case it's not obvious, this works only on Linux with a working udev
installation.
I am running an Edirol UA-25 audio interface under jackd2. When I
disconnect the device with jackd running, it will print
A long time ago, when jackd was designed, there were audio interfaces that
would fit in one of the mother board slots. They were called ISA slots.
These audio cards could only be removed when the beast was powered down.
Jackd is a manually set up utility, it is told the device name at start
and as such, it has no idea what to do when that device vanishes. It is
possible with the tools supplied to tell jack to change it's device or
backend while running via dbus. I have had varying amounts of success
doing this after the USB device has been pulled. I would guess that
because it is possible to change the device like this, jackdbus continues
to run in hopes something else will happen.
Basically, a device vanishing in an audio context is a system failure. USB
might be designed for hot plugging but jackd is not.
6:08 p.m.
Hi Len,
* Len Ovens <len(a)ovenwerks.net> [2025-02-09 17:45]:
[...]
Jackd is a manually set up utility, it is told the
device name at start and
as such, it has no idea what to do when that device vanishes. It is possible
with the tools supplied to tell jack to change it's device or backend while
running via dbus. I have had varying amounts of success doing this after the
USB device has been pulled. I would guess that because it is possible to
change the device like this, jackdbus continues to run in hopes something
else will happen.
following up your kind reply, I discovered that I had disabled the "JACK D-Bus
interface" in qjackctl and enabled it now.
I am still wondering about the difference between qjackctl's "JACK D-Bus
interface" and its "D-Bus interface" by the way. Enabled both.
Now qjackctl will apparently launch jackdbus instead of jackd.
Unplugging the devuce while jackdbus runs will yield
ERROR: ALSA: capture device disconnected
ERROR: JackAudioDriver::ProcessAsync: read error, stopping...
and jackdbus keeps running. Qjackctl will show "started" status.
Clicking onto its "Stop" button, will freeze qjackctl for a long time
until it posts:
Client deactivated.
D-BUS: JACK server is stopping...
ERROR: JackPosixProcessSync::LockedTimedWait error usec = 20000000 err = Connection timed
out
ERROR: JackEngine::ClientDeactivate wait error ref = 3 name = qjackctl
ERROR: JackPosixProcessSync::LockedTimedWait error usec = 4000000 err = Connection timed
out
ERROR: JackEngine::ClientCloseAux wait error ref = 3
Client 'qjackctl' with PID 1847586 is out
Stopping jack server...
ERROR: JackPosixProcessSync::LockedTimedWait error usec = 20000000 err = Connection timed
out
ERROR: JackEngine::ClientDeactivate wait error ref = 2 name = dbusapi
ERROR: failed to deactivate dbusapi jack client. error is -1
2025: Client 'system' with PID 0 is out
D-BUS: JACK server was stopped (org.jackaudio.service aka jackdbus).
ERROR: JackPosixProcessSync::LockedTimedWait error usec = 4000000 err = Connection timed
out
ERROR: JackEngine::ClientCloseAux wait error ref = 2
ERROR: ALSA: channel flush for playback failed (No such device)
ERROR: Cannot stop driver
ERROR: control open "hw:UA25" (No such device)
ERROR: control open "hw:UA25" (No such device)
Jackdbus is still running, also when quitting qjackctl. Reconnecting the usb device and
starting via a new qjackctl will not work, reporting
D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Could not connect to JACK server as client. - Overall operation failed. - Unable to
connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Starting jack server...
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
ERROR: cannot register object path "/org/freedesktop/ReserveDevice1/Audio2": A
handler is already registered for /org/freedesktop/ReserveDevice1/Audio2
ERROR: Failed to acquire device name : Audio2 error : A handler is already registered for
/org/freedesktop/ReserveDevice1/Audio2
ERROR: Audio device hw:UA25 cannot be acquired...
ERROR: Cannot initialize driver
ERROR: JackServer::Open failed with -1
ERROR: Failed to open server
Saving settings to "/home/peter/.config/jack/conf.xml" ...
So this is basically the same behavior as with jackd before.
I am curious what the intended behavior with jackdbus and qjackctl is
supposed to be, given that it all is set up correctly.
I might look closer into dbus syslogs unless someone tells me that there
are certain usb audio cards, which do not signal to dbus properly.
Basically, a device vanishing in an audio context is a
system failure. USB
might be designed for hot plugging but jackd is not.
Good point Len! I find that
jackd/jackdbus should exit nevertheless in such cases.
Again, thanks for the help!
best, P
6:16 p.m.
Am 09.02.25 um 19:08 schrieb Peter P.:
I am still wondering about the difference between
qjackctl's "JACK D-Bus
interface" and its "D-Bus interface" by the way. Enabled both.
One is the D-BUS interface that jackdbus provides and, when enabled,
causes qjackctl to start/ connect to jackdbus instead of running jackd,
the other is the D-BUS interface which the qjackctl application
provides, which you probably won't need.
Hth, Chris
80
days inactive
80
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Christopher Arndt -
David Klann -
Len Ovens -
Peter P.