Hi folks, I use jack for returning my own voice in the headphone without
latency. I have a MacBook Pro with M1 chip. I installed the universal
installer for macOS, and it was working fine, however, after installing the
last update of the OS, called Sonoma, jack stopped working. I use it with
QjackCtl, and I get the following error message:
Could not connect to JACK server as client.
- Overall operation failed.
- Unable to connect to the server.
Please check the message window for more info.
In the message window, I get the following logs:
12:59:38.454 Statistics reset.
12:59:38.465 JACK is starting...
12:59:38.465 /usr/local/bin/jackd -dcoreaudio -r44100 -p256 -D
-CBuiltInHeadphoneInputDevice -PBuiltInHeadphoneOutputDevice
12:59:38.512 JACK was started with PID=37727.
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
jackdmp 1.9.22
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2023 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"
Separated input = 'MacBook Pro Microphone'
Separated output = 'MacBook Pro Speakers'
12:59:41.013 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
Input channel = 0 ==> JACK input port = 0
JACK output port = 0 ==> output channel = 0
JACK output port = 1 ==> output channel = 1
CoreAudio driver is running...
12:59:47.591 JACK is stopping...
Jack main caught signal 15
12:59:47.632 JACK was stopped I would appreciate any help about this issue,
Rodrigo
Hello everyone.
I have been trying to get this for many weeks.
I want to use a Pi (any Pi) with a sound device on a private wired network as an output device (with a sound device attached).
It has been very confusing trying to figure out what to use, considering that now PipeWire seems to have taken over everything and it seems to emulate the behavior of Jack2 and PulseAudio.
I can get it working as long as everything is Linux, but that seems to be only when PipeWire emulates PulseAudio.
When I try to put Windows into the mix, I find that there is really no support for PulseAudio in Windows.
So I fall back to trying to use Jack2.
It looks like it should be so simple, but I'm not getting anywhere.
I am able to setup what looks like a connection by running jackd on the Pi as:
#Server
jackd -d alsa -d hw:3 -r48000 -S &
jack_load netmanager -i"-a 10.1.1.10 -p 19000"
And jackd on the Windows machine as:
#Client
jackd -R -P 70 -d net -a 10.1.1.10 -p 19000
When I open the Graph in qjackctl on the Pi, I can see the Windows client device objects when the jackd server is running on the Windows machine.
I have no idea how to play a wav file from Windows into this connection.
Any help would be greatly appreciated!
Thanks!
James.
Hi there,
I'm a bit frustrated, because I am setting up a sound installation out
of reach, and need a remote shutdown key. I had a Logitech R400
presenter lying around, so I tried that. It works fine on my laptop
(Debian 12), using KeyState UGen in SuperCollider. But on th RPi 4B
(Raspbian 11, for reasons) as soon as jackd is started, the keyboard
input is blocked and doesn't register.
I first thought, it might be that the Logitech uses bluetooth or
something similar, so I got a Flirc USB dongle. The same behaviour:
works fine on the desktop, but on the Pi, as soon as jackd starts, input
is no longer received. If I kill jackd, keyboard input comes back
immediately.
I tried to use different USB ports, makes no difference. The audio
device in a trusty Logilink UA0099 class compliant USB interface. (To
reiterate, using this same setup on my laptop has no issues).
Any help is appreciated.
Best, .h.h.
Hi all -
I hope I'm in the right place. I've tried a few different forums and
message boards now with no response.
I am attempting to run an AudioInjector Octo (a simple 8-channel audio
hardware card attached to the GPIO) on a Raspberry Pi 4, running the
Raspberry Lite OS.
My understanding is that ALSA manages AudioInjector - but that I also need
jackd to send audio from my software (SuperCollider) to ALSA.
While ALSA seems to read the AudioInjector without trouble, I seemingly
cannot get jackd to boot. I am new to all of this, so there may be many
things I have not yet tried.
Namely, the following line of code causes my terminal prompt to freeze:
jackd -d alsa -r 44100 -P hw:2
Any pointers would be a great help. Thanks!
The external USB midi port shows up in the qjackctl graph.
The midi dongle works fine in other Windows apps. It was also working
with jack not long ago since then I have upgraded the PC and reinstalled
Windows.
Windows version is 10.
qjackctl messages:
03:45:32.764 Statistics reset.
03:45:37.209 JACK is starting...
03:45:37.210 D:/msys64/ucrt64/bin/jackd.exe -S -X winmme -dportaudio
03:45:37.281 JACK was started with PID=11604.
jackdmp 1.9.22
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2023 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
Drivers/internals found in : D:\msys64\ucrt64\lib\jack
Drivers/internals found in : D:\msys64\ucrt64\lib\jack
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
03:45:39.479 JACK connection change.
03:45:39.483 Server configuration saved to "D:\msys64\home\johnm/.jackdrc".
03:45:39.486 Statistics reset.
03:45:39.492 Client activated.
03:45:39.493 Patchbay deactivated.
03:45:39.519 JACK connection graph change.
\\ midi keyboard note pressed here
03:46:24.154 Shutdown notification.
03:46:24.169 Client deactivated.
03:46:24.178 JACK is being forced...
03:46:24.379 JACK was stopped
.jackdrc:
D:/msys64/ucrt64/bin/jackd.exe -S -X winmme -dportaudio
commandline:
$ qjackctl
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0
err = 2
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 named pipe after wait = \\.\pipe\server_jack_default_0
err = 2
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
\\ midi keyboard note pressed here
CheckRes error
JackWinNamedPipeClientChannel read fail
Server is not running
Server is not running
