You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect the JACK server to start but this is printed in Messages:
13:17:06.188 Statistics reset.
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
The text was updated successfully, but these errors were encountered:
Hello, I had the same issue some days ago on macbook pro m4.
Looking at the logs it seems that the shell command used to run the jackd server is not adding spaces between argument names and argument values.
here are the logs (in the messages tab)
11:28:45.471 /usr/local/bin/jackd -aa -dcoreaudio -D -C"AppleUSBAudioEngine:RODE Microphones:RODE AI-1:86B88917:1,2" -PBuiltInSpeakerDevice
11:28:45.518 JACK was started with PID=74301.
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
When I run this command /usr/local/bin/jackd -aa -dcoreaudio -D -C"AppleUSBAudioEngine:RODE Microphones:RODE AI-1:86B88917:1,2" -PBuiltInSpeakerDevice adding spaces like that in a terminal aside (notice the spaces between -a a for example) /usr/local/bin/jackd -a a -d coreaudio -D -C "AppleUSBAudioEngine:RODE Microphones:RODE AI-1:86B88917:1,2" -P BuiltInSpeakerDevice there is no issue and I'm able to click on start in qjackctl
you need to put a higher timeout in qjackctl for it to work, specially if you get popups asking for microphone access. jack wont properly start until those popups go away, so the qjackctl detection for jack running fails early.
Describe the bug
Jack server cannot be started on M1 macbook.
Environment
Steps To Reproduce
Open QjackCtl, go to Messages.
Expected vs. actual behavior
I expect the JACK server to start but this is printed in Messages:
The text was updated successfully, but these errors were encountered: