Re: [Alsa-user] Issue starting JACK
Ok. Here is the output: bash-5.0$ pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process bash-5.0$ killall -KILL jackd jackd: no process found bash-5.0$ jackd --sync -P80 -ndefault -dalsa -dhw:Generic -r441 jackd 0.125.0 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 441 creating alsa driver ... hw:Generic|hw:Generic|1024|2|441|0|0|nomon|swmeter|-|32bit ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa On Fri, Jul 10, 2020 at 12:16 AM wrote: > > On 2020-07-10 01:10, Nathan Dehnel wrote: > >> Do you use pulseaudio ? > > Yes. I have tried using module-jack and also disabling it, but neither > > work. > > > >> /usr/bin/jackd > > I have never found any use for jack2 in the most demanding tasks. the > same advice would be given to you on the jack users group and years ago > in fact it was the advice I got and it proved accurate. > > Install jackd > > I cannot help without jackd > > > > > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Issue starting JACK
On 2020-07-14 03:29, Nathan Dehnel wrote: Ok. Here is the output: Start alsamixer, Then press F6, write down the devices that is listed there and report them back to me. They should be the same as aplay-l In alsamixer select interface that you used in the jackd string. then do F5 Do you see inputs and outputs ? If not the interface was recognized but probably incorrectly. Cycle through with F6 F5 untill one of the options gives you inputs and outputs with F5. then use aplay -l at cli to find the moniker you have to add to the jackd string and try the jackd string again. Remember you need to start the jackd string I gave you from user account not root. I am not sure where you started it from. A succesfull jackd string has output as follows. :~$ /usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:UMC1820 -r441 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2018 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 80 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:UMC1820|hw:UMC1820|1024|2|441|0|0|nomon|swmeter|-|32bit configuring for 441Hz, period = 1024 frames (2322.0 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Issue starting JACK
On 2020-07-14 03:29, Nathan Dehnel wrote: Ok. Here is the output: To add to my last request for info: Try the following. cp .asoundrc .asoundrc.bak(not the hidden file "dot" "." preceding the file. make sure that .asoundrc.bak was created. Reboot. Sorry to ask that but I want to make sure alsa starts from scratch as I cannot remember right now how to restart the alsa sound system with sysctl etc. Start alsamixer, see if tghe default device etc is available and check with F5 if all the inputs and outputs show. Try the jack string again. If this solves your problem, then leave it so. If not, then copy back .asoundrc .bak to .asoundrc in your user account BTW this is clearly not a jack problem . Jack works. It seems to be a driver problem if the above doesnt work. So the problem must be between alsa and the kernel module for the sound card you use. But, try the above first. Sometimes it solves the problem. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Issue starting JACK
On 2020-07-14 03:29, Nathan Dehnel wrote: Ok. Here is the output: CORRECTION: cp .asoundrc .asoundrc.bak(note the hidden file "dot" "." preceding the file.) ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
