Re: [Alsa-user] Issue starting JACK
Yes, it seems like it. On Wed, Jul 15, 2020 at 3:17 AM wrote: > > So, is it working now ? > > > On 2020-07-15 03:05, Nathan Dehnel wrote: > > Jack starts with jackd --sync -P80 -ndefault -dalsa -dhw:Generic_1 > > [HD-Audio Generic] -r441 > > > > Thank you. > > > > > ___ > 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
So, is it working now ? On 2020-07-15 03:05, Nathan Dehnel wrote: Jack starts with jackd --sync -P80 -ndefault -dalsa -dhw:Generic_1 [HD-Audio Generic] -r441 Thank you. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Issue starting JACK
Jack starts with jackd --sync -P80 -ndefault -dalsa -dhw:Generic_1 [HD-Audio Generic] -r441 Thank you. On Tue, Jul 14, 2020 at 3:01 AM wrote: > > 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 ___ 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
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: 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
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-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
Re: [Alsa-user] Issue starting JACK
>Do you use pulseaudio ? Yes. I have tried using module-jack and also disabling it, but neither work. >/usr/bin/jackd This file is not on my system. These are the executables installed by the jack2 package: -r-xr-xr-x 2 root root 48640 Dec 31 1969 alsa_in -r-xr-xr-x 2 root root 48512 Dec 31 1969 alsa_out -r-xr-xr-x 2 root root 16832 Dec 31 1969 jack_alias -r-xr-xr-x 2 root root 17392 Dec 31 1969 jack_bufsize -r-xr-xr-x 2 root root 17664 Dec 31 1969 jack_connect -r-xr-xr-x 2 root root398 Dec 31 1969 jack_control -r-xr-xr-x 2 root root 17992 Dec 31 1969 jack_cpu -r-xr-xr-x 2 root root 16848 Dec 31 1969 jack_cpu_load -r-xr-xr-x 2 root root 137104 Dec 31 1969 jackdbus lrwxrwxrwx 3 root root 12 Dec 31 1969 jack_disconnect -> jack_connect -r-xr-xr-x 2 root root 17456 Dec 31 1969 jack_evmon -r-xr-xr-x 2 root root 16824 Dec 31 1969 jack_freewheel -r-xr-xr-x 2 root root 17928 Dec 31 1969 jack_iodelay -r-xr-xr-x 2 root root 17744 Dec 31 1969 jack_latent_client -r-xr-xr-x 2 root root 17864 Dec 31 1969 jack_load -r-xr-xr-x 2 root root 22160 Dec 31 1969 jack_lsp -r-xr-xr-x 2 root root 18088 Dec 31 1969 jack_metro -r-xr-xr-x 2 root root 22520 Dec 31 1969 jack_midi_dump -r-xr-xr-x 2 root root 33848 Dec 31 1969 jack_midi_latency_test -r-xr-xr-x 2 root root 17368 Dec 31 1969 jack_midiseq -r-xr-xr-x 2 root root 17544 Dec 31 1969 jack_midisine -r-xr-xr-x 2 root root 16632 Dec 31 1969 jack_monitor_client -r-xr-xr-x 2 root root 18528 Dec 31 1969 jack_multiple_metro -r-xr-xr-x 2 root root 17304 Dec 31 1969 jack_net_master -r-xr-xr-x 2 root root 17240 Dec 31 1969 jack_net_slave -r-xr-xr-x 2 root root 47712 Dec 31 1969 jack_netsource -r-xr-xr-x 2 root root 21680 Dec 31 1969 jack_property -r-xr-xr-x 2 root root 23152 Dec 31 1969 jack_rec -r-xr-xr-x 2 root root 16896 Dec 31 1969 jack_samplerate -r-xr-xr-x 2 root root 18328 Dec 31 1969 jack_server_control -r-xr-xr-x 2 root root 18040 Dec 31 1969 jack_session_notify -r-xr-xr-x 2 root root 16960 Dec 31 1969 jack_showtime -r-xr-xr-x 2 root root 34136 Dec 31 1969 jack_simdtests -r-xr-xr-x 2 root root 17376 Dec 31 1969 jack_simple_client -r-xr-xr-x 2 root root 17704 Dec 31 1969 jack_simple_session_client -r-xr-xr-x 2 root root 65752 Dec 31 1969 jack_test -r-xr-xr-x 2 root root 17488 Dec 31 1969 jack_thru -r-xr-xr-x 2 root root 23544 Dec 31 1969 jack_transport -r-xr-xr-x 2 root root 16680 Dec 31 1969 jack_unload -r-xr-xr-x 2 root root 17040 Dec 31 1969 jack_wait -r-xr-xr-x 2 root root 16976 Dec 31 1969 jack_zombie On Thu, Jul 9, 2020 at 10:29 PM wrote: > > Pleazse ignore my previous reply. It contains an error which is > corrected here: > > On 2020-07-09 22:30, Nathan Dehnel wrote: > >> Which of the cards Generic or Generic1 do you want to connect to with > > Jack ? > > I don't care which. > > > Do you use pulseaudio ? > > Regardless; > > Here is something you can do to try and make jack work with alsa > > !) Close qjackctl, as it doesnt work for you. I avoid it like the > plague. It helps me none and just causes problems. > > 2) execute the following in a user terminal > > $] pulseaudio -k > $] killall -KILL jackd > $] /usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:Generic -r441 > > Post the complete terminal output from the last /usr/bin/jackd command > > > > > ___ > 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
Pleazse ignore my previous reply. It contains an error which is corrected here: On 2020-07-09 22:30, Nathan Dehnel wrote: Which of the cards Generic or Generic1 do you want to connect to with Jack ? I don't care which. Do you use pulseaudio ? Regardless; Here is something you can do to try and make jack work with alsa !) Close qjackctl, as it doesnt work for you. I avoid it like the plague. It helps me none and just causes problems. 2) execute the following in a user terminal $] pulseaudio -k $] killall -KILL jackd $] /usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:Generic -r441 Post the complete terminal output from the last /usr/bin/jackd command ___ 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-09 22:30, Nathan Dehnel wrote: Which of the cards Generic or Generic1 do you want to connect to with Jack ? I don't care which. I rely heavily on Jack and run complex routes and cannot live without it, but I must ask why you want to use jack? Do you really need it ? I need to run LV2 plugins. On Thu, Jul 9, 2020 at 8:29 PM wrote: On 2020-07-09 21:03, Nathan Dehnel wrote: > I had this issue with qjackctl and was referred here > https://github.com/rncbc/qjackctl/issues/96 > > bash-5.0$ uname -a > Linux guixlaptop 5.4.50 #1 SMP 1 x86_64 GNU/Linux Which of the cards Generic or Generic1 do you want to connect to with Jack ? I rely heavily on Jack and run complex routes and cannot live without it, but I must ask why you want to use jack? Do you really need it ? Do you use pulseaudio ? Regardless; Here is something you can do to try and make jack work with alsa !) Close qjackctl, as it doesnt work for you. I avoid it like the plague. It helps me none and just causes problems. 2) execute the following in a user terminal $] pulseaudio -k $] killall -KILL jackd $] /usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:Generic -r441 Post the complete terminal output from the last /usr/bin/jackd command /usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:UMC1820 -r441 ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Issue starting JACK
>Which of the cards Generic or Generic1 do you want to connect to with Jack ? I don't care which. >I rely heavily on Jack and run complex routes and cannot live without it, but I must ask why you want to use jack? Do you really need it ? I need to run LV2 plugins. On Thu, Jul 9, 2020 at 8:29 PM wrote: > > On 2020-07-09 21:03, Nathan Dehnel wrote: > > I had this issue with qjackctl and was referred here > > https://github.com/rncbc/qjackctl/issues/96 > > > > bash-5.0$ uname -a > > Linux guixlaptop 5.4.50 #1 SMP 1 x86_64 GNU/Linux > > Which of the cards Generic or Generic1 do you want to connect to with > Jack ? > I rely heavily on Jack and run complex routes and cannot live without > it, but I must ask why you want to use jack? Do you really need it ? > ___ 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-09 21:03, Nathan Dehnel wrote: I had this issue with qjackctl and was referred here https://github.com/rncbc/qjackctl/issues/96 bash-5.0$ uname -a Linux guixlaptop 5.4.50 #1 SMP 1 x86_64 GNU/Linux Which of the cards Generic or Generic1 do you want to connect to with Jack ? I rely heavily on Jack and run complex routes and cannot live without it, but I must ask why you want to use jack? Do you really need it ? ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Issue starting JACK
I had this issue with qjackctl and was referred here https://github.com/rncbc/qjackctl/issues/96 bash-5.0$ uname -a Linux guixlaptop 5.4.50 #1 SMP 1 x86_64 GNU/Linux bash-5.0$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c5) 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) bash-5.0$ lsusb Bus 003 Device 003: ID 0cf3:e500 Qualcomm Atheros Communications USB2.0 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub bash-5.0$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic_1 [HD-Audio Generic], device 0: CX20751/2 Analog [CX20751/2 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 bash-5.0$ aplay -v /home/nathan/Downloads/*.wav ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave aplay: main:830: audio open error: No such file or directory Using Guix System ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
