I have successfully installed and used Ardour8 with Musescore3 along with JACK and Qjackctl on my Windows 11 computer using a Focusrite Clarett+ audio interface.
I have now installed Ardour8, Musescore3, JACK and QjackCtl on my MacBook Pro with M4max silicon processor for use with my UA Apollo x8p audio interface. I appear to be getting an error related to a server socket. Here is a portion of the Message output from QjackCtl:
10:20:11.503 Statistics reset.
10:20:11.519 JACK is starting…
10:20:11.519 /usr/local/bin/jackd -v -S -dcoreaudio -dcom_uaudio_driver_UAD2AudioEngine:0 -r48000 -p32
10:20:11.573 JACK was started with PID=1709.
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
Has anyone experienced this type of error on a MacOS system? Does anyone have any idea how to resolve the issue?
With the Apollo on I started the jackd per your excellent suggestion and jackd started and ran without ANY errors or issues. I was able to open QjackCtl and stop and start it and it would Activate.
I was able to configure both Ardour and Musescore in their setup for using Jack. I closed them and opened them both with QjackCtl running and I can see both the Apollo and Ardour created I/O ports in the Graph, but I could not get Musescore’s I/O ports to show up in the Graph like I did on my Windows 11 system.
I may have to create a script file to start jackd before opening QjackCtl.
Any ideas you might have on getting QjackCtl to run jackd would be welcomed for sure. Not sure why Musescore is not being seen in Graph. I’ll have to keep plugging at these issues.
Using the exact same command shown in the output above?
/usr/local/bin/jackd -v -S -dcoreaudio -dcom_uaudio_driver_UAD2AudioEngine:0 -r48000 -p32
There does not appear to be any mention of MacOS on the QJackCtl project page, so perhaps you have found some kind of Mac specific problem in the port to MacOS. Does the jackd installer for MacOS still include QJackCtl as part of the installation? It is not very clear who has worked on the MacOS port recently and who might be able to offer any advice or help.
Yes, I used exactly the line that was in the command you listed. It was copied and pasted.
You raise a great question about whether the jack installation was separate
The JACK and QjackCtl programs came packaged together in
jack2-macOS-universal-v1.9.22.tar. (specifically for M Silicon MacBook Pro processors)
To me this is likely an issue with JACK and QjackCtr configuration. I will see if I can contact the packager of the above tar package to see if they can shed some light on any potential issues with the jackd start line on MacOS 15.
That is exactly why I am still using the latest version of MuseScore 3 (and not 4). I use JACK and Ardour with the latest release of Musescore 3 on my Windows 11 system, routinely.
Note that there is some activity from some interested individuals to provide a Jack enabling plugin for Musescore 4 to bring back JACK capability. You can see the Pull Request postings on Musescores’s web site for the activity. This will be a great thing for Musescore 4 if and when it is completed.
I would much prefer to go to Musescore 4, but I need JACK and I need the panning capabilities that are implemented under the Advanced tab of the Musescore 3 Preferences before going to Musescore 4, which dropped the panning functionality under the Advance tab in the Preferences setup.