I cannot use QjackCtl when it was started from the Finder (double click e.g. directly in /opt/homebrew/Cellar/qjackctl/1.0.0/qjackctl.app). The GUI opens as usual, but initializing the JACK server always results in the following verbose error messages:
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 start JACK. Sorry.
JACK was stopped
However, starting QjackCtl via terminal and subsequent initialization of the JACK server works without issues.
I'm running QjackCtl 1.0.0 via homebrew on Apple M1 Pro with MacOS 14.5. I have not encountered such problem on any Intel Mac before.
This may be another "walled garden" problem, but do you have any idea what may cause the problem or how to investigate?
I cannot use QjackCtl when it was started from the Finder (double click e.g. directly in
/opt/homebrew/Cellar/qjackctl/1.0.0/qjackctl.app). The GUI opens as usual, but initializing the JACK server always results in the following verbose error messages:However, starting QjackCtl via terminal and subsequent initialization of the JACK server works without issues.
I'm running QjackCtl 1.0.0 via homebrew on Apple M1 Pro with MacOS 14.5. I have not encountered such problem on any Intel Mac before.
This may be another "walled garden" problem, but do you have any idea what may cause the problem or how to investigate?