You are not logged in.
Look at the second post below. I have previously used Pulseaudio but uninstalled it and removed ~/.asoundrc configured to work with it. Now I installed jack2-dbus. First, when I tried `jack_control start`, I got this error: `DBus exception: org.jackaudio.Error.Generic: Failed to open server alsa`. It worked when I used `sudo`. After a reboot the behaviour reversed - works only when I don't use sudo. While JACK is running, I tried opening patchage to have a look. The "Dropouts" field shows a steadily and quickly increasing number. Trying to run any audio applications, all I hear are crackling sounds.
Also I copied the configuration lines from the sample script on the wiki, and this is how I start jack:
jack_control start
sudo schedtool -R -p 20 `pidof jackdbus`
jack_control eps realtime true
jack_control ds alsa
jack_control dps device hw:HD2
jack_control dps rate 48000
jack_control dps nperiods 2
jack_control dps period 64Trying to run JACK using qjackctl, I get this message:
15:14:36.718 Statistics reset.
15:14:36.720 ALSA connection change.
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
15:14:36.828 ALSA connection graph change.
15:14:39.258 JACK is starting...
15:14:39.258 jackd -dalsa -dhw:SB,0 -r48000 -p1024 -n2 -Xseq
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
15:14:39.308 Could not start JACK. Sorry.
15:14:41.368 JACK was stoppedNot sure what more I can do, hope you can help.
Last edited by Ploppz (2016-07-04 23:20:56)
Offline
I decided after all to go with PulseAudio. After doing everything that is said here and here, using qjackctl, I get the same errors as before. Using the script that uses jack_control, it starts just fine, but there is no sound output from any applications. Here's Patchage and Pavucontrol: http://imgur.com/a/X5oZb The 'Dropouts' field in Patchage is still ever increasing.
Last edited by Ploppz (2016-07-04 23:21:19)
Offline
Is your user added to 'audio' group? Did you try increasing the 'period' settings to reduce dropouts?
If you use qjackctl with jack2-dbus, you should enable "Setup->Misc->Enable JACK D-Bus interface". Otherwise it will try to use the legacy jackd, which isn't included in jack2-dbus package.
Also you seem to be using different alsa device with qjackctl and your jack_control script.
Offline
Yes I'm in the audio group. I enabled JACK D-Bus interface and tried with qjackctl, and it started successfully, however, there was still no sound. I set 'Periods/Buffer' to 50, but this time I got errors when I tried to start it. Rebooted and set Periods/Buffer back to 2 like it was before, and when I try to start it, I get these errors (same as with 50 Periods/Buffer):
10:09:29.279 D-BUS: JACK server could not be started. Sorry
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
Tue Jul 5 10:09:29 2016: Starting jack server...
Tue Jul 5 10:09:29 2016: JACK server starting in realtime mode with priority 10
Tue Jul 5 10:09:29 2016: self-connect-mode is "Don't restrict self connect requests"
Tue Jul 5 10:09:29 2016: ERROR: cannot register object path "/org/freedesktop/ReserveDevice1/Audio0": A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Tue Jul 5 10:09:29 2016: ERROR: Failed to acquire device name : Audio0 error : A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Tue Jul 5 10:09:29 2016: ERROR: Audio device hw:SB,0 cannot be acquired...
Tue Jul 5 10:09:29 2016: ERROR: Cannot initialize driver
Tue Jul 5 10:09:29 2016: ERROR: JackServer::Open failed with -1
Tue Jul 5 10:09:29 2016: ERROR: Failed to open server
Tue Jul 5 10:09:30 2016: Saving settings to "/home/ploppz/.config/jack/conf.xml" ...
10:09:32.582 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 startedjack_control started jack without problems before the reboot, but now it has that error 'DBus exception: org.jackaudio.Error.Generic: Failed to open server' again.
Using jack_control, I think hw:HD2 is not right, seems like it's my webcam.. Doesn't make a difference but I tried with hw:SB,0 and hw:0,0. Not sure how I can find out what is the right device. These are the devices listed in qjackctl: http://i.imgur.com/FgS6piB.png
Last edited by Ploppz (2016-07-05 08:20:43)
Offline
The error seems like some application was already reserving your sound card, but it could be anything else. You could try 'jack_control exit' to kill jackdbus in case it was already running.
It's probably simpler to get jack working with bare alsa, and without pulseaudio, as PA's jack modules can be quirky.
periods/buffer should be 2 or 3 depending on your soundcard. I meant try increasing frames/period (jack_control dps period) to e.g. 1024. When you get jack working, you can reduce it until you start getting xruns, to improve latency.
You should know yourself which device you want to use for output. It seems like hw:0 would be the sound chip on your motherboard and hw:1 probably your graphics cards hdmi port.
Offline
After jack_coltrol exit, I can indeed start qjackctl! But there's still no sound. I can have mpd playing a song, and it gets silenced while JACK is running, and unsilenced when it exits. Frames/period = 2048 now.
Offline
