Re: Sound issues on ThinkPad X220T (Lenovo)
Hi, For the record, I had the exact same problem on a computer running buster that I don't use very often. For sure, it was working fine even with timidity installed a few months ago. Many thanks to Andrei for the 'lsof | grep /dev/snd' command that pointed us in the right direction! Debugging these sound issues that appear spontaneously on a previously-working setup is not easy, especially now that PulseAudio is required everywhere. Regards -- Florent
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > On 4/12/20, riveravaldez wrote: >> On 4/12/20, Andrei POPESCU wrote: >>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo speaker-test -c2' works flawlessly. (The idea to check that came from [1].) >>> >>> Some program might be blocking the sound card, check also the output of >>> 'lsof | grep /dev/snd' (as root). >>> >>> Kind regards, >>> Andrei >> >> Thanks a lot for your answer and help, Andrei. >> I've got these: >> >> $ sudo lsof | grep /dev/snd/ >> timidity 644timidity mem CHR >> 116,213463 /dev/snd/pcmC0D0p >> timidity 644timidity3r CHR >>116,33 0t0 12547 /dev/snd/timer >> timidity 644timidity4u CHR >> 116,2 0t0 13463 /dev/snd/pcmC0D0p >> timidity 644timidity5u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> timidity 644timidity6u CHR >> 116,1 0t0 12548 /dev/snd/seq >> alsamixer 2150thinkpad3u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> >> Maybe a timidity configuration issue? > > Oh, mother-bugger... Problem - practically - solved. > IT is known issue with timidity. I did not know that sound can be played via root account though. We learned a bit more.
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, riveravaldez wrote: > On 4/12/20, Andrei POPESCU wrote: >> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>> >>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>> speaker-test -c2' works flawlessly. (The idea to check that came from >>> [1].) >> >> Some program might be blocking the sound card, check also the output of >> 'lsof | grep /dev/snd' (as root). >> >> Kind regards, >> Andrei > > Thanks a lot for your answer and help, Andrei. > I've got these: > > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Oh, mother-bugger... Problem - practically - solved. I did: $ sudo apt-get purge timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los siguientes paquetes se ELIMINARÁN: timidity* timidity-daemon* 0 actualizados, 0 nuevos se instalarán, 2 para eliminar y 9 no actualizados. Se liberarán 1.655 kB después de esta operación. ¿Desea continuar? [S/n] (Leyendo la base de datos ... 123466 ficheros o directorios instalados actualmente.) Desinstalando timidity-daemon (2.14.0-8) ... Desinstalando timidity (2.14.0-8) ... Procesando disparadores para mime-support (3.64) ... Procesando disparadores para man-db (2.9.1-1) ... Procesando disparadores para desktop-file-utils (0.24-1) ... (Leyendo la base de datos ... 123413 ficheros o directorios instalados actualmente.) Purgando ficheros de configuración de timidity-daemon (2.14.0-8) ... Purgando ficheros de configuración de timidity (2.14.0-8) ... Procesando disparadores para systemd (244.3-1) ... And everything came to work. Pavucontrol shows the devices, streams and configurations. All media-players (audacious, mplayer, firefox, audacity, etc.) work with default audio configuration, and even JACK is working flawlessly. In fact, tested JACK (qjackctl) with qsynt and vmpk and everything worked fine (maybe I don't even need timidity at all?). And then - testing if could reinstall - found the cause of the problem: $ sudo apt-get install timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Paquetes sugeridos: fluid-soundfont-gs pmidi timidity-daemon Se instalarán los siguientes paquetes NUEVOS: timidity 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 9 no actualizados. Se necesita descargar 0 B/627 kB de archivos. Se utilizarán 1.582 kB de espacio de disco adicional después de esta operación. Obteniendo informes de fallo... Finalizado Analizando información Encontrada/Corregida... Finalizado Fallos critical del paquete timidity (→ 2.14.0-8) b1 - #901148 - timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Fusionado con: 902330 904652 918522 Resumen: timidity(1 fallo) ¿Está seguro de que desea instalar/actualizar los paquetes mostrados anteriormente? [Y/n/?/...] n * ** Saliendo con error para detener la instalación. ** * E: El subproceso /usr/bin/apt-listbugs apt devolvió un código de error (10) E: Failure running script /usr/bin/apt-listbugs apt Don't know how that passed without me noticing it... Last messages from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148#147 > After many tests I have found the solution about the > bugs around timidity-daemon and pulseaudio. > > timidity-daemon installs an system-wide daemon. But > pulseaudio is a user-wide "daemon". I guess that explains the 'sudo works, non-sudo non-works'? > With my appended patch the system-wide daemon will be > removed and a xdg/autostart script will be installed. > > After that timidity together with pulseaudio runs > perfectly. > Now I have made new Debian packages for buster and testing > including my patch: That last's from 20 Feb 2020, maybe still not uploaded? Should I mark this as 'SOLVED' in some manner? Thanks a lot for everything. Andrei, you saved me. ^_^ (!)
Re: Sound issues on ThinkPad X220T (Lenovo)
On Du, 12 apr 20, 11:39:52, riveravaldez wrote: > > $ groups > thinkpad cdrom floppy sudo audio dip video plugdev netdev Ok. > $ speaker-test -c2 [Still not sound.] And no error... > $ sudo speaker-test -c2 [Sounds OK.] That would indicate that sound is handled differently for the regular user (e.g. via pulseaudio) vs. the root user. This could be either pulseaudio or an .asoundrc (do you have one in your home directory?). Try this as user: pasuspender -- speaker-test -c2 > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Try stopping / disabling it and see if that helps. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, deloptes wrote: > riveravaldez wrote: > >> But this not, even as sudo (and the error is similar to JACK one): >> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav >> aplay: main:830: audio open error: Device or resource bussy > > aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav Problem persists, no sound: $ aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav aplay: main:830: audio open error: Device or resource busy > read this > https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture I'll check it again. > > you should know what you are doing Yes, that's the idea. Any help? Thanks!
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, Andrei POPESCU wrote: > On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) > > Any error message? Is your user a member of group 'audio'? > > Some program might be blocking the sound card, check also the output of > 'lsof | grep /dev/snd' (as root). > > Kind regards, > Andrei Thanks a lot for your answer and help, Andrei. I've got these: $ groups thinkpad cdrom floppy sudo audio dip video plugdev netdev $ speaker-test -c2 [Still not sound.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 96 to 1048576 Period size range from 32 to 349526 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Time per period = 12,314270 0 - Front Left 1 - Front Right ^CTime per period = 12,317682 $ sudo speaker-test -c2 [Sounds OK.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5,644667 0 - Front Left ^CWrite error: -4,Llamada al sistema interrumpida xrun_recovery failed: -4,Llamada al sistema interrumpida Transfer failed: Llamada al sistema interrumpida [System is in Spanish, last lines mean, 'Interrupted system-call'.] $ sudo lsof | grep /dev/snd/ timidity 644timidity mem CHR 116,213463 /dev/snd/pcmC0D0p timidity 644timidity3r CHR 116,33 0t0 12547 /dev/snd/timer timidity 644timidity4u CHR 116,2 0t0 13463 /dev/snd/pcmC0D0p timidity 644timidity5u CHR 116,9 0t0 13479 /dev/snd/controlC0 timidity 644timidity6u CHR 116,1 0t0 12548 /dev/snd/seq alsamixer 2150thinkpad3u CHR 116,9 0t0 13479 /dev/snd/controlC0 Maybe a timidity configuration issue?
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > But this not, even as sudo (and the error is similar to JACK one): > $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav > aplay: main:830: audio open error: Device or resource bussy aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav read this https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture you should know what you are doing
Re: Sound issues on ThinkPad X220T (Lenovo)
On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) Any error message? Is your user a member of group 'audio'? Some program might be blocking the sound card, check also the output of 'lsof | grep /dev/snd' (as root). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > On 4/11/20, riveravaldez wrote: >> Hi, >> >> I would like to know what's the proper way to solve this. I'm on an >> updated debian-testing installation (with pulseaudio installed and >> working, but the problem seems to be previous, i.e., in ALSA, because >> pavucontrol doesn't show the soundcard in its correspondent tab). >> >> I can get audio from audacity and audacious as long as I choose >> manually the proper soundcard in its options, but not from other >> programs (e.g., firefox, mplayer, etc.), which I suppose use the >> default soundcard. >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) >> >> I already tested (following [2]): >> >> $ sudo alsactl init >> Found hardware: "HDA-Intel" "Conexant CX20590" >> "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" >> "0x17aa" "0x21db" >> Hardware is initialized using a generic method >> >> But nothing changed after reboot. (Though, the CX20590 is the working >> choice for audacious/audacity.) >> >> I have this info: >> >> $ cat /proc/asound/cards >> 0 [PCH]: HDA-Intel - HDA Intel PCH >> HDA Intel PCH at 0xf252 irq 35 >> >> $ lspci -v >> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset >> Family High Definition Audio Controller (rev 04) >> Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition >> Audio Controller >> Flags: bus master, fast devsel, latency 0, IRQ 35 >> Memory at f252 (64-bit, non-prefetchable) [size=16K] >> Capabilities: >> Kernel driver in use: snd_hda_intel >> Kernel modules: snd_hda_intel >> >> Any other info I could provide? >> What should I do? >> >> BTW, JACK also fails to work, with these messages: >> >> 20:59:14.349 Reiniciar estadísticas. >> 20:59:14.356 Cambios en las conexiones ALSA. >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.365 JACK está iniciándose... >> 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D >> -Chw:PCH,0 -Phw:PCH,0 >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.382 JACK se inició con PID=3144. >> no message buffer overruns >> no message buffer overruns >> no message buffer overruns >> jackdmp 1.9.12 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2016 Grame. >> Copyright 2016-2017 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 10 >> self-connect-mode is "Don't restrict self connect requests" >> Jack: JackPosixThread::StartImp : create non RT thread >> Jack: JackPosixThread::ThreadHandler : start >> Jack: capture device hw:PCH,0 >> Jack: playback device hw:PCH,0 >> Jack: apparent rate = 48000 >> Jack: frames per period = 512 >> Jack: JackDriver::Open capture_driver_name = hw:PCH,0 >> Jack: JackDriver::Open playback_driver_name = hw:PCH,0 >> Jack: Check protocol client = 8 server = 8 >> Jack: JackEngine::ClientInternalOpen: name = system >> Jack: JackEngine::AllocateRefNum ref = 0 >> Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = >> 0 >> Jack: JackEngine::NotifyAddClient: name = system >> Jack: JackGraphManager::SetBufferSize size = 512 >> Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackDriver::SetupDriverSync driver sem in flush mode >> audio_reservation_init >> Acquire audio card Audio0 >> creating alsa driver ... >> hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit >> ATTENTION: The playback device "hw:PCH,0" is already in use. Please >> stop the application using it and run JACK again >> Jack: JackDriver::Close >> Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackEngine::ClientInternalClose ref = 0 >> Jack: JackEngine::ClientCloseAux ref = 0 >> Jack: JackGraphManager::RemoveAllPorts ref = 0 >> Released audio card Audio0 >> audio_reservation_finish >> Jack: ~JackDriver >> Cannot initialize driver >> Jack: no message buffer overruns >> Jack: JackPosixThread::Stop >>
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > Hi, > > I would like to know what's the proper way to solve this. I'm on an > updated debian-testing installation (with pulseaudio installed and > working, but the problem seems to be previous, i.e., in ALSA, because > pavucontrol doesn't show the soundcard in its correspondent tab). > > I can get audio from audacity and audacious as long as I choose > manually the proper soundcard in its options, but not from other > programs (e.g., firefox, mplayer, etc.), which I suppose use the > default soundcard. > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) > > I already tested (following [2]): > > $ sudo alsactl init > Found hardware: "HDA-Intel" "Conexant CX20590" > "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" > "0x17aa" "0x21db" > Hardware is initialized using a generic method > > But nothing changed after reboot. (Though, the CX20590 is the working > choice for audacious/audacity.) > > I have this info: > > $ cat /proc/asound/cards > 0 [PCH]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf252 irq 35 > > $ lspci -v > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > Family High Definition Audio Controller (rev 04) > Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition > Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 35 > Memory at f252 (64-bit, non-prefetchable) [size=16K] > Capabilities: > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > Any other info I could provide? > What should I do? > > BTW, JACK also fails to work, with these messages: > > 20:59:14.349 Reiniciar estadísticas. > 20:59:14.356 Cambios en las conexiones ALSA. > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.365 JACK está iniciándose... > 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D > -Chw:PCH,0 -Phw:PCH,0 > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.382 JACK se inició con PID=3144. > no message buffer overruns > no message buffer overruns > no message buffer overruns > jackdmp 1.9.12 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2016 Grame. > Copyright 2016-2017 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 10 > self-connect-mode is "Don't restrict self connect requests" > Jack: JackPosixThread::StartImp : create non RT thread > Jack: JackPosixThread::ThreadHandler : start > Jack: capture device hw:PCH,0 > Jack: playback device hw:PCH,0 > Jack: apparent rate = 48000 > Jack: frames per period = 512 > Jack: JackDriver::Open capture_driver_name = hw:PCH,0 > Jack: JackDriver::Open playback_driver_name = hw:PCH,0 > Jack: Check protocol client = 8 server = 8 > Jack: JackEngine::ClientInternalOpen: name = system > Jack: JackEngine::AllocateRefNum ref = 0 > Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 > Jack: JackEngine::NotifyAddClient: name = system > Jack: JackGraphManager::SetBufferSize size = 512 > Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackDriver::SetupDriverSync driver sem in flush mode > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... > hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit > ATTENTION: The playback device "hw:PCH,0" is already in use. Please > stop the application using it and run JACK again > Jack: JackDriver::Close > Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackEngine::ClientInternalClose ref = 0 > Jack: JackEngine::ClientCloseAux ref = 0 > Jack: JackGraphManager::RemoveAllPorts ref = 0 > Released audio card Audio0 > audio_reservation_finish > Jack: ~JackDriver > Cannot initialize driver > Jack: no message buffer overruns > Jack: JackPosixThread::Stop > Jack: JackPosixThread::ThreadHandler : exit > JackServer::Open failed with -1 > Jack: Succeeded in unlocking 82280346 byte memory area > Jack:
Re: sound issues
2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl regards -r what you want meaning a complicated setup that allows WOW and Skype to co-exist - but requires you to fiddle with every upgrade, and more fiddling for every application that requires sound. With the greatest respect - though you've invested a great deal in the belief that pulseaudio is bad, it's not a belief shared by the upstream developers of most applications (or more importantly, Debian). PA doesn't stop you using JACK - it's one of many sound systems that work just fine *under* PA (I run Ardour). Contrary to some commentary - PA is just a foreman, not a wheelbarrow. There's a number of things that PA can do[*1], that [insert pet sound system here] can't do. The reverse is not true - because PA allows you to run [insert pet sound system here]. Kind regards Hi, FOA, let's say I am not interested in starting a flame war nor arguing with you or anybody else about jack vs pulse. - jack and PA are completely different ( http://jackaudio.org/pulseaudio_and_jack) so there's no use in listing what PA can and can not do - jack is intended for audio pro but it can address low/high level tasks without fiddling with upgrades as you claim. - you run ardour but how many apps are you coupling with it? using jamin? hydrogen? guitarix? synth? well all those apps can be controlled and synced by jack with a high level of complexity in the connection graph. Can you do it with PA (answer to yourserlf)? - belive it or not, pulseaudio does not address pro audio needs - debian devs are right in using PA, they must aim at the average user last: I have SUGGESTED hime to give it a try (killall pulseaudio != remove pulseaudio) [insert your favourite pet system sound here] regards :-) -r
Re: sound issues
On 05/03/12 19:18, Raffaele Morelli wrote: 2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com mailto:scott.ferguson.debian.u...@gmail.com Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl snipped Hi, FOA, let's say I am not interested in starting a flame war Good. FWIW - I think JACK is a fine sound system, also ALSA, ESD, SDL and phonon. nor arguing with you or anybody else about jack vs pulse. Good also. I never said it was JACK vs. PA. I don't know where you got that from. Read again - you can have both if you choose. By default WOW and Skype both use ALSA. For the OP they still do - except that Kelly has helped him get PA working properly to manage them. * �jack and PA are completely different I never said they weren't. I'm not sure where you've got that idea from either. Read again (http://jackaudio.org/pulseaudio_and_jack) so there's no use in listing what PA can and can not do The two things have nothing to do with each other. I listed Pulse audio capabilities as a reason to, as the OP has since done, fix it - instead of leaving it broken and using JACK in it's place. I never said *don't* use JACK, only that you can have both. * �jack is intended for audio pro but it can address low/high level tasks without fiddling with upgrades as you claim. Debian now uses pulseaudio - using JACK in it's place will create difficulties with upgrades. * you run ardour but how many apps are you coupling with it? using jamin? hydrogen? guitarix? synth? Relevance to fixing the Pulse audio configuration? If you're doing a survey - the answer is as many as I need, and the system, and JACK, can handle. well all those apps can be controlled and synced by jack with a high level of complexity in the connection graph. Can you do it with PA I've never tried - why would I? I do it with JACK. PA doesn't interfere. * belive it or not, pulseaudio does not address pro audio needs Nice strawman I've never said it did. Read again. Did the OP say anything about pro audio needs? I must of missed that post... :-) You do realise this is not 'your' usual, linuxaudio RT list, right? :-) * debian devs are right in using PA, they must aim at the average user I don't know that they must do anything. Certainly it seems they're aiming at the widest range of uses - which would include more than just desktop users. last: I have SUGGESTED hime to give it a try (killall pulseaudio != remove pulseaudio) That was understood the first time. Your point being? What would be the purpose of disabling an unconfigured and perfectly good sound system? IMHO it's better to configure what's in place - which has been done. You don't need audio plumbing to record Skype either - there's a package for that. He could also have just used ALSA... but the simplest solution to how do I enable sound for WOW and Skype on his system was simply to configure pulseaudio. Pulseaudio in Debian is not great for everyone now. Rather than not make use of all the work developers upstream, and in Debian, have put into it - it would seem simpler to just fix it. (don't throw the baby out with the bathwater) Which is what Kelly did. The audio is great now. regards :-) -r Kind regards -- Oh sorry, I was taking life seriously. — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f549aa7.2010...@gmail.com
Re: sound issues
2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com On 05/03/12 19:18, Raffaele Morelli wrote: 2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com mailto:scott.ferguson.debian.u...@gmail.com Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl snipped Hi, FOA, let's say I am not interested in starting a flame war Good. FWIW - I think JACK is a fine sound system, also ALSA, ESD, SDL and phonon. nor arguing with you or anybody else about jack vs pulse. Good also. I never said it was JACK vs. PA. I don't know where you got that from. Read again - you can have both if you choose. it's a statement of mine, no need to read agian BTW you can have both at your own risk By default WOW and Skype both use ALSA. For the OP they still do - except that Kelly has helped him get PA working properly to manage them. * �jack and PA are completely different I never said they weren't. I'm not sure where you've got that idea from either. Read again again, it's a statement of mine, you never said that (http://jackaudio.org/pulseaudio_and_jack) so there's no use in listing what PA can and can not do The two things have nothing to do with each other. I listed Pulse audio capabilities as a reason to, as the OP has since done, fix it - instead of leaving it broken and using JACK in it's place. I never said *don't* use JACK, only that you can have both. Combining PulseAudio and JACK on the same machine can be problematic. There are several options, some of which leave PulseAudio and JACK as entirely separate systems with no audio flow between them. Others connect them so that audio from one of them can be heard via the other. * �jack is intended for audio pro but it can address low/high level tasks without fiddling with upgrades as you claim. Debian now uses pulseaudio - using JACK in it's place will create difficulties with upgrades. you should explain or send a bug report to debian devs then * you run ardour but how many apps are you coupling with it? using jamin? hydrogen? guitarix? synth? Relevance to fixing the Pulse audio configuration? you claimed jack works just fine under PA because you run ardour so I wonder why jack devs wrote Option 1 in http://www.jackaudio.org/pulseaudio_and_jack If you're doing a survey - the answer is as many as I need, and the system, and JACK, can handle. well all those apps can be controlled and synced by jack with a high level of complexity in the connection graph. Can you do it with PA I've never tried - why would I? I do it with JACK. PA doesn't interfere. * belive it or not, pulseaudio does not address pro audio needs Nice strawman I've never said it did. Read again. Did the OP say anything about pro audio needs? I must of missed that post... :-) he wrote that, reag again http://lists.debian.org/debian-user/2012/03/msg00161.html You do realise this is not 'your' usual, linuxaudio RT list, right? :-) * debian devs are right in using PA, they must aim at the average user I don't know that they must do anything. Certainly it seems they're aiming at the widest range of uses - which would include more than just desktop users. last: I have SUGGESTED hime to give it a try (killall pulseaudio != remove pulseaudio) That was understood the first time. Your point being? What would be the purpose of disabling an unconfigured and perfectly good sound system? I think maybe your just too sensitive and in love wiht PA :-) to admit mine was a suggestion, I think he posted on this list because his sound sistem isn't configured and perfectly good 100%, do you? over and out -r -- *L'unica speranza di catarsi, ammesso che ne esista una, resta affidata all'istinto di ribellione, alla rivolta non isterilita in progetti, alla protesta violenta e viscerale.*
Re: sound issues
On Mon, Mar 5, 2012 at 02:51, Scott Ferguson scott.ferguson.debian.u...@gmail.com wrote: On 05/03/12 19:18, Raffaele Morelli wrote: 2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com mailto:scott.ferguson.debian.u...@gmail.com Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl snipped Hi, FOA, let's say I am not interested in starting a flame war Good. FWIW - I think JACK is a fine sound system, also ALSA, ESD, SDL and phonon. Personally, I would argue about ESD being fine. Though it is moot really, since ESD is dead. And of course SDL and Phonon (and OpenAL and libao, etc) are in a very different space from PA/Jack, being sound libraries rather than sound servers. ALSA is different again, being the fundamental interface to the sound hardware (sharing that space with OSS). http://www.clowersnet.net/~krc/computers/realistic_linux_audio_v2.png (needs some updating and improving, e.g. libsydney never came to be) Which maybe you know all about, but I know plenty of people find a diagram like that useful. Heck, I did, that is why I made it. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=9fhot+4pmmqb32wqz+ylv4nrzjcxwrborjcrr044y...@mail.gmail.com
Re: sound issues
On 06/03/12 03:01, Kelly Clowers wrote: On Mon, Mar 5, 2012 at 02:51, Scott Ferguson scott.ferguson.debian.u...@gmail.com wrote: On 05/03/12 19:18, Raffaele Morelli wrote: 2012/3/5 Scott Ferguson scott.ferguson.debian.u...@gmail.com mailto:scott.ferguson.debian.u...@gmail.com Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl snipped Hi, FOA, let's say I am not interested in starting a flame war Good. FWIW - I think JACK is a fine sound system, also ALSA, ESD, SDL and phonon. Personally, I would argue about ESD being fine. And I wouldn't disagree - it had a few things wrong with it (DoSing amongst others) - and it was limited. They all, and OSS, had/have their place - even if they're not my choice (it's choices that's important IMHO) snipped And of course SDL and Phonon (and OpenAL and libao, etc) are in a very different space from PA/Jack, being sound libraries rather than sound servers. Which is why I wrote system not server. ALSA is different again, being the fundamental interface to the sound hardware (sharing that space with OSS). Some prefer OSS, I prefer ALSA for it's better support of hardware and it's willingness to share. Despite some popular beliefs it's also capable of very low latency (I think you mentioned dmix). http://www.clowersnet.net/~krc/computers/realistic_linux_audio_v2.png (needs some updating and improving, e.g. libsydney never came to be) Which maybe you know all about, but I know plenty of people find a diagram like that useful. Heck, I did, that is why I made it. As do I, thanks. I've bookmarked it for the next time I need to come up with a better explanation of pulseadio than it's just the site foreman, not a wheelbarrow. I'm a KDE user. Tried the xine and gstreamer phonon backends, we settled on the VLC backend which you don't list (you did say it's an old diagram). On Squeeze we've found it seems to have less problems with various applications - particularly streaming between other devices. Cheers, Kelly Clowers Kind regards -- Oh sorry, I was taking life seriously. — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f5546a0.50...@gmail.com
Re: sound issues
On Mon, Mar 5, 2012 at 15:05, Scott Ferguson scott.ferguson.debian.u...@gmail.com wrote: On 06/03/12 03:01, Kelly Clowers wrote: http://www.clowersnet.net/~krc/computers/realistic_linux_audio_v2.png (needs some updating and improving, e.g. libsydney never came to be) Which maybe you know all about, but I know plenty of people find a diagram like that useful. Heck, I did, that is why I made it. As do I, thanks. I've bookmarked it for the next time I need to come up with a better explanation of pulseadio than it's just the site foreman, not a wheelbarrow. I'm a KDE user. Tried the xine and gstreamer phonon backends, we settled on the VLC backend which you don't list (you did say it's an old diagram). On Squeeze we've found it seems to have less problems with various applications - particularly streaming between other devices. VLC is on there, actually. But yeah, the Phonon VLC backend was a little later, but is now the preferred one. The gstreamer backend is still improving, though, and has worked fine for Amarok playback. I hope after GST 1.0 comes out (fingers crossed for this year), it will eventually become the default backend for Phonon. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM�conccqvex1hwanj8fs0yx8yqxdeayn9bbyamyf0...@mail.gmail.com
Re: sound issues
On 04/03/12 04:56, Scott Ferguson wrote: On 04/03/12 14:18, Darren Crotchett wrote: snipped Thank you so much for sticking with me. I appreciate everyone's comments. I hope that someone with find this thread useful in the future. Not only in the future :) I've been following this thread, without contributing, I'm afraid, but it's sorted out my sound problems. Thanks all! -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f536eda.80...@vanderhoff.org
Re: sound issues
2012/3/4 Darren Crotchett deb...@crotchett.com
I am going to clearly remark as much as possible for the benefit of anyone
who may find this page later. See my inline replies/comments.
On Sat, Mar 3, 2012 at 12:24 PM, Kelly Clowers kelly.clow...@gmail.comwrote:
On Sat, Mar 3, 2012 at 05:53, Darren Crotchett deb...@crotchett.com
wrote:
Can you elaborate on what you mean by it just needs to be setup
correctly?
I'm going to be working on this issue today. Before I install the
applications that Raffaele recommended, I want to give Pulseaudio one
more
chance because I would rather figure out the problem than to circumvent
it.
OTOH, I don't want to fight a losing battle either.
So, I originally setup mine based on the PA wiki's Perfect Setup.
It is rather
extensive and a lot of the stuff in there is from a time when there
was less support
for PA.
Here are the essentials:
Edit /etc/asound.conf (for all users) or ~/.asoundrc (per-user)
I have only these two entries in mine:
Neither of these files existed. I didn't care about a per-user setting,
so I just created an /etc/asound.conf and added the recommended lines below.
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
Make sure you are in the groups audio, pulse-access and pulse-rt
I used vigr and vigr -s to edit the groups. My user was already in
audio. I added it to pulse-access group. And, I did not have a
pulse-rt group. I did not create the group.
Make sure that Pulse is being run automatically at startup (it should be,
I just remember when it was not, and I had to set it up myself).
It was already starting automatically with /etc/init.d/pulseaudio
---
The setting of the alsa default to pulse should make most things work,
but personally I set a number of things to PA explicitly. At least some
of these
used to be required (they did not automatically use pulse and avoided the
alsa default or similar). Nowadays that may not be the case, I don't know.
Also they may have a PA driver that is different from the alsa driver, and
may work better than redirected alsa.
in ~/.mplayer/config: ao = pulse
in ~/.xine/config: audio.driver:pulseaudio
in ~/.vlcrc or ~/.config/vlc/vlcrc: aout=pulse
in /etc/libao.conf: default_driver=pulse
I did not have the mplayer or xine config files above files. So, I
created them and add the recommended lines. I had the ~/.config/vlc/vlcrc.
The aout directive was present, but was commented out and had no value.
So, I set it. I changed the /etc/libao.conf from default_driver=alsa to
default_driver=pulse.
for gstreamer:
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink
pulsesink
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc
pulsesrc
gconftool-2 -t string --set
/system/gstreamer/0.10/default/musicaudiosink pulsesink
gconftool-2 -t string --set
/system/gstreamer/0.10/default/chataudiosink pulsesink
I ran the gconftool-2 commands.
KDE's Phonon uses vlc, mplayer or gstreamer, so the above should cover
that as well
SDL (used for some games) can be set to explicitly use PA with:
export SDL_AUDIODRIVER=pulse
(needs to be done in a startup script like ~/.bashrc to be permanent)
I added the export to the .bashrc. I also executed it at the command line
so I didn't have to log out and back in.
I restarted pulseaudio with: /etc/init.d/pulseaudio restart
This did not seem to work. So, I rebooted. This seems to work. I was
able to play a movie with sound on VLC, Minecraft and Skype all at once
without breaking anything.
As far as I remember that is about it. As I said, setting those explicitly
may not be needed anymore, I just don't know.
Cheers,
Kelly Clowers
Thank you so much for sticking with me. I appreciate everyone's comments.
I hope that someone with find this thread useful in the future.
Just to clarify with Kelly about what complicated stands for :-)
IMHO you are going to get what you want in two steps:
killall pulseaudio aptitude install jackd qjackctl
regards
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale.*
Re: sound issues
On Sun, Mar 4, 2012 at 10:24 AM, Raffaele Morelli
raffaele.more...@gmail.com wrote:
2012/3/4 Darren Crotchett deb...@crotchett.com
I am going to clearly remark as much as possible for the benefit of
anyone who may find this page later. See my inline replies/comments.
On Sat, Mar 3, 2012 at 12:24 PM, Kelly Clowers
kelly.clow...@gmail.comwrote:
On Sat, Mar 3, 2012 at 05:53, Darren Crotchett deb...@crotchett.com
wrote:
Can you elaborate on what you mean by it just needs to be setup
correctly?
I'm going to be working on this issue today. Before I install the
applications that Raffaele recommended, I want to give Pulseaudio one
more
chance because I would rather figure out the problem than to
circumvent it.
OTOH, I don't want to fight a losing battle either.
So, I originally setup mine based on the PA wiki's Perfect Setup.
It is rather
extensive and a lot of the stuff in there is from a time when there
was less support
for PA.
Here are the essentials:
Edit /etc/asound.conf (for all users) or ~/.asoundrc (per-user)
I have only these two entries in mine:
Neither of these files existed. I didn't care about a per-user setting,
so I just created an /etc/asound.conf and added the recommended lines below.
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
Make sure you are in the groups audio, pulse-access and pulse-rt
I used vigr and vigr -s to edit the groups. My user was already in
audio. I added it to pulse-access group. And, I did not have a
pulse-rt group. I did not create the group.
Make sure that Pulse is being run automatically at startup (it should be,
I just remember when it was not, and I had to set it up myself).
It was already starting automatically with /etc/init.d/pulseaudio
---
The setting of the alsa default to pulse should make most things work,
but personally I set a number of things to PA explicitly. At least some
of these
used to be required (they did not automatically use pulse and avoided the
alsa default or similar). Nowadays that may not be the case, I don't
know.
Also they may have a PA driver that is different from the alsa driver,
and
may work better than redirected alsa.
in ~/.mplayer/config: ao = pulse
in ~/.xine/config: audio.driver:pulseaudio
in ~/.vlcrc or ~/.config/vlc/vlcrc: aout=pulse
in /etc/libao.conf: default_driver=pulse
I did not have the mplayer or xine config files above files. So, I
created them and add the recommended lines. I had the ~/.config/vlc/vlcrc.
The aout directive was present, but was commented out and had no value.
So, I set it. I changed the /etc/libao.conf from default_driver=alsa to
default_driver=pulse.
for gstreamer:
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink
pulsesink
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc
pulsesrc
gconftool-2 -t string --set
/system/gstreamer/0.10/default/musicaudiosink pulsesink
gconftool-2 -t string --set
/system/gstreamer/0.10/default/chataudiosink pulsesink
I ran the gconftool-2 commands.
KDE's Phonon uses vlc, mplayer or gstreamer, so the above should cover
that as well
SDL (used for some games) can be set to explicitly use PA with:
export SDL_AUDIODRIVER=pulse
(needs to be done in a startup script like ~/.bashrc to be permanent)
I added the export to the .bashrc. I also executed it at the command
line so I didn't have to log out and back in.
I restarted pulseaudio with: /etc/init.d/pulseaudio restart
This did not seem to work. So, I rebooted. This seems to work. I was
able to play a movie with sound on VLC, Minecraft and Skype all at once
without breaking anything.
As far as I remember that is about it. As I said, setting those
explicitly
may not be needed anymore, I just don't know.
Cheers,
Kelly Clowers
Thank you so much for sticking with me. I appreciate everyone's
comments. I hope that someone with find this thread useful in the future.
Just to clarify with Kelly about what complicated stands for :-)
IMHO you are going to get what you want in two steps:
killall pulseaudio aptitude install jackd qjackctl
regards
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale.*
Thanks for posting. The were 2 reasons that I went with PA, neither of
which were because I thought installing jackd might be complicated. The
first reason was because PA was installed by default. Unless I have a
particularly good reason (like nVidia drivers) I try to stick to out of
the box as much as possible because it seems to help prevent future issues
related to updates and upgrades. The other reason was because I was hoping
to finally figure out what I don't understand about sound on Linux. As I
mentioned in my first post, sound is always an issue for me. And, somehow,
I always
Re: sound issues
On Sun, Mar 4, 2012 at 08:24, Raffaele Morelli raffaele.more...@gmail.com wrote: Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge is definitely more complicated than PA. The rest is about the same, you have to make sure things are installed, and set apps to use jack, just as you do with PA. if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=-aNdmvqJOc2iG=edArZd=opk3y56d4h8etzqqi13h...@mail.gmail.com
Re: sound issues
On 05/03/12 03:24, Raffaele Morelli wrote: 2012/3/4 Darren Crotchett deb...@crotchett.com mailto:deb...@crotchett.com snipped I restarted pulseaudio with: /etc/init.d/pulseaudio restart This did not seem to work. So, I rebooted. This seems to work. I was able to play a movie with sound on VLC, Minecraft and Skype all at once without breaking anything. As far as I remember that is about it. As I said, setting those explicitly may not be needed anymore, I just don't know. Cheers, Kelly Clowers Thank you so much for sticking with me. I appreciate everyone's comments. I hope that someone with find this thread useful in the future. Just to clarify with Kelly about what complicated stands for :-) IMHO you are going to get what you want in two steps: killall pulseaudio aptitude install jackd qjackctl regards -r what you want meaning a complicated setup that allows WOW and Skype to co-exist - but requires you to fiddle with every upgrade, and more fiddling for every application that requires sound. With the greatest respect - though you've invested a great deal in the belief that pulseaudio is bad, it's not a belief shared by the upstream developers of most applications (or more importantly, Debian). PA doesn't stop you using JACK - it's one of many sound systems that work just fine *under* PA (I run Ardour). Contrary to some commentary - PA is just a foreman, not a wheelbarrow. There's a number of things that PA can do[*1], that [insert pet sound system here] can't do. The reverse is not true - because PA allows you to run [insert pet sound system here]. [*1] Per-application volume controls. An extensible plugin architecture with support for loadable modules. Compatibility with many popular audio applications. Support for multiple audio sources and sinks. Low-latency operation and support for latency measurement. A zero-copy memory architecture for processor resource efficiency. Ability to discover other computers using PulseAudio on the local network and play sound through their speakers directly. Ability to change which output device an application plays sound through while the application is playing sound (without the application needing to support this, and indeed without even being aware that this happened). A command-line interface with scripting capabilities. A sound daemon with command line reconfiguration capabilities. Built-in sample conversion and resampling capabilities. The ability to combine multiple sound cards into one. The ability to synchronize multiple playback streams (including across networks, vms, through X etc). Bluetooth audio devices with dynamic detection. The ability to enable system wide equalization. Support for most Operating Systems (and most many portable devices, Nokia, Palm, and others). Kind regards -- I tried being conservative for a change... but all I found was more of the same -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f53f4e2.6090...@gmail.com
Re: sound issues
On Fri, Mar 2, 2012 at 10:11 AM, Kelly Clowers kelly.clow...@gmail.comwrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). It has been a while since I setup PA, and I don't have my Debian box here, so I can't say much until about 5:00 Pacific standard time. When you say Pandora, you mean the internet radio, right? In that case the app is the browser (and not Flash anymore, thankfully. Although even that is better than it used to be). Make sure the PA plugins for various programs are installed: vlc-plugin-pulse gstreamer0.10-pulseaudio Much more when I get home. Cheers, Kelly Clowers Can you elaborate on what you mean by it just needs to be setup correctly? I'm going to be working on this issue today. Before I install the applications that Raffaele recommended, I want to give Pulseaudio one more chance because I would rather figure out the problem than to circumvent it. OTOH, I don't want to fight a losing battle either.
Re: sound issues
On Sat, Mar 3, 2012 at 05:53, Darren Crotchett deb...@crotchett.com wrote:
Can you elaborate on what you mean by it just needs to be setup correctly?
I'm going to be working on this issue today. Before I install the
applications that Raffaele recommended, I want to give Pulseaudio one more
chance because I would rather figure out the problem than to circumvent it.
OTOH, I don't want to fight a losing battle either.
So, I originally setup mine based on the PA wiki's Perfect Setup.
It is rather
extensive and a lot of the stuff in there is from a time when there
was less support
for PA.
Here are the essentials:
Edit /etc/asound.conf (for all users) or ~/.asoundrc (per-user)
I have only these two entries in mine:
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
Make sure you are in the groups audio, pulse-access and pulse-rt
Make sure that Pulse is being run automatically at startup (it should be,
I just remember when it was not, and I had to set it up myself).
---
The setting of the alsa default to pulse should make most things work,
but personally I set a number of things to PA explicitly. At least some of these
used to be required (they did not automatically use pulse and avoided the
alsa default or similar). Nowadays that may not be the case, I don't know.
Also they may have a PA driver that is different from the alsa driver, and
may work better than redirected alsa.
in ~/.mplayer/config: ao = pulse
in ~/.xine/config: audio.driver:pulseaudio
in ~/.vlcrc or ~/.config/vlc/vlcrc: aout=pulse
in /etc/libao.conf: default_driver=pulse
for gstreamer:
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink pulsesink
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc pulsesrc
gconftool-2 -t string --set
/system/gstreamer/0.10/default/musicaudiosink pulsesink
gconftool-2 -t string --set
/system/gstreamer/0.10/default/chataudiosink pulsesink
KDE's Phonon uses vlc, mplayer or gstreamer, so the above should cover
that as well
SDL (used for some games) can be set to explicitly use PA with:
export SDL_AUDIODRIVER=pulse
(needs to be done in a startup script like ~/.bashrc to be permanent)
As far as I remember that is about it. As I said, setting those explicitly
may not be needed anymore, I just don't know.
Cheers,
Kelly Clowers
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAFoWM=_dckebymf-nch4wj115op+misioznq2gq5_lxlfxk...@mail.gmail.com
Re: sound issues
I am going to clearly remark as much as possible for the benefit of anyone
who may find this page later. See my inline replies/comments.
On Sat, Mar 3, 2012 at 12:24 PM, Kelly Clowers kelly.clow...@gmail.comwrote:
On Sat, Mar 3, 2012 at 05:53, Darren Crotchett deb...@crotchett.com
wrote:
Can you elaborate on what you mean by it just needs to be setup
correctly?
I'm going to be working on this issue today. Before I install the
applications that Raffaele recommended, I want to give Pulseaudio one
more
chance because I would rather figure out the problem than to circumvent
it.
OTOH, I don't want to fight a losing battle either.
So, I originally setup mine based on the PA wiki's Perfect Setup.
It is rather
extensive and a lot of the stuff in there is from a time when there
was less support
for PA.
Here are the essentials:
Edit /etc/asound.conf (for all users) or ~/.asoundrc (per-user)
I have only these two entries in mine:
Neither of these files existed. I didn't care about a per-user setting, so
I just created an /etc/asound.conf and added the recommended lines below.
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
Make sure you are in the groups audio, pulse-access and pulse-rt
I used vigr and vigr -s to edit the groups. My user was already in
audio. I added it to pulse-access group. And, I did not have a
pulse-rt group. I did not create the group.
Make sure that Pulse is being run automatically at startup (it should be,
I just remember when it was not, and I had to set it up myself).
It was already starting automatically with /etc/init.d/pulseaudio
---
The setting of the alsa default to pulse should make most things work,
but personally I set a number of things to PA explicitly. At least some of
these
used to be required (they did not automatically use pulse and avoided the
alsa default or similar). Nowadays that may not be the case, I don't know.
Also they may have a PA driver that is different from the alsa driver, and
may work better than redirected alsa.
in ~/.mplayer/config: ao = pulse
in ~/.xine/config: audio.driver:pulseaudio
in ~/.vlcrc or ~/.config/vlc/vlcrc: aout=pulse
in /etc/libao.conf: default_driver=pulse
I did not have the mplayer or xine config files above files. So, I created
them and add the recommended lines. I had the ~/.config/vlc/vlcrc. The
aout directive was present, but was commented out and had no value. So, I
set it. I changed the /etc/libao.conf from default_driver=alsa to
default_driver=pulse.
for gstreamer:
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink
pulsesink
gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc
pulsesrc
gconftool-2 -t string --set
/system/gstreamer/0.10/default/musicaudiosink pulsesink
gconftool-2 -t string --set
/system/gstreamer/0.10/default/chataudiosink pulsesink
I ran the gconftool-2 commands.
KDE's Phonon uses vlc, mplayer or gstreamer, so the above should cover
that as well
SDL (used for some games) can be set to explicitly use PA with:
export SDL_AUDIODRIVER=pulse
(needs to be done in a startup script like ~/.bashrc to be permanent)
I added the export to the .bashrc. I also executed it at the command line
so I didn't have to log out and back in.
I restarted pulseaudio with: /etc/init.d/pulseaudio restart
This did not seem to work. So, I rebooted. This seems to work. I was
able to play a movie with sound on VLC, Minecraft and Skype all at once
without breaking anything.
As far as I remember that is about it. As I said, setting those explicitly
may not be needed anymore, I just don't know.
Cheers,
Kelly Clowers
Thank you so much for sticking with me. I appreciate everyone's comments.
I hope that someone with find this thread useful in the future.
Re: sound issues
On 04/03/12 14:18, Darren Crotchett wrote: I am going to clearly remark as much as possible for the benefit of anyone who may find this page later. See my inline replies/comments. On Sat, Mar 3, 2012 at 12:24 PM, Kelly Clowers kelly.clow...@gmail.com mailto:kelly.clow...@gmail.com wrote: snipped Thank you so much for sticking with me. I appreciate everyone's comments. I hope that someone with find this thread useful in the future. Glad you've got it sorted. To record Skype calls (under PA) I use skype-call-recorder:- http://atdot.ch/scr/download/ Kind regards -- Oh sorry, I was taking life seriously. — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f52e7f7.30...@gmail.com
Re: sound issues
2012/3/2 Darren Crotchett deb...@crotchett.com I am having issues with sound on my son's computer. We are unable to run two sound applications simultaneously. Occasionally, I can stumble upon a combination of more than one (usually two) that will work together. But, it's not repeatable. I have tried a few combinations non of which worked together, such as Skype and Pandora, Pandora and Movie Player (which I guess is Totem), Pandora and VLC. Oddly, even video would not play on Movie Player while another sound application was open, but VLC video would play (without sound). I did not try every combination because I just didn't have time. If you think it would be beneficial, I can go back and do so. I don't know enough about the backend sound systems that these applications use to interpret which combinations, if any, would be significant in terms of troubleshooting. Often times, you would not want two sound apps open at the same time. But, in this case, my son plays Minecraft and talks on Skype. So, it makes sense in that case.It seems that whichever one he starts first gets control of the sound output and the other app can't get any output. He is using Debian Wheezy AMD64. He is using Gnome 3 as the desktop. He is running Pulseaudio. His motherboard is an Asus P8Z68 Deluxe and proc is i7. He has a logitech webcam for input. But, that hasn't been an issue. I only mention it to explain the USB-Audio below. I've been using Debian and Linux for many years. But, I've never been able to wrap my head around sound problems (which I seem to have with every new install). I get confused by alas, esd, pulseaudio and so on. Sound issues have always been hit or miss for me, with something sooner or later just ending up working. I'm not sure how to troubleshoot this. Any suggestions would be greatly appreciated. $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xfae2 irq 74 1 [U0x46d0x821]: USB-Audio - USB Device 0x46d:0x821 USB Device 0x46d:0x821 at usb-:00:1d.0-1.4, high speed 2 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfa08 irq 17 Install jackd, qjackctl and vlc-plugin-jack, kill pulseaudio and use alsa. In VLC preferences-audio choose alsa as output module. Have a look at the device dropdown, there you should see the relevand devices (eg. your intel and hdmi if any). if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. -r -- *L'unica speranza di catarsi, ammesso che ne esista una, resta affidata all'istinto di ribellione, alla rivolta non isterilita in progetti, alla protesta violenta e viscerale.*
Re: sound issues
Thank you so much for this information. I will do that tonight or tomorrow and report back. On Fri, Mar 2, 2012 at 7:35 AM, Raffaele Morelli raffaele.more...@gmail.com wrote: 2012/3/2 Darren Crotchett deb...@crotchett.com I am having issues with sound on my son's computer. We are unable to run two sound applications simultaneously. Occasionally, I can stumble upon a combination of more than one (usually two) that will work together. But, it's not repeatable. I have tried a few combinations non of which worked together, such as Skype and Pandora, Pandora and Movie Player (which I guess is Totem), Pandora and VLC. Oddly, even video would not play on Movie Player while another sound application was open, but VLC video would play (without sound). I did not try every combination because I just didn't have time. If you think it would be beneficial, I can go back and do so. I don't know enough about the backend sound systems that these applications use to interpret which combinations, if any, would be significant in terms of troubleshooting. Often times, you would not want two sound apps open at the same time. But, in this case, my son plays Minecraft and talks on Skype. So, it makes sense in that case.It seems that whichever one he starts first gets control of the sound output and the other app can't get any output. He is using Debian Wheezy AMD64. He is using Gnome 3 as the desktop. He is running Pulseaudio. His motherboard is an Asus P8Z68 Deluxe and proc is i7. He has a logitech webcam for input. But, that hasn't been an issue. I only mention it to explain the USB-Audio below. I've been using Debian and Linux for many years. But, I've never been able to wrap my head around sound problems (which I seem to have with every new install). I get confused by alas, esd, pulseaudio and so on. Sound issues have always been hit or miss for me, with something sooner or later just ending up working. I'm not sure how to troubleshoot this. Any suggestions would be greatly appreciated. $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xfae2 irq 74 1 [U0x46d0x821]: USB-Audio - USB Device 0x46d:0x821 USB Device 0x46d:0x821 at usb-:00:1d.0-1.4, high speed 2 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfa08 irq 17 Install jackd, qjackctl and vlc-plugin-jack, kill pulseaudio and use alsa. In VLC preferences-audio choose alsa as output module. Have a look at the device dropdown, there you should see the relevand devices (eg. your intel and hdmi if any). if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. -r -- *L'unica speranza di catarsi, ammesso che ne esista una, resta affidata all'istinto di ribellione, alla rivolta non isterilita in progetti, alla protesta violenta e viscerale.*
Re: sound issues
On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). It has been a while since I setup PA, and I don't have my Debian box here, so I can't say much until about 5:00 Pacific standard time. When you say Pandora, you mean the internet radio, right? In that case the app is the browser (and not Flash anymore, thankfully. Although even that is better than it used to be). Make sure the PA plugins for various programs are installed: vlc-plugin-pulse gstreamer0.10-pulseaudio Much more when I get home. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=8WHRDGeCixM+niaRJkT8EW0-BVsZYxW=cqzamszkh...@mail.gmail.com
Re: sound issues
2012/3/2 Kelly Clowers kelly.clow...@gmail.com On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it) As I said it's not trivial... but he only needs a loopback device and a jackplugin if he wants to record stuff coming from skype, flashplayers and other non jack compliant apps For vlc+skype to work jack and qjackctl is enough, BTW qjackctl it's the way to go he wants to control everything. -r -- *L'unica speranza di catarsi, ammesso che ne esista una, resta affidata all'istinto di ribellione, alla rivolta non isterilita in progetti, alla protesta violenta e viscerale.*
Re: sound issues
Thanks for feedback. Yes. It is Pandora in Google Chrome. These plugins are installed. $ aptitude search vlc |grep pulse i A vlc-plugin-pulse- PulseAudio plugin for VLC $ aptitude search gstreamer |grep pulse i A gstreamer0.10-pulseaudio- GStreamer plugin for PulseAudio Thanks, Darren On Fri, Mar 2, 2012 at 10:11 AM, Kelly Clowers kelly.clow...@gmail.comwrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). It has been a while since I setup PA, and I don't have my Debian box here, so I can't say much until about 5:00 Pacific standard time. When you say Pandora, you mean the internet radio, right? In that case the app is the browser (and not Flash anymore, thankfully. Although even that is better than it used to be). Make sure the PA plugins for various programs are installed: vlc-plugin-pulse gstreamer0.10-pulseaudio Much more when I get home. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=8WHRDGeCixM+niaRJkT8EW0-BVsZYxW=cqzamszkh...@mail.gmail.com
Re: sound issues
On Fri, Mar 2, 2012 at 10:56 AM, Raffaele Morelli raffaele.more...@gmail.com wrote: 2012/3/2 Kelly Clowers kelly.clow...@gmail.com On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it) As I said it's not trivial... but he only needs a loopback device and a jackplugin if he wants to record stuff coming from skype, flashplayers and other non jack compliant apps For vlc+skype to work jack and qjackctl is enough, BTW qjackctl it's the way to go he wants to control everything. -r Recording hasn't been an issue for me, probably because I haven't actually had the need to try it. But, this sounds interesting because at some point, I might want to grab some audio via a flashplayer or skype.
Re: sound issues
On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120302155630.149e5335.cele...@gmail.com
Re: sound issues
On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=9jy3git78ccev+lnv3yewyjvam3wxkakbftasiro-...@mail.gmail.com
Re: sound issues
On Fri, 2 Mar 2012 13:36:34 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... I don't know what dmix is; it doesn't seem to exist on my system. Sound hardware is: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) I'm pretty sure I had automatic mixing on my previous system, which also had some sort of Intel sound, although I don't have the info available here ATM. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120302165227.2158623b.cele...@gmail.com
Re: sound issues
On Fri, Mar 2, 2012 at 13:52, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 13:36:34 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... I don't know what dmix is; it doesn't seem to exist on my system. Sound hardware is: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) I'm pretty sure I had automatic mixing on my previous system, which also had some sort of Intel sound, although I don't have the info available here ATM. I doubt that has hardware mixing. Dmix is part of alsa, you should have it unless you recompiled alsa without it or something. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=_w79wcdjh_mjtkhgedz0z09jgq-dnglkwryd0hfh5...@mail.gmail.com
Re: sound issues
On Fri, 2 Mar 2012 14:19:32 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 13:52, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 13:36:34 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... I don't know what dmix is; it doesn't seem to exist on my system. Sound hardware is: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) I'm pretty sure I had automatic mixing on my previous system, which also had some sort of Intel sound, although I don't have the info available here ATM. I doubt that has hardware mixing. Dmix is part of alsa, you should have it unless you recompiled alsa without it or something. Okay - so dmix it is; I'm using stock Debian packages for everything, with no specific configuration for my setup. I though that dmix was some sort of command / daemon / package. But you say it only works on occasion? I've never seemed to have any problem with it at all. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120302173811.fab8598d.cele...@gmail.com
Re: sound issues
On Fri, Mar 2, 2012 at 14:38, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 14:19:32 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 13:52, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 13:36:34 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... I don't know what dmix is; it doesn't seem to exist on my system. Sound hardware is: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) I'm pretty sure I had automatic mixing on my previous system, which also had some sort of Intel sound, although I don't have the info available here ATM. I doubt that has hardware mixing. Dmix is part of alsa, you should have it unless you recompiled alsa without it or something. Okay - so dmix it is; I'm using stock Debian packages for everything, with no specific configuration for my setup. I though that dmix was some sort of command / daemon / package. But you say it only works on occasion? I've never seemed to have any problem with it at all. I don't know how often it works. All I know is I have seen other people have problems with it, and I have never had it work on my machines. So when PA got to the early 0.9 series, I installed it and set it up, and never looked back. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=9fni4-tofss2lfrvrotm6f0rcqhpghmqkbxaahr8f...@mail.gmail.com
Re: sound issues
On 03/03/12 09:50, Kelly Clowers wrote: On Fri, Mar 2, 2012 at 14:38, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 14:19:32 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 13:52, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 13:36:34 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 12:56, Celejar cele...@gmail.com wrote: On Fri, 2 Mar 2012 08:11:18 -0800 Kelly Clowers kelly.clow...@gmail.com wrote: On Fri, Mar 2, 2012 at 05:35, Raffaele Morelli raffaele.more...@gmail.com wrote: if you want two or more audio apps to share the same sound device, start qjackctl, tell vlc to use jack output module and do the same with other apps if needed. In qjackctl connection panel you should see all your alsa compliant apps listed as readable clients and the sound device as writeable clients. Using skype together with other apps is also possible even if it's a little more tricky, have a look at http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge I can run skype togeter with other jack/alsa compliant apps, record them and/or route audio output between them using Qjackctl. That sounds excessively complicated. PA will work fine (and automatically), it just needs to be setup correctly. I set mine up long ago, and it has never given me problems (well, a few times the PA volume got muted and had to be unmuted, but that is about it). I use just plain alsa, and while I don't use skype, multiple applications can use my sound devices simultaneously. No special configuration; it just works. Either a sound card with hardware mixing, or you got lucky with alsa's dmix. It has been known to work on occasion... I don't know what dmix is; it doesn't seem to exist on my system. Sound hardware is: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) I'm pretty sure I had automatic mixing on my previous system, which also had some sort of Intel sound, although I don't have the info available here ATM. I doubt that has hardware mixing. Dmix is part of alsa, you should have it unless you recompiled alsa without it or something. Okay - so dmix it is; I'm using stock Debian packages for everything, with no specific configuration for my setup. I though that dmix was some sort of command / daemon / package. But you say it only works on occasion? I've never seemed to have any problem with it at all. I don't know how often it works. All I know is I have seen other people have problems with it, and I have never had it work on my machines. So when PA got to the early 0.9 series, I installed it and set it up, and never looked back. Likewise - multiple Skype connections + my ISPs VOIP, networked sound, virtualbox machines also using sound, and frozenbubble, all at the same time - without a hitch. Alsa, jack, and other sound systems without restrictions running underneath. Initially PA was a learning curve - it's a different way of dealing with sound. Well worth the small amount of effort required to get it working. paman makes life easier if your system doesn't automagically have pa working. Cheers, Kelly Clowers Kind regards -- Oh sorry, I was taking life seriously. — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f5165ac.5040...@gmail.com
Re: Sound issues
Well, assuming you are running alsa modules to run your hardware, then you can use alsaconf (found in the alsa-utils package) to configure the sound levels of your sound card. If you are not using alsa modules you can just get any other mixer (KDE should have one) and fiddle around with the settings in there. If this does not help then tell us what lsmod gives out because somtimes the OSS drivers get loaded along with the alsa drivers and then the sound doesnt work. HTH Oli Þann 2006-06-12, 19:23:53 (+0100) skrifaði Alan Chandler: I few weeks ago, I re-installed debian from scratch (blank partitions apart from my home directories). One of the things I did was let debian totally find all my hardware. I have an SBLive, and it has installed the snd_emu10k1 (and related) modules automatically. However, I get no sound at all. I tried running from console mode (ie kdm was shutdown) as root music123 file.mp3 that I have, and no sound came out at all. The other operating system that I have installed for games has no problem with sound - so clearly all hardware, from sound card to speakers, is working. Looking at a linux sound howto says I should have /dev/audio - but udev (or whatever does it in debian) has not set that up. However it has set up a directory /dev/snd with a number of files in it. Is that the problem? What steps can I take to help diagnose my problem further? -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues-no sound from cd players
On Wed, Dec 10, 2003 at 10:00:01PM -0600, tripolar wrote: | Thanks | hooked up the cdrom drive to soundcard. | now enjoying Tool cd :-) | In the past( I think) I have listened to cd's without that cable. | any idea how that worked? Some cd player software simply sends commands to the drive to play the cd. This requires the drive's audio-out to be connected to the sound card's audio-in. The other option is for the software to extract the data from the cd, process it, and write it out to the sound card. This does not require a direct audio connected between the two. It also requires more complex software processing, and as a result more CPU and bus bandwidth to play. -- One man gives freely, yet gains even more; another withholds unduly, but comes to poverty. Proverbs 11:24 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Sound issues-no sound from cd players
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Dec 10, 2003 at 08:48:37PM -0600, tripolar wrote: $ playsound english.au /dev/dsp did work then I tried cd players again- both gnome kde cdplayers. each cd player picked up my music cd but played no sound. Is your CD player connected to your sound card? Do you have read access to the CD player device? - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/19wUUzgNqloQMwcRAitjAJwJnehfMUw4CuWOfp4PMLBJzqPGAwCgrGMj 8QGgm3VL9xvG0EdfKGT4K4A= =kL50 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues-no sound from cd players
Thanks hooked up the cdrom drive to soundcard. now enjoying Tool cd :-) In the past( I think) I have listened to cd's without that cable. any idea how that worked? On Wed, 2003-12-10 at 20:53, Paul Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Dec 10, 2003 at 08:48:37PM -0600, tripolar wrote: $ playsound english.au /dev/dsp did work then I tried cd players again- both gnome kde cdplayers. each cd player picked up my music cd but played no sound. Is your CD player connected to your sound card? Do you have read access to the CD player device? - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/19wUUzgNqloQMwcRAitjAJwJnehfMUw4CuWOfp4PMLBJzqPGAwCgrGMj 8QGgm3VL9xvG0EdfKGT4K4A= =kL50 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Summary: Re: Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1
Hi, I just wanted to sum up the issue I was experiencing. The emu10k1 depends on the ac97_codec. As both Matt and Bob pointed out modprobe would cover this dependacy. After confirming things worked, I rebuit my kernel successfully with emu10k1 built in which also works as prior research suggested. Thanks for the help :) wolftales [Bob wrote] Try 'modprobe emu10k1' instead. But even better use 'modconf'. modconf Page down to the emu10k1 driver. Select it. Have modconf handle the setting up of this in your system. This is my recommendation. Bob On Thu, 2002-10-31 at 15:29, Matthias Hentges wrote: Am Don, 2002-10-31 um 23.57 schrieb Wolftales: Hi, I am trying to troubleshoot why I do not have sound on my system (specific info below). I have had this hardware configuration working before, using a customer kernel and frozen at the time. What is the cause? Is there a way to fix the module so the kernel can remain stock? Has anyone else ran into related issues with the SB Live card and stock kernels modules? Thank you for any insight into this. Please feel free to request any additional information I can provide. system error messages and config below System: x86 sound card: SB live! 5.1 Kernel: 2.4.18-bf2.4-xfs OS: Sarge error: sandbox:~# insmod emu10k1 Using /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_probe_codec /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_read_proc Just to be sure: did you try a modprobe emu10k1? emu10k1 needs the module ac97_codec which must be loaded before insmodding emu10k1 AFAIK. A modprobe will load this module automagically for you. system info: sandbox:/usr/src/linux# lsmod Module Size Used byNot tainted [...] Right...no ac97_codec. Contact [EMAIL PROTECTED] -- Wolftales \/A Debian/GNU linux user\/,''`. UNIX is user friendly,: :' : it's just picky about who its friends are!`. `' Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1
you can try downloading and compiling the driver from Creative http://www.americas.creative.com/support/files/download.asp?Centric=107OS=12descID=346 = Shawn Lamson Debian Gnu\Linux Sid Kernel 2.4.19-custom XFree86 Version 4.2.1 __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1
Am Don, 2002-10-31 um 23.57 schrieb Wolftales: Hi, I am trying to troubleshoot why I do not have sound on my system (specific info below). I have had this hardware configuration working before, using a customer kernel and frozen at the time. The errors are similar to the problems I had using the stock kernel 2.4.18 2.4.19 as well for debian on this system. The research I have done suggests rebuilding the kernel with SB Live support inside the kernel instead of as a module resolve the issue for some using SUSE, but I would like ti stay with a stock kernel if possible (translated :) system wouldn't boot after attempting that route). What is the cause? Is there a way to fix the module so the kernel can remain stock? Has anyone else ran into related issues with the SB Live card and stock kernels modules? Thank you for any insight into this. Please feel free to request any additional information I can provide. system error messages and config below System: x86 sound card: SB live! 5.1 Kernel: 2.4.18-bf2.4-xfs OS: Sarge error: sandbox:~# insmod emu10k1 Using /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_probe_codec /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_read_proc Just to be sure: did you try a modprobe emu10k1? emu10k1 needs the module ac97_codec which must be loaded before insmodding emu10k1 AFAIK. A modprobe will load this module automagically for you. system info: sandbox:/usr/src/linux# lsmod Module Size Used byNot tainted pcmcia_core41472 0 parport_pc 25672 1 (autoclean) lp 6912 0 (autoclean) parport21696 1 (autoclean) [parport_pc lp] iptable_filter 1672 0 (autoclean) (unused) ip_tables 10392 1 [iptable_filter] lvm-mod46816 0 (unused) nfsd 42792 0 (unused) smbfs 31248 0 (unused) binfmt_misc 5696 1 binfmt_aout 4196 0 usbcore48064 0 sound 52812 0 (unused) soundcore 3236 2 [sound] 3c59x 24624 1 raid0 3080 1 raid1 11820 0 (unused) raid5 15784 0 (unused) xor 8644 0 [raid5] nbd14724 0 (unused) linear 1288 0 (unused) md 43488 1 [raid0 raid1 raid5 linear] sandbox:/usr/src/linux# Right...no ac97_codec. -- Matthias Hentges [www.hentges.net] - PGP + HTML are welcome ICQ: 97 26 97 4 - No files, no URLs My OS: Debian Woody: Geek by Nature, Linux by Choice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1
Wolftales [EMAIL PROTECTED] [2002-10-31 14:57:19 -0800]: I am trying to troubleshoot why I do not have sound on my system (specific info below). I have had this hardware configuration working before, using a customer kernel and frozen at the time. [...] sandbox:~# insmod emu10k1 Using /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_probe_codec /lib/modules/2.4.18-bf2.4-xfs/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol ac97_read_proc Try 'modprobe emu10k1' instead. But even better use 'modconf'. modconf Page down to the emu10k1 driver. Select it. Have modconf handle the setting up of this in your system. This is my recommendation. Bob msg10326/pgp0.pgp Description: PGP signature
