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:
Sound issues on ThinkPad X220T (Lenovo)
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: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver Jack: Succeeded in unlocking 1187 byte memory area Jack: JackShmMem::delete size = 0 index = 1 Jack: Cleaning up shared memory Jack: Cleaning up files Jack: Unregistering server `default' Failed to open server
PulseAudio sound issues
Hi, I'm using Debian Wheezy Testing on both my desktop computer and my Laptop. On the Laptop the sound works fine, but on the desktop I can't play two or more sounds at the same time, for example while watching a video on VLC, hitting pause, then opening a video on YouTube. Other problem is: after watching a video on VLC and closing VLC, I have to wait 20 seconds to open a new VLC program since otherwise the sound coming out of the speakers will be garbage. Since after killing the PulseAudio daemon with pulseaudio -k the problems goes away, it is my strong opinion that this is a PulseAudio issue. My workaround so far was to remove the execution permissions on PulseAdio with: chmod a-x /usr/bin/pulseaudio I have two questions: 1. How can I debug this problem? I'd like to file an appropiate bug on the corresponding bug tracker. 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? -- Alejandro Santos -- 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/CAKMi1Tzpqc4+txeahjKggqn6+s--X4u9-YFC=mgpja_scmx...@mail.gmail.com
Re: PulseAudio sound issues
On Thu, Oct 11, 2012 at 10:21:54AM -0300, Alejandro Santos wrote: Hi, I'm using Debian Wheezy Testing on both my desktop computer and my Laptop. On the Laptop the sound works fine, but on the desktop I can't play two or more sounds at the same time, for example while watching a video on VLC, hitting pause, then opening a video on YouTube. Other problem is: after watching a video on VLC and closing VLC, I have to wait 20 seconds to open a new VLC program since otherwise the sound coming out of the speakers will be garbage. Is your VLC configured to use Pulseaudio? You'll get best results with Pulseaudio using an all-or-nothing approach. Since after killing the PulseAudio daemon with pulseaudio -k the problems goes away, it is my strong opinion that this is a PulseAudio issue. My workaround so far was to remove the execution permissions on PulseAdio with: chmod a-x /usr/bin/pulseaudio I have two questions: 1. How can I debug this problem? I'd like to file an appropiate bug on the corresponding bug tracker. Probably your first action is to determine which package is at fault. Try playing a sound with paplay and then playing it again within 20 seconds. If you hear garbage the second time, then it's probably a pulseaudio problem. If you don't hear problems, then it probably IS a VLC issue. 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? Due to various differences of opinion gnome-core isn't as minimal as its title might have you believe. If you need Gnome without pulseaudio, try removing the gnome-core package, but add everything it depends on. In answer to your other question, though, Pulseaudio is a networked sound server. It has a lot more capability than ALSA does such as the ability to stream audio over a network, the ability to (fairly) easily manage multiple sources AND sinks (that is, you can replicate 4.0 surround sound using two sound cards, or even two computers). See the wikipedia article for a nice intro: https://en.wikipedia.org/wiki/PulseAudio signature.asc Description: Digital signature
Re: PulseAudio sound issues
On Thu 11 Oct 2012 at 10:21:54 -0300, Alejandro Santos wrote: Since after killing the PulseAudio daemon with pulseaudio -k the problems goes away, it is my strong opinion that this is a PulseAudio issue. My workaround so far was to remove the execution permissions on PulseAdio with: chmod a-x /usr/bin/pulseaudio The Debian way: update-rc.d pulseaudio disable 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I'm just a user and I ask myself, why install gnome-core when all the bits and pieces to make a customised GNOME are in the archive? -- 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/20121011144527.GN30872@desktop
Re: PulseAudio sound issues
On 11/10/2012 15:21, Alejandro Santos wrote: Hi, I'm using Debian Wheezy Testing on both my desktop computer and my Laptop. On the Laptop the sound works fine, but on the desktop I can't play two or more sounds at the same time, for example while watching a video on VLC, hitting pause, then opening a video on YouTube. Other problem is: after watching a video on VLC and closing VLC, I have to wait 20 seconds to open a new VLC program since otherwise the sound coming out of the speakers will be garbage. Hi, on Wheezy/Sid here I use Pulseaudio without problem. VLC is configured to output to pulse (vlc-plugin-pulse installed), works fine here, vlc and flash or anything else. I use KDE, did nothing special to make it work, only timidity gave me trouble but it was easily solved. User belongs to pulse group. Since after killing the PulseAudio daemon with pulseaudio -k the problems goes away, it is my strong opinion that this is a PulseAudio issue. My workaround so far was to remove the execution permissions on PulseAdio with: chmod a-x /usr/bin/pulseaudio I have two questions: 1. How can I debug this problem? I'd like to file an appropiate bug on the corresponding bug tracker. Make sure the problem really lies with Pulse. You could start by dumping pulse config with --dump-conf, change log level (--log-level). Install debug packages. 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I can play a flash video or listen to the bbc player and watch a video in vlc at the same time. I can throw Amarok into the mix or use at the same time Tuxguitar outputting through timidity and vlc (nice to write tabs from a concert video ;-). I can just click on the kde mixer applet and adjust output volume for each application separately. Record with a lightweight device and stream the sound to another powerful computer over the LAN to process it, and I am not even scratching the surface of what can be done with Pulse. I have been defiant toward anything pulse for a long time as it used to screw things up out of the box more than often (in KDE in my case). I adopted it not long ago, and I would be sad going back. My only complaint is that it isn't trivial to make it play with jackd, but given the nature of jack and the rarity of this setup it's not surprising. -- 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/5076dc4f.3050...@googlemail.com
Re: PulseAudio sound issues
On Thu, Oct 11, 2012 at 11:45 AM, Brian a...@cityscape.co.uk wrote: On Thu 11 Oct 2012 at 10:21:54 -0300, Alejandro Santos wrote: My workaround so far was to remove the execution permissions on PulseAdio with: chmod a-x /usr/bin/pulseaudio The Debian way: update-rc.d pulseaudio disable By default, PulseAudio is on Debian Wheezy configured not to start as an init.d SysV daemon. That won't work. 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I'm just a user and I ask myself, why install gnome-core when all the bits and pieces to make a customised GNOME are in the archive? Since I am not a native English speaker I must be missing something in the translation on my head. Can you explain further this comment? Thanks, -- Alejandro Santos -- 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/CAKMi1Tx_Y1-3KneMN1qjvkPkcgDtHoRRtpqM6_Cga8nD=ma...@mail.gmail.com
Re: PulseAudio sound issues
On Thu, Oct 11, 2012 at 11:48 AM, tv.deb...@googlemail.com tv.deb...@googlemail.com wrote: Hi, on Wheezy/Sid here I use Pulseaudio without problem. VLC is configured to output to pulse (vlc-plugin-pulse installed), works fine here, vlc and flash or anything else. I use KDE, did nothing special to make it work, only timidity gave me trouble but it was easily solved. User belongs to pulse group. Before posting my initial message, I have actually read the debian-user mailing list archives, and I know for a fact that PulseAudio can generate some heated discussions. I do know that PulseAudio works for most people. Thanks for your vote of confidence. But please, don't transform this thread on yet-anoter-X-software-is-{awesome/crap}. I want my sound working, and I want to fix PulseAudio. Thanks again, -- Alejandro Santos -- 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/cakmi1tyyex+suu7ggsvot4lxpyc0prua72_4ndyhpk4dmem...@mail.gmail.com
Re: PulseAudio sound issues
On 11/10/2012 18:12, Alejandro Santos wrote: On Thu, Oct 11, 2012 at 11:48 AM, tv.deb...@googlemail.com tv.deb...@googlemail.com wrote: Hi, on Wheezy/Sid here I use Pulseaudio without problem. VLC is configured to output to pulse (vlc-plugin-pulse installed), works fine here, vlc and flash or anything else. I use KDE, did nothing special to make it work, only timidity gave me trouble but it was easily solved. User belongs to pulse group. Before posting my initial message, I have actually read the debian-user mailing list archives, and I know for a fact that PulseAudio can generate some heated discussions. I do know that PulseAudio works for most people. Thanks for your vote of confidence. But please, don't transform this thread on yet-anoter-X-software-is-{awesome/crap}. I want my sound working, and I want to fix PulseAudio. Thanks again, Wasn't my intention, was responding to : I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does ^^^ PulseAudio gives me as a user over good ol' ALSA? Kind of sounds as an invite for yet another a heated discussion over the merits of pulse... I tried to be factual, give clues of what could be missing in your setup, and did say in another part of the message that I wasn't a pulseaudio fanboy, just a currently happy user. Sorry for polluting your thread with silly attempts to help you. -- 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/5076fc7d.6000...@googlemail.com
Re: PulseAudio sound issues
On 11/10/2012 18:07, Alejandro Santos wrote: On Thu, Oct 11, 2012 at 11:45 AM, Briana...@cityscape.co.uk wrote: On Thu 11 Oct 2012 at 10:21:54 -0300, Alejandro Santos wrote: [snip] 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I'm just a user and I ask myself, why install gnome-core when all the bits and pieces to make a customised GNOME are in the archive? Since I am not a native English speaker I must be missing something in the translation on my head. Can you explain further this comment? Thanks, Not a native English speaker either, but what I understand is: don't install metapackages and then complain that they are crap-bags, use them as guidance to install what you really need among their dependencies. -- 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/5076fd6c@googlemail.com
Re: PulseAudio sound issues
Alejandro Santos lis...@alejolp.com writes: […] 1. How can I debug this problem? I'd like to file an appropiate bug on the corresponding bug tracker. While I'm not a PulseAudio user myself, some of those I know use it, so I'm somewhat interested in that, too. (Thanks to Darac Marjal for his hints on P-A debugging elsewhere in this thread, BTW.) […] I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I remember playing with both GNOME and KDE back in 2000 or so. Honestly, I still don't get what advantages do they give to me over the good old “bunch of X applications” approach. (Though I've discovered somewhat recently that there're a few interesting Qt-based applications in Debian. Previously, anything depending on Qt was out of consideration for me.) -- FSF associate member #7257 -- 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/861uh4hqj2@gray.siamics.net
Re: PulseAudio sound issues
[received personally, forwarding to list] On 11/10/2012 19:20, Yaro Kasear wrote: On 10/11/2012 12:10 PM, tv.deb...@googlemail.com wrote: On 11/10/2012 18:07, Alejandro Santos wrote: On Thu, Oct 11, 2012 at 11:45 AM, Briana...@cityscape.co.uk wrote: On Thu 11 Oct 2012 at 10:21:54 -0300, Alejandro Santos wrote: [snip] 2. I can't purge the package with aptitude purge pulseaudio since the package pulseaudio is a dependency on gnome-core. After killing PulseAudio, the sound works fine. I'm a software developer myself, and I can't help keep asking myself, why is PulseAudio an strong dependency on Gnome? What advantages does PulseAudio gives me as a user over good ol' ALSA? I'm just a user and I ask myself, why install gnome-core when all the bits and pieces to make a customised GNOME are in the archive? Since I am not a native English speaker I must be missing something in the translation on my head. Can you explain further this comment? Thanks, Not a native English speaker either, but what I understand is: don't install metapackages and then complain that they are crap-bags, use them as guidance to install what you really need among their dependencies. Fortunately if you don't use GNOME (Why anyone subjects themselves to GNOME 3 willingly is beyond me, but a different topic altogether. There's a very good reason why MATE forked off.), then you don't have to put up with Pulseaudio usually. It really is a pain to work with if you don't accept its default configurations, which have a 50% chance of guessing the ideal settings for your system wrong. Frankly I've always found that bare ALSA works fine in almost all cases, a far higher functionality rate than PA. -- 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/50770fbe.2060...@googlemail.com
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
sound issues
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
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: Adobe flash sound issues
On Fri, Jun 24, 2011 at 21:25 +0200, Andrej Kacian wrote: On Tue, 14 Jun 2011 00:50:13 +0100 Wolodja Wentland babi...@gmail.com wrote: $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/iceweasel $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/chromium Thanks for this! I noticed some weird sound artifacts in flash videos, but didn't have the time to investigate. Next thing I open debian-user ML folder, and the solution (well, workaround really) is staring right at me. :) Please note that the paths changed due to the multiarch [0] transition. You now have to use: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libc/memcpy-preload.so Have fun! [0] http://wiki.debian.org/Multiarch/ -- .''`. Wolodja Wentlandbabi...@gmail.com : :' : `. `'` 4096R/CAF14EFC `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC signature.asc Description: Digital signature
Re: Adobe flash sound issues
On Tue, 14 Jun 2011 00:50:13 +0100 Wolodja Wentland babi...@gmail.com wrote: $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/iceweasel $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/chromium Thanks for this! I noticed some weird sound artifacts in flash videos, but didn't have the time to investigate. Next thing I open debian-user ML folder, and the solution (well, workaround really) is staring right at me. :) -- Andrej Kacian -- 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/20110624212536.4041f672@penny
Re: Adobe flash sound issues
Hi I had the same problem, and this fixed it http://earth.rockinthebury.com/?p=104 Martin On Friday 03 June 2011 13:01:27 John Kapnogiannis wrote: Hello there. I got an annoying problem with flash sound. On some services (eg Grooveshark) I hear scratches and deformities during playback. The actuall track is heard on the background though. I have flash installed through the flashplugin-nonfree packages. The problem even exists on Google Chrome, which is supposed to use a flash installation of its own. As far as I know flash version is not the latest. I am using Debian testing on a Dell Studio 1555 laptop with kde and alsa. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) : This is what lspci gives me about my sound card. This may be related to my problem, cause for a few weeks vlc gives me an error that the soundcard is already in use when another sound is already playing. In case you need more info, just tell. Thanks in advance for your help, John P.S: Please CC me in your replies cause I am not subscribed to this mailing list -- 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/201106131123.03296.kom...@uvt.cz
Re: Adobe flash sound issues
On Fri, Jun 03, 2011 at 14:01 +0300, John Kapnogiannis wrote: I got an annoying problem with flash sound. On some services (eg Grooveshark) I hear scratches and deformities during playback. The actuall track is heard on the background though. I have flash installed through the flashplugin-nonfree packages. The problem even exists on Google Chrome, which is supposed to use a flash installation of its own. As far as I know flash version is not the latest. I am using Debian testing on a Dell Studio 1555 laptop with kde and alsa. I guess that you are using amd64 and that the problem you are seeing is due to a difference in the memcpy implementation in libc6. Could you try to run iceweasel or chromium in the following way: $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/iceweasel $ LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/chromium You can find details about this in /usr/share/doc/libc6/README.Debian.gz and I would suggest to create a little shell script like the following: --- snip --- #!/bin/sh LD_PRELOAD=/usr/lib/libc/memcpy-preload.so /usr/bin/iceweasel --- snip --- and place is somewhere in your PATH (~/bin comes to mind) if that does indeed solve the problem. Note that the path to memcpy-preload.so will change to a multiarch conforming one in the next libc6 version that will hit wheezy. You can then find it in /usr/lib/x86_64-linux-gnu/libc/memcpy-preload.so - but you will be automatically informed about this is you have apt-listchanges installed. If you don't install it and apt-listbugs with it. :) I recommend reading the bug report on RedHat's bugtracker, it is worth your time if you want to understand what is going on here. -- .''`. Wolodja Wentlandbabi...@gmail.com : :' : `. `'` 4096R/CAF14EFC `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC signature.asc Description: Digital signature
Adobe flash sound issues
Hello there. I got an annoying problem with flash sound. On some services (eg Grooveshark) I hear scratches and deformities during playback. The actuall track is heard on the background though. I have flash installed through the flashplugin-nonfree packages. The problem even exists on Google Chrome, which is supposed to use a flash installation of its own. As far as I know flash version is not the latest. I am using Debian testing on a Dell Studio 1555 laptop with kde and alsa. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) : This is what lspci gives me about my sound card. This may be related to my problem, cause for a few weeks vlc gives me an error that the soundcard is already in use when another sound is already playing. In case you need more info, just tell. Thanks in advance for your help, John P.S: Please CC me in your replies cause I am not subscribed to this mailing list
Re: Adobe flash sound issues
On Fri, 03 Jun 2011 14:01:27 +0300, John Kapnogiannis wrote: Hello there. I got an annoying problem with flash sound. On some services (eg Grooveshark) I hear scratches and deformities during playback. The actuall track is heard on the background though. I have flash installed through the flashplugin-nonfree packages. The problem even exists on Google Chrome, which is supposed to use a flash installation of its own. As far as I know flash version is not the latest. I am using Debian testing on a Dell Studio 1555 laptop with kde and alsa. I would first check if you have installed the latest version (for linux that's now 10.3.181.14): http://www.adobe.com/software/flash/about/ If not, try with the most updated flash player from Adobe. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) : This is what lspci gives me about my sound card. This may be related to my problem, cause for a few weeks vlc gives me an error that the soundcard is already in use when another sound is already playing. lsof | grep snd will tell you if there is some sound process opened. In case you need more info, just tell. Thanks in advance for your help, John P.S: Please CC me in your replies cause I am not subscribed to this mailing list Sorry but I can't :-( You can read the mailing list archive. Greetings, -- Camaleón -- 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/pan.2011.06.03.11.35...@gmail.com
Re: list spam, reinstall and sound issues
On Sunday 30 July 2006 08:48, Andrew Sackville-West wrote: [...] sound. my spiffy new board has a via vt8233 sound chip, and I can't get alsa up and running. Alsaconf sees the chipset and claims to have configured it, but [EMAIL PROTECTED]:~$ aplay music/You\ Shook\ Me.mp3 ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3947:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:547: audio open error: No such device [...] Try aplay -L to list all PCMs, and if there are several, try specifying them with aplay -D [$DEVICE]. If one works, you can make it the default with a ~.asoundrc or /etc/asound.conf file. HTH, John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: list spam, reinstall and sound issues
On Mon, Jul 31, 2006 at 08:16:02PM +1000, John O'Hagan wrote: On Sunday 30 July 2006 08:48, Andrew Sackville-West wrote: [...] sound. my spiffy new board has a via vt8233 sound chip, and I can't get alsa up and running. Alsaconf sees the chipset and claims to have configured it, but [EMAIL PROTECTED]:~$ aplay music/You\ Shook\ Me.mp3 ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3947:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:547: audio open error: No such device [...] Try aplay -L to list all PCMs, and if there are several, try specifying them with aplay -D [$DEVICE]. If one works, you can make it the default with a ~.asoundrc or /etc/asound.conf file. damn, sometimes I amaze myself. solved with a `adduser andrew audio`. crap. this is why one should never reinstall... A signature.asc Description: Digital signature
list spam, reinstall and sound issues
Hi list, first let me apologise for the huge amount of bounced messages a recently barfed out of my system. I had quite a lot of queued up mail on my server (1200+ messages) that hit my improperly configured local exim and got rejected all over the place. so, sorry 'bout that. so why was my exim mis-configured? cause I lost my mobo, and forgot to keep a copy of my custom exim4.conf. ugh. I know there has been discussion in the past about dealing with major system changes my old mobo died, so I put my drives into a new one and booted up to see what would happen... kernel failed to find my harddrives as the right modules were probably not in the initrd. Isn't there a way to chroot in through knoppix and rebuild that stuff? I tried several things, to no avail and would like to work it out in case it happens again. sound. my spiffy new board has a via vt8233 sound chip, and I can't get alsa up and running. Alsaconf sees the chipset and claims to have configured it, but [EMAIL PROTECTED]:~$ aplay music/You\ Shook\ Me.mp3 ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3947:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:547: audio open error: No such device any clue here? A [EMAIL PROTECTED]:~$ lspci -s 00:11.5 -vvv 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) Subsystem: ASRock Incorporation Unknown device 1617 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin C routed to IRQ 185 Region 0: I/O ports at dc00 [size=256] Capabilities: access denied [EMAIL PROTECTED]:~$ lsmod | grep snd snd_seq_dummy 4100 0 snd_seq_oss28928 0 snd_seq_midi8416 0 snd_seq_midi_event 7424 2 snd_seq_oss,snd_seq_midi snd_seq46736 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_via82xx26200 0 snd_ac97_codec 82976 1 snd_via82xx snd_ac97_bus2624 1 snd_ac97_codec snd_pcm_oss36704 0 snd_mixer_oss 16192 1 snd_pcm_oss snd_pcm74884 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss snd_timer 21124 2 snd_seq,snd_pcm snd_page_alloc 9800 2 snd_via82xx,snd_pcm snd_mpu401_uart 7808 1 snd_via82xx snd_rawmidi23200 2 snd_seq_midi,snd_mpu401_uart snd_seq_device 8012 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi snd48548 11 snd_seq_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 9440 1 snd gameport 14600 2 snd_via82xx,analog signature.asc Description: Digital signature
Sound issues
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]
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: Sarge Sound Issues
Ben Alls wrote: kde uses oss by default, try to set arts to use ALSA in the KControl panel. go to sound options, and advanced (i think) to change the driver to alsa rather than oss. if that doesnt work, try un-installin alsa and adding snd-mixer-oss and snd-pcm-oss to you /etc/modules file. it worked for me. i have the same sound card :) another hint dont use kde or gnome :P Thanks for the info. Did you possibly confuse me with another post? I posted about a media player problem with movie trailer and clips which is now resolved. Perhaps you are saying that the sound is part of the problem? I had to use ALSA-OSS on a previous testing version of sarge to get sound working on my YMF724F card but sound worked right out of the box on sarge stable, so, I think I'll stay with it unless I start having problems. Regarding KDE, I prefer a GUI over a console. I only use konsole for upgrading and troubleshooting and file location. Perhaps I'm being cced on someone else's post. I do know a person who has a sound issue with his card using sarge testing but it's no a Yamaha card. I'll keep your suggestions in mind just in case. It sounds just like what i had to do on sarge testing to get sound going. Leonard Chatagnier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Sarge Sound Issues
kde uses oss by default, try to set arts to use ALSA in the KControl panel. go to sound options, and advanced (i think) to change the driver to alsa rather than oss. if that doesnt work, try un-installin alsa and adding snd-mixer-oss and snd-pcm-oss to you /etc/modules file. it worked for me. i have the same sound card :) another hint dont use kde or gnome :P
Re: Confusing sound issues (ALSA, jackd, etc.)
Silvan wrote: On Saturday 14 August 2004 06:46 pm, Inge Thorin Eidsaether wrote: Haven't tried recording yet. So I installed Ardour. Ardour won't work unless jackd is running, which it wasn't: Hm. Found out I needed the LSM realtime module. Alternatively, you can just run JACK and Ardour as a regular user. If you start it with jackd and don't elect to start with realtime set, it will work fine. It's true you will probably never get useful performance doing it this way, but it runs. Is jackd (the debian package) compiled with all necessary flags? Like --enable-capabilites ? How do I find out? It works on patched 2.4 kernels. I have no idea about 2.6. It may be there's some different capabilities library it needs to be compiled against or something. Pure speculation. This is what I get trying to start jackd with a 2.6.7-1-386 kernel on an AMD K6-2/350 in case anyone has any ideas: [EMAIL PROTECTED]:~$ sudo jackd -v -s -d alsa getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_iec61883.so getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_alsa.so getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_dummy.so getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_oss.so jackd 0.98.1 Copyright 2001-2003 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details Illegal instruction I have looked at Sylvan's excellent materials. TIA, Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confusing sound issues (ALSA, jackd, etc.)
On Saturday 14 August 2004 06:46 pm, Inge Thorin Eidsaether wrote: Haven't tried recording yet. So I installed Ardour. Ardour won't work unless jackd is running, which it wasn't: Hm. Found out I needed the LSM realtime module. Alternatively, you can just run JACK and Ardour as a regular user. If you start it with jackd and don't elect to start with realtime set, it will work fine. It's true you will probably never get useful performance doing it this way, but it runs. Is jackd (the debian package) compiled with all necessary flags? Like --enable-capabilites ? How do I find out? It works on patched 2.4 kernels. I have no idea about 2.6. It may be there's some different capabilities library it needs to be compiled against or something. Pure speculation. The more I read the more questions I have, like: - What FAQ, guide, tutorial etc. is the most authoritative and updated on the subject? Differences abound, depending on kernel version, etc. I'm writing a thorough guide to Rosegarden, and JACK is a big issue I need to deal with. I've spent a lot of time surfing, reading, trying to educate myself. The state of audio documentation is absolutely PATHETIC. Much of the documentation keeps referring to places where kernel 2.4.0 is spoken of in the future tense for crying out loud. Everyone, and every google search all keep referring to the same conglomeration of crap that evidently must make perfect sense to someone somewhere, but certainly not to me. - What files must be present for all this to work, (ALSA, jackd and all features of Soundblaster Live) on a system running the 2.6.7 kernel, and what magic do they possibly contain? I have absolutely no clue about 2.6 kernels. I'm not running one yet, and I don't support them. You can have my recipe for getting a happy JACK with a 2.4 kernel though. Add the following line to your sources.list: # AGNULA deb http://apt.agnula.org/demudi/ testing main local extra Update, then get (as needed, and with suitable arch if necessary): alsa-modules-2.4.25-1-multimedia-686 kernel-headers-2.4.25-1-multimedia-686 kernel-image-2.4.25-1-multimedia-686 kernel-pcmcia-modules-2.4.25-1-multimedia-686 They don't make it very obvious to the casual browser, but they maintain a repository of Debian packages. No need to replace your running system with something off the CD. Just install AGNULA packages whenever they're available and take the rest from Sid or Sarge. Then you might want to have a look at my book. While I deal mostly with MIDI issues, I do cover JACK. I'm trying to deal with all of this on a KISS, least you need to know level, and keep it distro-neutral, so don't expect an authoritative JACK treatise. (I couldn't write one if you paid me anyway. The least you need to know, in this case, is very nearly all that I *do* know after months wrestling with this most wretched of subjects.) I've just committed a new round of changes to document my latest success with the AGNULA kernel. That version won't get rsynced out to the web server until tomorrow sometime, so here's the URL to the PDF version instead. I host this myself, and I just updated it. You want to look at chapter 2.2: http://users.adelphia.net/~silvan/using-rosegarden.pdf If you decide to play with Rosegarden for audio work, I'm afraid I still haven't really dealt with the vagaries of recording with Rosegarden yet, and neither have I mentioned managing audio files. All of that is coming in the next few weeks, along with detailed instructions for managing the evil bastard mixer from hell on the SB Live! to control which audio sources get recorded. I'm still in the playing with it to figure it out stage, really, since I've only just gotten Rosegarden's audio features working smoothly for myself, after nearly two years with the project. -Why on Earth must all this be so convoluted? (sigh...) Tell me about it. The up side is that once you do finally get it working, it's pretty cool. Install the LADSPA stuff to get plugins up the wazoo: swh-plugins - Steve Harris's LADSPA plugins tap-plugins - Tom's Audio Processing LADSPA plugins I could go on, but let's see how far you get. -- Michael McIntyre Silvan [EMAIL PROTECTED] Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Confusing sound issues (ALSA, jackd, etc.)
Hi I'm having a few problems getting jackd to work on my Debian box (testing, kernel 2.6.7) The soundcard is a Soundblaster Live. Sequencial summary (so far): ALSA seems to be working, that is: playback works. Haven't tried recording yet. So I installed Ardour. Ardour won't work unless jackd is running, which it wasn't: -- Ardour/GTK 0.453.1 running with libardour 0.728.1 Loading UI configuration file /etc/ardour/ardour_ui.rc ardour: [ERROR]: Could not connect to JACK server as ardour Killed -- Aha, jackd it is, then. Tried starting jackd (or jackstart, as a regular user): --- cannot get realtime capabilities, current capabilities are: =ep cap_setpcap-e probably running under a kernel with capabilities disabled, a suitable kernel would have printed something like =eip --- Hm. Found out I needed the LSM realtime module. Why didn't the error message just say this? Or point to some place with more info on the problem? Even though I read somewhere that latency issues and such was now dealt with in kernel config, not in patches or modules? Could be my mistake. No big deal. Made sure kernel was configured as per the instructions for building the LSM realtime module. Meaning: CONFIG_MODULES=y CONFIG_SECURITY=y CONFIG_SECURITY_CAPABILITIES=m CONFIG_SECURITY_SELINUX=y CONFIG_MODULE_UNLOAD=y Built a kernel including the above options, then downloaded, compiled and installed the LSM realtime module, and it's seemed to load OK with no error messages: # modprobe realtime allcaps=1 # lsmod | grep realtime realtime9616 0 Tried starting jackd (or jackstart, as a regular user): Now it just says 'illegal instruction'. Nothing more. No matter what arguments I give. By the way: LD_ASSUME_KERNEL=2.4.19 is set in .bash_profile to account for the 'creating SCHED_FIFO threads for real-time processing'-issue mentioned on jackit.sourceforge.net/docs/faq.php#a53 Is jackd (the debian package) compiled with all necessary flags? Like --enable-capabilites ? How do I find out? *Taking a deep breath* I've spent more time than I like to admit tinkering with this, reading faqs, guides and tips from everywhere, but still not getting it to work. I'm just about ready to throw the towel in and go back to win98 (only for audio recording). Tried Agnula's DeMuDi, a dedicated Linux distro for Audio work, which indeed looked promising, and may work well, but: 1) v1.0 didn't recognize my serial mouse (Hellooo???) 2) v1.2 didn't recognize itself (the CD) as a valid Debian CD and refused to install (could be my CDROM needs a cleaning?) But I digress... The more I read the more questions I have, like: - What FAQ, guide, tutorial etc. is the most authoritative and updated on the subject? Differences abound, depending on kernel version, etc. - What files must be present for all this to work, (ALSA, jackd and all features of Soundblaster Live) on a system running the 2.6.7 kernel, and what magic do they possibly contain? -Why on Earth must all this be so convoluted? (sigh...) This is by far the biggest show stopper for me since, starting with Linux (first time in '95). I am most certainly not a guru, but no newbie anymore, either. I would like to spend some time actually doing some (audio) work, too. And my family likes to see my face in awhile. Is there a script available that takes the guesswork out of the installation of all of the necessary components? Obviously I'm not a programmer, so making one is out of my league. Sorry for whining, but now it's out of my system... I'm not subscribing to debian-user, but will search the mailing list for (hopefully) any answers. They will be most appreciated... Feel free to cc me your opinion, though. Thanks in advance, -- Inge Thorin Eidsaether probot at warpmail dot net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confusing sound issues (ALSA, jackd, etc.)
Inge - waves of empathy i had a very similar set of problems...finally found out about the realtime-lsm, but simply could not get the damned thing to compile,(see my mail of yesterday - maybe someone will still be able to help) so you were a step ahead of me... i am now trying with a demudi installan improvement for me, but it still is not doing all it should. What with that and a grizzly bug in audacity that means i can't edit with that either, i also contemplate throwing in the towel after a decade of *nix use... It really is still a bit of an uphill battle. Hopefully Agnula will produce something worthwhile, most importantly because they seem to be intent on producing documentation. good :) The problem at the moment seems to be that the different distros, and the 2.4/2.6 and all the 2.6's all are sufficiently different on the alsa/c things to make any partial clues culled from google not always very useful. Do let us know if you have a breakthrough/insights. dee On Sun, 15 Aug 2004, Inge Thorin Eidsaether wrote: Hi I'm having a few problems getting jackd to work on my Debian box (testing, kernel 2.6.7) The soundcard is a Soundblaster Live. Sequencial summary (so far): ALSA seems to be working, that is: playback works. Haven't tried recording yet. So I installed Ardour. Ardour won't work unless jackd is running, which it wasn't: -- Ardour/GTK 0.453.1 running with libardour 0.728.1 Loading UI configuration file /etc/ardour/ardour_ui.rc ardour: [ERROR]: Could not connect to JACK server as ardour Killed -- Aha, jackd it is, then. Tried starting jackd (or jackstart, as a regular user): --- cannot get realtime capabilities, current capabilities are: =ep cap_setpcap-e probably running under a kernel with capabilities disabled, a suitable kernel would have printed something like =eip --- Hm. Found out I needed the LSM realtime module. Why didn't the error message just say this? Or point to some place with more info on the problem? Even though I read somewhere that latency issues and such was now dealt with in kernel config, not in patches or modules? Could be my mistake. No big deal. Made sure kernel was configured as per the instructions for building the LSM realtime module. Meaning: CONFIG_MODULES=y CONFIG_SECURITY=y CONFIG_SECURITY_CAPABILITIES=m CONFIG_SECURITY_SELINUX=y CONFIG_MODULE_UNLOAD=y Built a kernel including the above options, then downloaded, compiled and installed the LSM realtime module, and it's seemed to load OK with no error messages: # modprobe realtime allcaps=1 # lsmod | grep realtime realtime9616 0 Tried starting jackd (or jackstart, as a regular user): Now it just says 'illegal instruction'. Nothing more. No matter what arguments I give. By the way: LD_ASSUME_KERNEL=2.4.19 is set in .bash_profile to account for the 'creating SCHED_FIFO threads for real-time processing'-issue mentioned on jackit.sourceforge.net/docs/faq.php#a53 Is jackd (the debian package) compiled with all necessary flags? Like --enable-capabilites ? How do I find out? *Taking a deep breath* I've spent more time than I like to admit tinkering with this, reading faqs, guides and tips from everywhere, but still not getting it to work. I'm just about ready to throw the towel in and go back to win98 (only for audio recording). Tried Agnula's DeMuDi, a dedicated Linux distro for Audio work, which indeed looked promising, and may work well, but: 1) v1.0 didn't recognize my serial mouse (Hellooo???) 2) v1.2 didn't recognize itself (the CD) as a valid Debian CD and refused to install (could be my CDROM needs a cleaning?) But I digress... The more I read the more questions I have, like: - What FAQ, guide, tutorial etc. is the most authoritative and updated on the subject? Differences abound, depending on kernel version, etc. - What files must be present for all this to work, (ALSA, jackd and all features of Soundblaster Live) on a system running the 2.6.7 kernel, and what magic do they possibly contain? -Why on Earth must all this be so convoluted? (sigh...) This is by far the biggest show stopper for me since, starting with Linux (first time in '95). I am most certainly not a guru, but no newbie anymore, either. I would like to spend some time actually doing some (audio) work, too. And my family likes to see my face in awhile. Is there a script available that takes the guesswork out of the installation of all of the necessary components? Obviously I'm not a programmer, so making one is out of my league. Sorry for whining, but now it's out of my system... I'm not subscribing to debian-user, but will search the mailing list for (hopefully)
Sound issues resolved, thanks all!
Thanks, everyone! Due to Chris Metzler's comment about the ESD in Gnome, I checked the sound options in the gnome desktop preferences, and by unchecking enable sound server startup my woes were ended. I hate it when it's easier than you're expecting, and you don't look at what's right in front of your face. Oh well, at least it's fixed now. thanks, all! --Phil Ramey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux Sound Issues
Paul, (...) that is skips whenever I do anything that requires CPU resources. I've tried recompiling the kernel to make it more efficient and I've tried using the latest drivers from Creative. Mmh, it's probably just your IDE drive which is *not* accessed in DMA mode. At least, that's what caused sound problems on my system. Before playing around with low latency and preemtive kernel patches, try the following: Run hdparm -d {drive} and check wheter or not DMA mode is activated for your drive. If DMA mode is not activated, try hdparm -d 1 {drive}. If hdparm is unable to enable DMA mode, chances are that your kernel does not support your IDE chipset. Run lspci and make sure your kernel was compiled with support for both your chipset and DMA mode. Regards, Remo -- 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
Sound issues-no sound from cd players
$ 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. I then tried to listen to linus again $ playsound english.au /dev/dsp this time bash: /dev/dsp: Device or resource busy this is what fuser shows # fuser -v /dev/dsp USERPID ACCESS COMMAND /dev/dsp suley 2025 f artsd suley 2080 f artsd ok did #killall artsd now playsound works again what am i missing to get cdplayers to play sound? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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]
Re: Linux Sound Issues
Hmm, I think hdparm did the trick... turin:~# hdparm -t /dev/hdb /dev/hdb: Timing buffered disk reads:8 MB in 3.76 seconds = 2.13 MB/sec turin:~# hdparm -d1 /dev/hdb /dev/hdb: setting using_dma to 1 (on) using_dma= 1 (on) turin:~# hdparm -t /dev/hdb /dev/hdb: Timing buffered disk reads: 106 MB in 3.01 seconds = 35.22 MB/sec I thought of messing around with hdparm, never realized how easy it was. So far I haven't noticed any audio skipping when playing movies in kplayer or playing mp3s while running find and apt-cache search at the same time and didn't hear any skipping. Although I've heard that enabling DMA on VIA686B could cause data corruption and that's why it's disabled by default, I guess I'm willing to take the risk. A very big thank you to everyone that helped me. = - Paul Burkett __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux Sound Issues
On Sat, Nov 29, 2003 at 04:37:08PM -0800, Paul Burkett wrote: snip Could it be ext3 is just a lot slower than ext2 and can't handle it? Is there anything I can do to tweak this? Or should I move onto XFS or ResierFS? Should I buy a new sound card? Should I try ALSA? Any suggestions would be helpful. Thanks again guys and gals. System Info: snip *more* than adequate hardware I use alsa with an SB live value (5.1), also on ext3, and I don't have this problem... I get a hiccup or two during an apt[-get|itude] install, but not much else will make it skip. So you might want to try alsa... OR It might be your HD settings... check hdparm, and make sure that uhh... DMA (I think that's the parameter) is enabled. Your hardware is twice as fast as mine, twice as much RAM, so it may be the ALSA difference (no idea how likely that is) or it may be that something's hitting your HD performance pretty hard... But it's definitely not a question of needing more processor, RAM, or sound card. Cheers! -- ,-. -ScruLoose- | I don't want to start any blasphemous rumours Please |but I think that God's got a sick sense of humour do not Cc me. | - Depeche Mode `-' pgp0.pgp Description: PGP signature
Re: Linux Sound Issues
Paul Burkett wrote: I've been having a helluva time to get sound working decently in Linux. The issue isn't so much quality (though I do notice a slight difference in quality compared to Windows, nothing to complain about) but that fact that is skips whenever I do anything that requires CPU resources. I've tried recompiling the kernel to make it more efficient and I've tried using the latest drivers from Creative. It doesn't skip as much but there are times when it does skip when playing an mp3. Usually it happens when I'm running any apt tools. Now I don't know if it is so much the fault of the CPU (an AMD Tbird 1GHz) or the soundcard (a POS SB Live), but I do notice kjournald running in the background when I check it out using top. Could it be ext3 is just a lot slower than ext2 and can't handle it? Is there anything I can do to tweak this? Or should I move onto XFS or ResierFS? Should I buy a new sound card? Should I try ALSA? Any suggestions would be helpful. Thanks again guys and gals. System Info: AMD 1GHz Thunderbird 512MB of RAM Running KDE Ext3 Filesystem Kernel 2.4.22 compiled for i686 Debian Unstable 40GB Maxtor 740DX HDD Dedicated to Linux SB Live! Sound Card (OEM) Via686B Chipset (Abit KT7A-RAID MB) AFAIK I didn't have this problem in Mandrake 8 but that was so long ago. Hi, Paul I also have the same card, 1.3Ghz processor and ATA 100 disk and it does eventually hik up now and then... I'm ussing the OSS drivers. I think we have to fidlle with the priorities of the prog. processing sound. I use noatun. Still didn't have time to think about this subject but I think I'll give it a try. I'll post if anything comes out of this ... John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux Sound Issues
El sábado, 29 de noviembre de 2003, a las 16:37, Paul Burkett escribió: Should I buy a new sound card? Should I try ALSA? Any suggestions Yes, you should try ALSA. You also can try recompiling your kernel including one (or both) low latency patches. As you are running unstable, you can easily do this using make-kpkg, as the patches are packaged. $ apt-cache show kernel-patch-2.4-lowlatency kernel-patch-2.4-preempt Regards, Ismael -- `Tout fourmille de commentaries; d'autheurs il en est grande cherté.' signature.asc Description: Digital signature
Re: Linux Sound Issues
Paul Burkett wrote: I've been having a helluva time to get sound working decently in Linux. The issue isn't so much quality (though I do notice a slight difference in quality compared to Windows, nothing to complain about) but that fact that is skips whenever I do anything that requires CPU resources. I may be way off, of course, but I ran into this problem and it had nothing to do with sound but with the fact that did not have VIA82CXXX enabled under IDE, ATA and ATAPI Block Devices. Result was that with any disk access the disk would hang for seconds and the sound would stop. You might look into that too... Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Linux Sound Issues
I've been having a helluva time to get sound working decently in Linux. The issue isn't so much quality (though I do notice a slight difference in quality compared to Windows, nothing to complain about) but that fact that is skips whenever I do anything that requires CPU resources. I've tried recompiling the kernel to make it more efficient and I've tried using the latest drivers from Creative. It doesn't skip as much but there are times when it does skip when playing an mp3. Usually it happens when I'm running any apt tools. Now I don't know if it is so much the fault of the CPU (an AMD Tbird 1GHz) or the soundcard (a POS SB Live), but I do notice kjournald running in the background when I check it out using top. Could it be ext3 is just a lot slower than ext2 and can't handle it? Is there anything I can do to tweak this? Or should I move onto XFS or ResierFS? Should I buy a new sound card? Should I try ALSA? Any suggestions would be helpful. Thanks again guys and gals. System Info: AMD 1GHz Thunderbird 512MB of RAM Running KDE Ext3 Filesystem Kernel 2.4.22 compiled for i686 Debian Unstable 40GB Maxtor 740DX HDD Dedicated to Linux SB Live! Sound Card (OEM) Via686B Chipset (Abit KT7A-RAID MB) AFAIK I didn't have this problem in Mandrake 8 but that was so long ago. = - Paul Burkett __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Alsa sound for d4x, ut2003_demo ... sound issues again
Yes I've been able to get my sound running well using xmms, but now it seems unreal tournament doesn't seem to work and downloader for x (it's sounds) doesn't play it's usual wavs. Here's the error for unreal: Valhalla:/home/elijah# ut2003_demo ioctl SETFRAGMENT grab: Invalid argument ut2003-bin: al_mixer.c:704: _alSetMixer: Assertion `mixbuf.data' failed. Backtrace: [ 1] ./Core.so [0x409cf692] [ 2] /lib/libpthread.so.0 [0x40d6da44] [ 3] /lib/libc.so.6 [0x40b54518] [ 4] /lib/libc.so.6(abort+0xd1) [0x40b558d1] [ 5] /lib/libc.so.6 [0x40b4edb2] [ 6] ./openal.so(_alSetMixer+0x209) [0x438c6389] [ 7] ./openal.so [0x438db2f8] [ 8] ./openal.so(alcMakeContextCurrent+0x153) [0x438da2f7] [ 9] /usr/local/games/ut2003_demo/System/ALAudio.so(Init__17UALAudioSubsystem+0x168) [0x438a266c] [10] ./Engine.so(InitAudio__7UEngine+0x8b) [0x4024b9e7] [11] ./Engine.so(Init__11UGameEngine+0xf35) [0x4025a955] [12] ./ut2003-bin [0x80550ce] [13] ./ut2003-bin(main+0x296e) [0x80580ce] [14] /lib/libc.so.6(__libc_start_main+0xbb) [0x40b440bf] [15] ./ut2003-bin(GetFullName__C7UObjectPw+0x71) [0x80511b1] Signal: SIGIOT [iot trap] Aborting. xmms and mplayer works fine (although mplayer plays too fast!) through alsa though ... Can anyone please help? Elijah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alsa sound for d4x, ut2003_demo ... sound issues again [NEVERMIND ... ]
sigh sound is gone again after reboot, it seems amixer is not being created in /dev/ somehow also snd-via82xx.o cannot be detected but it's already there!! ... this is getting on my nerves now .. never mind this question. :( oh, well .. Elijah On Sun, 2003-01-12 at 18:39, Elijah wrote: Yes I've been able to get my sound running well using xmms, but now it seems unreal tournament doesn't seem to work and downloader for x (it's sounds) doesn't play it's usual wavs. Here's the error for unreal: Valhalla:/home/elijah# ut2003_demo ioctl SETFRAGMENT grab: Invalid argument ut2003-bin: al_mixer.c:704: _alSetMixer: Assertion `mixbuf.data' failed. Backtrace: [ 1] ./Core.so [0x409cf692] [ 2] /lib/libpthread.so.0 [0x40d6da44] [ 3] /lib/libc.so.6 [0x40b54518] [ 4] /lib/libc.so.6(abort+0xd1) [0x40b558d1] [ 5] /lib/libc.so.6 [0x40b4edb2] [ 6] ./openal.so(_alSetMixer+0x209) [0x438c6389] [ 7] ./openal.so [0x438db2f8] [ 8] ./openal.so(alcMakeContextCurrent+0x153) [0x438da2f7] [ 9] /usr/local/games/ut2003_demo/System/ALAudio.so(Init__17UALAudioSubsystem+0x168) [0x438a266c] [10] ./Engine.so(InitAudio__7UEngine+0x8b) [0x4024b9e7] [11] ./Engine.so(Init__11UGameEngine+0xf35) [0x4025a955] [12] ./ut2003-bin [0x80550ce] [13] ./ut2003-bin(main+0x296e) [0x80580ce] [14] /lib/libc.so.6(__libc_start_main+0xbb) [0x40b440bf] [15] ./ut2003-bin(GetFullName__C7UObjectPw+0x71) [0x80511b1] Signal: SIGIOT [iot trap] Aborting. xmms and mplayer works fine (although mplayer plays too fast!) through alsa though ... Can anyone please help? Elijah -- 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]
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
lsmod question (was....Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1)
A side question if you don't mind. It is my understanding that people use modules to make a lighter/smaller kernel. Is that correct? Other reasons? I have compiled kernels 30 times or so and most of the time I have no modules loaded. (maybe because I am clueless?) Are modules supposed to load automatically? For example, if I don't know my sound card on my laptop, and I load every sound module when doing xconfig, and then upon first boot, does linux simply see what card I have and then load appropriate module? (never works for meagain clueless...) You will see below he has smbfs as a module. When I put the samba file system into my kernel as a module, and I run lsmod, there is nothing there. Does it get loaded if I try to mount a samba server? Confused... 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lsmod question (was....Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1)
Andy said: A side question if you don't mind. It is my understanding that people use modules to make a lighter/smaller kernel. Is that correct? Other reasons? some things cannot be compiled into the kernel, or cannot be easily compiled into the kernel. examples are nvidia drivers, vmware drivers, lm_sensors, and more .. sometimes it is useful to be able to unload a driver perhaps to try to reset a device, or free up memory or something. also it provides limited functionality to do a hot upgrade on modules since the code can be removed and re-inserted(though due to many kernel things the usefulness of this in my experience is quite limited at the present time). I have compiled kernels 30 times or so and most of the time I have no modules loaded. (maybe because I am clueless?) no, it just means you probably don't need any modules loaded, or you don't need the functionality that modules provide. I am the same way. If it can be compiled into the kernel it will be on my systems. Which makes me sad to see that future linux kernels will be module-only. static kernels also make for easier moving kernels between machines since its just 1 file. this has helped me in the past. Are modules supposed to load automatically? they can be, the kernel module autoloader is designed to try to automatically load any modules it thinks you may need, I personally do not like this feature and turn it off on all my kernels. For example, if I don't know my sound card on my laptop, and I load every sound module when doing xconfig, and then upon first boot, does linux simply see what card I have and then load appropriate module? in the case of a soundcard, probably not. but in the case of something like a USB device, a filesystem driver, a networking driver etc, the kernel module loader can try to load the driver for you. Since I build my own kernels, and know what hardware I have(plan to use) I disable this feature so my logs don't start filling up with messages from the kernel saying it can't find XX module that it thinks I need. You will see below he has smbfs as a module. When I put the samba file system into my kernel as a module, and I run lsmod, there is nothing there. Does it get loaded if I try to mount a samba server? if you built it directly into the kernel instead of module it will be there, it loads when the kernel does, you can cat /proc/filesystems to see what filesystems are supported by the drivers you have loaded. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
OT:Re: lsmod question (was....Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1)
--- nate [EMAIL PROTECTED] wrote: -snip If it can be compiled into the kernel it will be on my systems. Which makes me sad to see that future linux kernels will be module-only. snip I thought that Linus was quoted as saying that the function of the kernel should not be to pass messages to modules. That it should interact directly with hardware. (obviously I am not quoting here). ie. the kernel _should_ be monolithic. Why are they going to module-only kernels? Can you point me to an article on this? Shawn = 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: OT:Re: lsmod question (was....Sound issues using 2.4.18-bf2.4-xfs and SB Live! 5.1)
Shawn Lamson said: I thought that Linus was quoted as saying that the function of the kernel should not be to pass messages to modules. That it should interact directly with hardware. (obviously I am not quoting here). ie. the kernel _should_ be monolithic. Why are they going to module-only kernels? Can you point me to an article on this? i'll try to dig it up tomorrow. I don't know if it was set in stone but I belive I read it in kernel traffic a few months ago. i've been searching on google for about 15 minutes and can't find the reference to it. hopefully i'm wrong but it really sticks out in my head so i'm almost certain I read it. it wasn't a full thread from what I remember, just a passing reference that future kernels(or the next kernel) would be all modules, I'm still lookin, but searching for words like 'linus kernel module only' comes up with a zillion results. I either read it on kernel traffic, or lwn.net's kernel section not too long ago(2-3 months tops I think). still looking nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]