I’ve successfully setup SC on Ubuntu and Fedora, but on Arch (which I wanted to try because it comes with Qt 5.15, which I’m hoping would solve some wayland bugs) I’m having some jackd issues.
Basically, SC plays for a few seconds (some totally basic
Synth(\default) output) but then it auto-kills jackd without any other user invention and posts this:
JackDriver: killed by jack Server 'localhost' exited with exit code 0. server 'localhost' disconnected shared memory interface
The longest I’ve managed to run a Synth is about one minute, it usually dies much faster, in about 10-15 seconds.
Any ideas what could be causing this?
Also, while it playes, the CPU usage is substantially higher than on the other distros, about 10% for just that synth. The latter might have something to do with the fact that jackd refused to work on Arch without me following its demands and setting
Please check your /etc/security/limits.conf for the following line and correct/add it if necessary: @audio - rtprio 99
And desipte that, I see with
qjackclt a ton of xruns, which seem to explain the quit as well
subgraph starting at SuperCollider timed out (subgraph_wait_fd=9, status = 0, state = Running, pollret = 0 revents = 0x0) internal poll failure reading response from client SuperCollider to a xrun event **** alsa_pcm: xrun of at least 0.201 msecs 23:41:47.675 JACK connection graph change. 23:41:47.877 JACK connection change. 23:42:12.645 XRUN callback (150). delay of 23605.000 usecs exceeds estimated spare time of 21228.000; restart ... **** alsa_pcm: xrun of at least 0.455 msecs 23:42:14.340 XRUN callback (1 skipped). 23:43:15.288 XRUN callback (152). delay of 21880.000 usecs exceeds estimated spare time of 21289.000; restart ... **** alsa_pcm: xrun of at least 0.106 msecs 23:43:16.972 XRUN callback (1 skipped). 23:44:48.713 XRUN callback (154). delay of 22506.000 usecs exceeds estimated spare time of 21258.000; restart ... **** alsa_pcm: xrun of at least 0.177 msecs 23:44:49.923 XRUN callback (1 skipped). 23:45:01.917 XRUN callback (156). delay of 22705.000 usecs exceeds estimated spare time of 21317.000; restart ... **** alsa_pcm: xrun of at least 0.120 msecs 23:45:02.118 XRUN callback (1 skipped). 23:45:08.778 XRUN callback (158). delay of 30736.000 usecs exceeds estimated spare time of 21316.000; restart ... **** alsa_pcm: xrun of at least 0.374 msecs 23:45:10.191 XRUN callback (1 skipped).
Any ideas how to fix this? I’m getting no xruns on Ubuntu or Fedora… (I haven’t actually got to enabling wayland on Arch, so that’s unrelated to this jackd issue.)
Also, I have jack not jack2 installed on Arch, if that makes any difference… I suspect that’s the problem though. Ubuntu has separate packages but only installed jack2 for me. Fedora calls it jack-audio-connection-kit, but that’s actually jack2 given the version (1.9.14); jack1 has some version 0.125. From their FAQ:
So what about the version numbers ? Jack 1 approaches version 1.0. At the time of writing it is at version 0.121.3. Jack 2 approaches version 2.0 - at the time of writing it is at version 1.9.10. run
jackd --versionto find out the version that you have installed.
The trouble is that pacman wants to remove 259 packages on Arch to get rid of jack (1)… which seems a bit much…