Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
wiki:troubleshooting_exclusive_sound_card_access [2009/09/20 12:32] – created raboofwiki:troubleshooting_exclusive_sound_card_access [2009/09/20 12:42] – Some distributions start [[apps:all:timidity]] on startup raboof
Line 1: Line 1:
 If some application accesses the sound card though one of the lower audio layers (see [[audio layers overview]]), the sound card might become inaccessible and other applications might fail to open the sound card, or even hang. If some application accesses the sound card though one of the lower audio layers (see [[audio layers overview]]), the sound card might become inaccessible and other applications might fail to open the sound card, or even hang.
 +
 +===== Finding out which application is holding your sound card =====
  
 ==== OSS ==== ==== OSS ====
Line 5: Line 7:
 You can see which applications are using OSS (or the ALSA OSS Emulation layer) with: You can see which applications are using OSS (or the ALSA OSS Emulation layer) with:
  
-<pre> +  $ sudo fuser /dev/dsp*
-$ sudo fuser /dev/dsp* +
-</pre>+
  
 ==== ALSA ==== ==== ALSA ====
Line 13: Line 13:
 You can see which applications are using ALSA with: You can see which applications are using ALSA with:
  
-<pre> +  $ sudo fuser /dev/snd/pcm*  
-$ sudo fuser /dev/snd/pcm*  + 
-</pre>+===== Stopping that application ===== 
 + 
 +In most cases you can simply close or kill the application that is using your sound card. 
 + 
 +==== PulseAudio ==== 
 + 
 +If [[apps:all:PulseAudio]] is holding your sound card, you can stop it with 'pulseaudio -k'. 
 + 
 +==== TiMiDity++ ==== 
 + 
 +Some distributions start [[apps:all:timidity]] on startup. It can generally be stopped with 'sudo /etc/init.d/timidity stop' 
  
wiki/troubleshooting_exclusive_sound_card_access.txt · Last modified: 2013/06/02 15:45 by 127.0.0.1