witch Posted February 23, 2016 Posted February 23, 2016 A friend of mine is struggling with this. He is getting this error message: JACK compiled with System V SHM support. loading driver .. apparent rate = 44100 creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit control device hw:0 ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa no message buffer overruns 13:28:04.003 JACK was stopped successfully. 13:28:06.018 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. Can anyone help? I know less than nothing about this stuff!
witch Posted February 23, 2016 Author Posted February 23, 2016 @twin-turbo this is the answer I got: Sound on the system works.Issue is with Jack and therefore any software reliant on it. ..
jinnantonnixx Posted February 23, 2016 Posted February 23, 2016 (edited) Maybe the ALSA plugins are missing: Install libasound2-plugins either from the software centre/synaptic or from the terminal prompt: sudo apt-get install libasound2-plugins I use Jack all the time with MusE sequencer. Edited February 23, 2016 by jinnantonnixx 1
witch Posted February 23, 2016 Author Posted February 23, 2016 Thanks - I'll tell him. Anything else?
twin--turbo Posted February 23, 2016 Posted February 23, 2016 it may be referencing the wrong hardware , if "aplay -l" comes back with more than onde device he will need to experiment starting jackd with different hardware id's don't use JACK, it's rare that I ever use sound of any sort. TT 1
jinnantonnixx Posted February 23, 2016 Posted February 23, 2016 Install qjackctl. Qjackctl offers a user interface for controlling the JACK sound server daemon. At the same time it figures as a JACK patch bay and monitoring tool. This is a graphical control for Jack. From here you can choose the hardware from drop-down boxes. 1
jinnantonnixx Posted February 23, 2016 Posted February 23, 2016 (edited) If all that fails, try deleting the Jack config (don't worry, it will be recreated next time Jackd saves its settings) rm ~/.config/jack/conf.xml Then run the graphical qjackctl tool. Configure Jack to use the hardware it finds, then save the settings. To be fair, I hardly ever get into a tangle even with a couple of different USB sound cards, Jack, ALSA and PulseAudio running together. Edited February 23, 2016 by jinnantonnixx 1
witch Posted February 24, 2016 Author Posted February 24, 2016 thanks guys - something worked so he is OK now
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now