Difference between revisions of "PulseAudio"

From ArchWiki
Jump to: navigation, search
m (Change PKG to package.)
m (Style)
Line 16: Line 16:
 
{{Article summary end}}
 
{{Article summary end}}
  
==Installation==
+
== Installation ==
*Required package:  {{Pkg|pulseaudio}}
+
*Optional GTK GUIs: {{Pkg|paprefs}} and {{Pkg|pavucontrol}}
+
*Optional volume control via mapped keyboard keys: {{AUR|pulseaudio_ctl}}
+
*Optional console mixer: {{AUR|ponymix-git}} and {{AUR|pamixer-git}}
+
*Optional system tray icon: {{AUR|pasystray-git}}
+
*Optional KDE plasma applet: {{Pkg|kdemultimedia-kmix}} and {{AUR|kdeplasma-applets-veromix}}
+
  
==Running==
+
* Required package:  {{Pkg|pulseaudio}}
{{Note|Pulseaudio requires [[D-Bus]] to function.}}
+
* Optional GTK GUIs: {{Pkg|paprefs}} and {{Pkg|pavucontrol}}
{{Note|Most X11 environments start pulseaudio automatically with the X11 session.}}
+
* Optional volume control via mapped keyboard keys: {{AUR|pulseaudio_ctl}}
 +
* Optional console mixer: {{AUR|ponymix-git}} and {{AUR|pamixer-git}}
 +
* Optional system tray icon: {{AUR|pasystray-git}}
 +
* Optional KDE plasma applet: {{Pkg|kdemultimedia-kmix}} and {{AUR|kdeplasma-applets-veromix}}
 +
 
 +
== Running ==
 +
 
 +
{{Note|
 +
* Pulseaudio requires [[D-Bus]] to function.
 +
* Most X11 environments start pulseaudio automatically with the X11 session.
 +
}}
  
 
In the unlikely event that pulseaudio is not automatically called upon entering X, it can can be started with:
 
In the unlikely event that pulseaudio is not automatically called upon entering X, it can can be started with:
Line 34: Line 38:
 
  $ pulseaudio -k
 
  $ pulseaudio -k
  
==Equalizer==
+
== Equalizer ==
  
 
Newer pulseaudio versions have an intergrated 10-band equalizer system. In order to use the equalizer do the following:
 
Newer pulseaudio versions have an intergrated 10-band equalizer system. In order to use the equalizer do the following:
  
===Load equalizer sink module===
+
=== Load equalizer sink module ===
  
 
  $ pactl load-module module-equalizer-sink
 
  $ pactl load-module module-equalizer-sink
  
===Install and run the gui frontend===
+
=== Install and run the gui frontend ===
  
# pacman -S --needed python2-pyqt
+
Install {{Pkg|python2-pyqt}} and execute:
  
 
  $ qpaeq
 
  $ qpaeq
Line 50: Line 54:
 
{{Note|If qpaeq has no effect, install pavucontrol and change "ALSA Playback on" to "FFT based equalizer on ..." while the media player is running.}}
 
{{Note|If qpaeq has no effect, install pavucontrol and change "ALSA Playback on" to "FFT based equalizer on ..." while the media player is running.}}
  
===Load equalizer module on every boot===
+
=== Load equalizer module on every boot ===
  
 
Edit the file {{ic|/etc/pulse/default.pa}} with your favorite editor and append the following lines:
 
Edit the file {{ic|/etc/pulse/default.pa}} with your favorite editor and append the following lines:
Line 57: Line 61:
 
  load-module module-equalizer-sink
 
  load-module module-equalizer-sink
  
==Backend Configuration==
+
== Backend Configuration ==
  
===ALSA===
+
=== ALSA ===
*Recommended package: {{Pkg|pulseaudio-alsa}}
+
 
*Optional packages: {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}}
+
* Recommended package: {{Pkg|pulseaudio-alsa}}
 +
* Optional packages: {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}}
  
 
{{Note|Optional packages are needed only if running x86_64 and wanting to have sound for 32 bit programs (like Wine).}}
 
{{Note|Optional packages are needed only if running x86_64 and wanting to have sound for 32 bit programs (like Wine).}}
Line 70: Line 75:
 
  # rmmod snd_pcm_oss
 
  # rmmod snd_pcm_oss
  
===ALSA/dmix without grabbing hardware device===
+
=== ALSA/dmix without grabbing hardware device ===
{{Note|This section describes alternative configuration, which is generally NOT recommended.}}
+
 
 +
{{Note|This section describes alternative configuration, which is generally '''not''' recommended.}}
  
 
You may want to use ALSA directly in most of your applications and to be able to use other applications, which constantly require PulseAudio at the same time. The following steps allow you to make PulseAudio use dmix instead of grabbing ALSA hardware device.
 
You may want to use ALSA directly in most of your applications and to be able to use other applications, which constantly require PulseAudio at the same time. The following steps allow you to make PulseAudio use dmix instead of grabbing ALSA hardware device.
  
*Remove package {{Pkg|pulseaudio-alsa}}, which provides compatibility layer between ALSA applications and PulseAudio. After this your ALSA apps will use ALSA directly without being hooked by Pulse.
+
* Remove package {{Pkg|pulseaudio-alsa}}, which provides compatibility layer between ALSA applications and PulseAudio. After this your ALSA apps will use ALSA directly without being hooked by Pulse.
$ sudo pacman -R pulseaudio-alsa
+
  
*Edit {{ic|/etc/pulse/default.pa}}.
+
* Edit {{ic|/etc/pulse/default.pa}}.
 
:Find and uncomment lines which load backend drivers. Add '''device''' parameters as follows. Then find and comment lines which load autodetect modules.
 
:Find and uncomment lines which load backend drivers. Add '''device''' parameters as follows. Then find and comment lines which load autodetect modules.
 
  load-module module-alsa-sink '''device=dmix'''
 
  load-module module-alsa-sink '''device=dmix'''
Line 85: Line 90:
 
  # load-module module-detect
 
  # load-module module-detect
  
*''Optional:'' If you use {{Pkg|kdemultimedia-kmix}} you may want to control ALSA volume instead of PulseAudio volume:
+
* ''Optional:'' If you use {{Pkg|kdemultimedia-kmix}} you may want to control ALSA volume instead of PulseAudio volume:
 
  $ echo export KMIX_PULSEAUDIO_DISABLE=1 > ~/.kde4/env/kmix_disable_pulse.sh
 
  $ echo export KMIX_PULSEAUDIO_DISABLE=1 > ~/.kde4/env/kmix_disable_pulse.sh
 
  $ chmod +x ~/.kde4/env/kmix_disable_pulse.sh
 
  $ chmod +x ~/.kde4/env/kmix_disable_pulse.sh
  
*Now, reboot your computer and try running alsa and pulseaudio applications at the same time. They both should produce sound simultaneously.
+
* Now, reboot your computer and try running alsa and pulseaudio applications at the same time. They both should produce sound simultaneously.
 
:Use {{Pkg|pavucontrol}} to control PulseAudio volume if needed.
 
:Use {{Pkg|pavucontrol}} to control PulseAudio volume if needed.
  
===OSS===
+
=== OSS ===
 +
 
 
There are multiple ways of making OSS-only programs play to PulseAudio:
 
There are multiple ways of making OSS-only programs play to PulseAudio:
  
====ossp====
+
==== ossp ====
Start {{Pkg|ossp}} with:
+
 
# systemctl start osspd
+
Install {{Pkg|ossp}} package and start '''ossp''' service.
 +
 
 +
==== padsp wrapper (part of PulseAudio) ====
  
====padsp wrapper (part of PulseAudio)====
 
 
Programs using OSS can work with PulseAudio by starting it with padsp:
 
Programs using OSS can work with PulseAudio by starting it with padsp:
  
Line 114: Line 121:
 
Make sure {{ic|/usr/local/bin}} comes before {{ic|/usr/bin}} in your '''PATH'''.
 
Make sure {{ic|/usr/local/bin}} comes before {{ic|/usr/bin}} in your '''PATH'''.
  
===GStreamer===
+
=== GStreamer ===
 +
 
 
To make [[GStreamer]] use PulseAudio, you need to install {{Pkg|gst-plugins-good}} or {{Pkg|gstreamer0.10-good-plugins}}.
 
To make [[GStreamer]] use PulseAudio, you need to install {{Pkg|gst-plugins-good}} or {{Pkg|gstreamer0.10-good-plugins}}.
  
===OpenAL===
+
=== OpenAL ===
 +
 
 
OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so: {{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}
 
OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so: {{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}
  
===libao===
+
=== libao ===
 +
 
 
Edit the libao configuration file:
 
Edit the libao configuration file:
 
{{hc|/etc/libao.conf|2=default_driver=pulse}}
 
{{hc|/etc/libao.conf|2=default_driver=pulse}}
 
Be sure to remove the {{ic|1=dev=default}} option of the alsa driver or adjust it to specify a specific Pulse sink name or number. Alternatively, note that you could keep the libao standard of outputting to the ''alsa'' driver and its default device if you install {{Pkg|pulseaudio-alsa}} since the ALSA default device then '''is''' PulseAudio.
 
Be sure to remove the {{ic|1=dev=default}} option of the alsa driver or adjust it to specify a specific Pulse sink name or number. Alternatively, note that you could keep the libao standard of outputting to the ''alsa'' driver and its default device if you install {{Pkg|pulseaudio-alsa}} since the ALSA default device then '''is''' PulseAudio.
 
   
 
   
===ESD===
+
=== ESD ===
 +
 
 
PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.
 
PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.
  
==Desktop Environments==
+
== Desktop environments ==
===General X11===
+
 
 +
=== General X11 ===
 +
 
 
{{Note|As mentioned previously, PulseAudio is very likely launched automatically via either {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} or the files in {{ic|/etc/xdg/autostart/}} if users have some DE installed.}}
 
{{Note|As mentioned previously, PulseAudio is very likely launched automatically via either {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} or the files in {{ic|/etc/xdg/autostart/}} if users have some DE installed.}}
  
 
Check to see if PulseAudio is running:
 
Check to see if PulseAudio is running:
  
$ ps aux | grep pulse
+
{{hc|<nowiki>$ ps aux | grep pulse</nowiki>|
 
  facade  1794  0.0  0.0 360464  6532 ?        S<l  15:33  0:00 /usr/bin/pulseaudio --start
 
  facade  1794  0.0  0.0 360464  6532 ?        S<l  15:33  0:00 /usr/bin/pulseaudio --start
 
  facade  1827  0.0  0.0  68888  2608 ?        S    15:33  0:00 /usr/lib/pulse/gconf-helper
 
  facade  1827  0.0  0.0  68888  2608 ?        S    15:33  0:00 /usr/lib/pulse/gconf-helper
 +
}}
  
 
If Pulseaudio is not running and users are using X, the following will start PulseAudio with the needed the X11 plugins manually:
 
If Pulseaudio is not running and users are using X, the following will start PulseAudio with the needed the X11 plugins manually:
Line 146: Line 160:
 
}}
 
}}
  
===GNOME===
+
=== GNOME ===
 +
 
 
As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.
 
As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.
  
===KDE 3===
+
=== KDE 3 ===
 +
 
 
PulseAudio is ''not'' a drop-in replacement for aRts. Users of KDE 3 cannot use PulseAudio. However note, recent versions of PulseAudio may have eliminated the prohibition:
 
PulseAudio is ''not'' a drop-in replacement for aRts. Users of KDE 3 cannot use PulseAudio. However note, recent versions of PulseAudio may have eliminated the prohibition:
  
Line 159: Line 175:
 
  SuspendTime=1
 
  SuspendTime=1
  
===KDE Plasma Workspaces and Qt4===
+
=== KDE Plasma Workspaces and Qt4 ===
 +
 
 
PulseAudio, it will be used by KDE/Qt4 applications. For more information see the [http://www.pulseaudio.org/wiki/KDE KDE page in the PulseAudio wiki].
 
PulseAudio, it will be used by KDE/Qt4 applications. For more information see the [http://www.pulseaudio.org/wiki/KDE KDE page in the PulseAudio wiki].
  
Line 170: Line 187:
 
Additionally, the {{AUR|kdeplasma-applets-veromix}} is available in the [[AUR]] as a KDE alternative to KMix or pavucontrol.
 
Additionally, the {{AUR|kdeplasma-applets-veromix}} is available in the [[AUR]] as a KDE alternative to KMix or pavucontrol.
  
===Xfce===
+
=== Xfce ===
 +
 
 
Applications running under Xfce can take advantage of PulseAudio. To manage PulseAudio settings you can use {{Pkg|pavucontrol}}.
 
Applications running under Xfce can take advantage of PulseAudio. To manage PulseAudio settings you can use {{Pkg|pavucontrol}}.
  
==Applications==
+
== Applications ==
===Audacious===
+
 
 +
=== Audacious ===
 +
 
 
[[Audacious]] natively supports PulseAudio. In order to use it, set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.
 
[[Audacious]] natively supports PulseAudio. In order to use it, set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.
  
===Java/OpenJDK 6===
+
=== Java/OpenJDK 6 ===
 +
 
 
Create a wrapper for the java executable using padsp as seen on the [[Java#Java_sound_with_Pulseaudio|Java sound with Pulseaudio]] page.
 
Create a wrapper for the java executable using padsp as seen on the [[Java#Java_sound_with_Pulseaudio|Java sound with Pulseaudio]] page.
  
===Music Player Daemon (MPD)===
+
=== Music Player Daemon (MPD) ===
[http://mpd.wikia.com/wiki/PulseAudio configure] [[MPD]] to use PulseAudio. See also [[MPD/Tips_and_Tricks#MPD_.26_PulseAudio]].
+
 
 +
[http://mpd.wikia.com/wiki/PulseAudio configure] [[MPD]] to use PulseAudio. See also [[MPD/Tips_and_tricks#MPD_.26_PulseAudio]].
 +
 
 +
=== MPlayer ===
  
===MPlayer===
 
 
[[MPlayer]] natively supports PulseAudio output with the "{{ic|-ao pulse}}" option. It can also be configured to default to PulseAudio output, in {{ic|~/.mplayer/config}} for per-user, or {{ic|/etc/mplayer/mplayer.conf}} for system-wide:
 
[[MPlayer]] natively supports PulseAudio output with the "{{ic|-ao pulse}}" option. It can also be configured to default to PulseAudio output, in {{ic|~/.mplayer/config}} for per-user, or {{ic|/etc/mplayer/mplayer.conf}} for system-wide:
 
{{hc|/etc/mplayer/mplayer.conf|2=ao=pulse}}
 
{{hc|/etc/mplayer/mplayer.conf|2=ao=pulse}}
  
===Skype (x86_64 only)===
+
=== Skype (x86_64 only) ===
 +
 
 
Install {{Pkg|lib32-libpulse}}, otherwise the following error will occur when trying to initiate a call: "Problem with Audio Playback".
 
Install {{Pkg|lib32-libpulse}}, otherwise the following error will occur when trying to initiate a call: "Problem with Audio Playback".
  
==Troubleshooting==
+
== Troubleshooting ==
===No sound after install===
+
  
====Muted audio device====
+
=== No sound after install ===
If one experiences no audio output via any means while using ALSA, attempt to unmute the sound card.  To do this, launch {{ic|alsamixer}} and make sure each column has a green 00 under it (this can be toggled by pressing {{keypress|m}}):
+
 
 +
==== Muted audio device ====
 +
 
 +
If one experiences no audio output via any means while using ALSA, attempt to unmute the sound card.  To do this, launch {{ic|alsamixer}} and make sure each column has a green 00 under it (this can be toggled by pressing {{Keypress|m}}):
 
  $ alsamixer -c 0
 
  $ alsamixer -c 0
  
====Bad configuration files====
+
==== Bad configuration files ====
 +
 
 
If after starting pulseaudio, the system outputs no sound, it may be necessary to delete the contents of {{ic|~/.pulse}}. Pulseaudio will automatically create new configuration files on its next start.
 
If after starting pulseaudio, the system outputs no sound, it may be necessary to delete the contents of {{ic|~/.pulse}}. Pulseaudio will automatically create new configuration files on its next start.
  
====Flash Content====
+
==== Flash content ====
 +
 
 
Since Adobe Flash does not directly support PulseAudio the recommended way is to [https://wiki.archlinux.org/index.php/PulseAudio#ALSA configure ALSA to use the virtual PulseAudio soundcard].
 
Since Adobe Flash does not directly support PulseAudio the recommended way is to [https://wiki.archlinux.org/index.php/PulseAudio#ALSA configure ALSA to use the virtual PulseAudio soundcard].
  
Line 206: Line 234:
 
{{Note|This may invariably crash the flash plugin.}}
 
{{Note|This may invariably crash the flash plugin.}}
  
====No cards====
+
==== No cards ====
 +
 
 
If PulseAudio starts, run {{ic|pacmd list}}. If no cards are reported, make sure that the ALSA devices are not in use:
 
If PulseAudio starts, run {{ic|pacmd list}}. If no cards are reported, make sure that the ALSA devices are not in use:
 
  $ fuser -v /dev/snd/*
 
  $ fuser -v /dev/snd/*
Line 213: Line 242:
 
Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.
 
Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.
  
====The only device shown is "dummy output"====
+
==== The only device shown is "dummy output" ====
 +
 
 
This may be caused by different reasons, one of them being the {{ic|.asoundrc}} file in $HOME is taking precedence over the systemwide {{ic|/etc/asound.conf}}.
 
This may be caused by different reasons, one of them being the {{ic|.asoundrc}} file in $HOME is taking precedence over the systemwide {{ic|/etc/asound.conf}}.
  
 
The user file is modified also by the tool {{ic|asoundconf}} or by its graphical variant {{ic|asoundconf-gtk}} (the latter is named "Default sound card" in the menu) as soon as it  runs.  Prevent the effects of {{ic|.asoundrc}} altogether by commenting the last line like this:
 
The user file is modified also by the tool {{ic|asoundconf}} or by its graphical variant {{ic|asoundconf-gtk}} (the latter is named "Default sound card" in the menu) as soon as it  runs.  Prevent the effects of {{ic|.asoundrc}} altogether by commenting the last line like this:
 
{{hc|.asoundrc|
 
{{hc|.asoundrc|
# </home/<yourusername>/.asoundrc.asoundconf>
+
# </home/''yourusername''/.asoundrc.asoundconf>
 
}}
 
}}
  
Line 239: Line 269:
 
  # pacman -Rnsc fluidsynth
 
  # pacman -Rnsc fluidsynth
  
====KDE4====
+
==== KDE4 ====
 +
 
 
It may be that another output device set as preferred in phonon. Make sure that every setting reflects the preferred output device at the top, and check the playback streams tab in {{ic|kmix}} to make sure that applications are using the device for output.
 
It may be that another output device set as preferred in phonon. Make sure that every setting reflects the preferred output device at the top, and check the playback streams tab in {{ic|kmix}} to make sure that applications are using the device for output.
  
====Failed to create sink input: sink is suspended====
+
==== Failed to create sink input: sink is suspended ====
 +
 
 
If you do not have any output sound and receive dozens of errors related to a suspended sink in your {{ic|journalctl -b}} log, then backup first and then delete your user-specific pulse folders:
 
If you do not have any output sound and receive dozens of errors related to a suspended sink in your {{ic|journalctl -b}} log, then backup first and then delete your user-specific pulse folders:
  
 
  $ rm -r ~/.pulse ~/.pulse-cookie
 
  $ rm -r ~/.pulse ~/.pulse-cookie
  
===Bluetooth headset replay problems===
+
=== Bluetooth headset replay problems ===
 +
 
 
Some user [https://bbs.archlinux.org/viewtopic.php?id=117420 report] huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated.  
 
Some user [https://bbs.archlinux.org/viewtopic.php?id=117420 report] huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated.  
  
Line 260: Line 293:
 
[http://robert.orzanna.de/2011/08/prevent-idle-suspend-with-bluetooth.html More information]
 
[http://robert.orzanna.de/2011/08/prevent-idle-suspend-with-bluetooth.html More information]
  
===Automatically switch to Bluetooth or USB headset===
+
=== Automatically switch to Bluetooth or USB headset ===
 +
 
 
Add the following:
 
Add the following:
 
{{hc|/etc/pulse/default.pa|
 
{{hc|/etc/pulse/default.pa|
Line 267: Line 301:
 
}}
 
}}
  
===Pulse overwrites ALSA settings===
+
=== Pulse overwrites ALSA settings ===
 +
 
 
Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to {{ic|.xinitrc}} or {{ic|.bash_profile}} or any other [[Autostarting|autostart]] file:
 
Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to {{ic|.xinitrc}} or {{ic|.bash_profile}} or any other [[Autostarting|autostart]] file:
  
 
  restore_alsa() {
 
  restore_alsa() {
   while [ -z "`pidof pulseaudio`" ]; do
+
   while [ -z "$(pidof pulseaudio)" ]; do
 
   sleep 0.5
 
   sleep 0.5
 
   done
 
   done
Line 278: Line 313:
 
  restore_alsa &
 
  restore_alsa &
  
===Prevent Pulse from restarting after being killed===
+
=== Prevent Pulse from restarting after being killed ===
 +
 
 
Sometimes you may wish to temporarily disable Pulse. In order to do so you will have to prevent Pulse from restarting after being killed.
 
Sometimes you may wish to temporarily disable Pulse. In order to do so you will have to prevent Pulse from restarting after being killed.
  
 
  $ echo autospawn=no > ~/.pulse/client.conf
 
  $ echo autospawn=no > ~/.pulse/client.conf
  
===Daemon startup failed===
+
=== Daemon startup failed ===
 +
 
 
Try resetting PulseAudio:
 
Try resetting PulseAudio:
 
  $ rm -rf /tmp/pulse* ~/.pulse*
 
  $ rm -rf /tmp/pulse* ~/.pulse*
Line 291: Line 328:
 
If there is no server running but pulseaudio fails to start with an error message "User-configured server at ... refusing to start/autospawn", the issue may be with PulseAudio settings from a previous login. Check to see if there are any stale properties attached to the X11 root window with {{ic|pax11publish -d}}, and if there are, remove them with {{ic|pax11publish -r}} before trying to start the server. This manual cleanup is always required when using LXDM because it does not restart the X server on logout; see [[LXDM#PulseAudio]].
 
If there is no server running but pulseaudio fails to start with an error message "User-configured server at ... refusing to start/autospawn", the issue may be with PulseAudio settings from a previous login. Check to see if there are any stale properties attached to the X11 root window with {{ic|pax11publish -d}}, and if there are, remove them with {{ic|pax11publish -r}} before trying to start the server. This manual cleanup is always required when using LXDM because it does not restart the X server on logout; see [[LXDM#PulseAudio]].
  
====inotify issue====
+
==== inotify issue ====
 +
 
 
If the previous fix doesn't work, run the following:
 
If the previous fix doesn't work, run the following:
 
  $ pulseaudio -vvvv
 
  $ pulseaudio -vvvv
Line 308: Line 346:
 
  fs.inotify.max_user_watches = 100000
 
  fs.inotify.max_user_watches = 100000
  
===padevchooser===
+
=== padevchooser ===
If one cannot launch the PulseAudio Device Chooser, first (re)start the Avahi daemon as follows:
+
 
# systemctl restart avahi-daemon
+
If one cannot launch the PulseAudio Device Chooser, first restart the Avahi daemon ('''avahi-daemon''').
 +
 
 +
=== Glitches, skips or crackling ===
  
===Glitches, skips or crackling===
 
 
The newer implementation of PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach.  
 
The newer implementation of PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach.  
  
Line 330: Line 369:
 
Please report any such cards to [http://pulseaudio.org/wiki/BrokenSoundDrivers PulseAudio Broken Sound Driver page]
 
Please report any such cards to [http://pulseaudio.org/wiki/BrokenSoundDrivers PulseAudio Broken Sound Driver page]
  
===Setting the default fragment number and buffer size in Pulseaudio===
+
=== Setting the default fragment number and buffer size in Pulseaudio ===
  
 
[http://forums.linuxmint.com/viewtopic.php?f=42&t=44862 More Information]
 
[http://forums.linuxmint.com/viewtopic.php?f=42&t=44862 More Information]
  
====Finding out your audio device parameters (1/4)====
+
==== Finding out your audio device parameters (1/4) ====
  
 
To find your sound card buffering settings:
 
To find your sound card buffering settings:
Line 358: Line 397:
 
Take note the buffer_size and fragment_size values for the relevant sound card.
 
Take note the buffer_size and fragment_size values for the relevant sound card.
  
====Calculate your fragment size in msecs and number of fragments (2/4)====
+
==== Calculate your fragment size in msecs and number of fragments (2/4) ====
  
 
Pulseaudio's default sampling rate and bit depth are set to {{ic|44100Hz}} @ {{ic|16 bits}}.
 
Pulseaudio's default sampling rate and bit depth are set to {{ic|44100Hz}} @ {{ic|16 bits}}.
Line 369: Line 408:
 
  device.buffering.fragment_size = "384000" => 384000/1411200 = 0.272108843537s = 272 msecs
 
  device.buffering.fragment_size = "384000" => 384000/1411200 = 0.272108843537s = 272 msecs
  
====Modify Pulseaudio's configuration file (3/4)====
+
==== Modify Pulseaudio's configuration file (3/4) ====
  
 
{{hc|/etc/pulse/daemon.conf|<nowiki>
 
{{hc|/etc/pulse/daemon.conf|<nowiki>
Line 384: Line 423:
 
</nowiki>}}
 
</nowiki>}}
  
====Restart the Pulseaudio daemon (4/4)====
+
==== Restart the Pulseaudio daemon (4/4) ====
  
 
  $ pulseaudio -k
 
  $ pulseaudio -k
Line 391: Line 430:
 
For more information, see: [http://forums.linuxmint.com/viewtopic.php?f=42&t=44862 Linux Mint topic]
 
For more information, see: [http://forums.linuxmint.com/viewtopic.php?f=42&t=44862 Linux Mint topic]
  
===Laggy sound===
+
=== Laggy sound ===
 +
 
 
This issue is due to incorrect buffer sizes.
 
This issue is due to incorrect buffer sizes.
  
Line 400: Line 440:
 
</nowiki>}}
 
</nowiki>}}
  
===Choppy, overdriven sound===
+
=== Choppy, overdriven sound ===
 +
 
 
Choppy sound in pulsaudio can result from wrong settings for the sample rate. Try:
 
Choppy sound in pulsaudio can result from wrong settings for the sample rate. Try:
 
{{hc|/etc/pulse/daemon.conf|<nowiki>
 
{{hc|/etc/pulse/daemon.conf|<nowiki>
Line 412: Line 453:
 
Setting the PCM volume above 0dB can cause clipping of the audio signal.  Running {{ic|alsamixer -c0}} will allow you to see if this is the problem and if so fix it.
 
Setting the PCM volume above 0dB can cause clipping of the audio signal.  Running {{ic|alsamixer -c0}} will allow you to see if this is the problem and if so fix it.
  
===Volume adjustment does not work properly===
+
=== Volume adjustment does not work properly ===
 +
 
 
Check:
 
Check:
 
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common}}
 
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common}}
Line 418: Line 460:
 
If the volume does not appear to increment/decrement properly using {{ic|alsamixer}} or {{ic|amixer}}, it may be due to pulseaudio having a larger number of increments (65537 to be exact). Try using larger values when changing volume (e.g. {{ic|amixer set Master 655+}}).
 
If the volume does not appear to increment/decrement properly using {{ic|alsamixer}} or {{ic|amixer}}, it may be due to pulseaudio having a larger number of increments (65537 to be exact). Try using larger values when changing volume (e.g. {{ic|amixer set Master 655+}}).
  
===Volume gets louder every time a new application is started===
+
=== Volume gets louder every time a new application is started ===
 +
 
 
Per default, it seems as if changing the volume in an application sets the global system volume to that level instead of only affecting the respective application. Applications setting their volume on startup will therefore cause the system volume to "jump".
 
Per default, it seems as if changing the volume in an application sets the global system volume to that level instead of only affecting the respective application. Applications setting their volume on startup will therefore cause the system volume to "jump".
  
Line 430: Line 473:
 
When Pulse comes back after a few seconds, applications will not alter the global system volume anymore but have their own volume level again.
 
When Pulse comes back after a few seconds, applications will not alter the global system volume anymore but have their own volume level again.
  
{{Note|A previously installed and removed pulseaudio-equalizer may leave behind remnants of the setup in {{Ic|~/.pulse/default.pa}} which can also cause maximized volume trouble. Comment that out as needed.}}
+
{{Note|A previously installed and removed pulseaudio-equalizer may leave behind remnants of the setup in {{ic|~/.pulse/default.pa}} which can also cause maximized volume trouble. Comment that out as needed.}}
 +
 
 +
=== No mic on ThinkPad T400/T500/T420 ===
  
===No mic on ThinkPad T400/T500/T420===
 
 
Run:
 
Run:
 
  alsamixer -c 0
 
  alsamixer -c 0
Line 441: Line 485:
 
you might still need to adjust the settings. The microphone and the audio jack are duplexed. Set the configuration of the internal audio in pavucontrol to ''Analog Stereo Duplex''.
 
you might still need to adjust the settings. The microphone and the audio jack are duplexed. Set the configuration of the internal audio in pavucontrol to ''Analog Stereo Duplex''.
  
===No mic input on Acer Aspire One===
+
=== No mic input on Acer Aspire One ===
 +
 
 
Install pavucontrol, unlink the microphone channels and turn down the left one to 0.
 
Install pavucontrol, unlink the microphone channels and turn down the left one to 0.
 
Reference: http://getsatisfaction.com/jolicloud/topics/deaf_internal_mic_on_acer_aspire_one#reply_2108048
 
Reference: http://getsatisfaction.com/jolicloud/topics/deaf_internal_mic_on_acer_aspire_one#reply_2108048
  
===Sound output is only mono on M-Audio Audiophile 2496 sound card===
+
=== Sound output is only mono on M-Audio Audiophile 2496 sound card ===
 +
 
 
Add the following:
 
Add the following:
 
{{hc|/etc/pulseaudio/default.pa|<nowiki>
 
{{hc|/etc/pulseaudio/default.pa|<nowiki>
Line 454: Line 500:
 
</nowiki>}}
 
</nowiki>}}
  
===Static Noise in Microphone Recording===
+
=== Static noise in microphone recording ===
 +
 
 
If we are getting static noise in skype, gnome-sound-recorder, arecord, etc.'s recordings then the sound card samplerate is incorrect. That is why there is static noise in linux microphone recordings. To fix this We need to set sample-rate in {{ic|/etc/pulse/daemon.conf}} for the sound hardware.
 
If we are getting static noise in skype, gnome-sound-recorder, arecord, etc.'s recordings then the sound card samplerate is incorrect. That is why there is static noise in linux microphone recordings. To fix this We need to set sample-rate in {{ic|/etc/pulse/daemon.conf}} for the sound hardware.
  
====Determine soundcards in the system (1/5)====
+
==== Determine soundcards in the system (1/5) ====
 +
 
 
This requires alsa-utils and related packages to be installed:
 
This requires alsa-utils and related packages to be installed:
 
{{hc|$  arecord --list-devices|
 
{{hc|$  arecord --list-devices|
Line 471: Line 519:
 
Sound card is {{ic|hw:0,0}}.
 
Sound card is {{ic|hw:0,0}}.
  
====Determine sampling-rate of the sound card (2/5)====
+
==== Determine sampling-rate of the sound card (2/5) ====
 
{{hc|arecord -f dat -r 60000 -D hw:0,0 -d 5 test.wav|
 
{{hc|arecord -f dat -r 60000 -D hw:0,0 -d 5 test.wav|
 
"Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 60000 Hz, Stereo
 
"Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 60000 Hz, Stereo
Line 480: Line 528:
 
observe, the {{ic|got = 96000Hz}}. This is the max sample-rate of our card.
 
observe, the {{ic|got = 96000Hz}}. This is the max sample-rate of our card.
  
====Setting the soundcard's sampling rate into pulse audio configuration (3/5)====
+
==== Setting the soundcard's sampling rate into pulse audio configuration (3/5) ====
 +
 
 
The default sample-rate in pulseaudio:
 
The default sample-rate in pulseaudio:
 
{{hc|$ grep "default-sample-rate" /etc/pulse/daemon.conf|
 
{{hc|$ grep "default-sample-rate" /etc/pulse/daemon.conf|
Line 489: Line 538:
 
  # sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf
 
  # sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf
  
====Restart pulseaudio to apply the new settings (4/5)====
+
==== Restart pulseaudio to apply the new settings (4/5) ====
 +
 
 
  $ pulseaudio -k
 
  $ pulseaudio -k
 
  $ pulseaudio --start
 
  $ pulseaudio --start
  
====Finally check by recording and playing it back (5/5)====
+
==== Finally check by recording and playing it back (5/5) ====
 +
 
 
Let us record some voice using mic for say 10 seconds. Make sure the mic is not muted and all
 
Let us record some voice using mic for say 10 seconds. Make sure the mic is not muted and all
 
  $ arecord -f cd -d 10 test-mic.wav
 
  $ arecord -f cd -d 10 test-mic.wav
Line 503: Line 554:
  
 
=== My Bluetooth device is paired but does not play any sound ===
 
=== My Bluetooth device is paired but does not play any sound ===
 +
 
[[Bluetooth#My_device_is_paired_but_no_sound_is_played_from_it|See the article in Bluetooth section]]
 
[[Bluetooth#My_device_is_paired_but_no_sound_is_played_from_it|See the article in Bluetooth section]]
  
Line 510: Line 562:
 
Enable=Socket
 
Enable=Socket
 
</nowiki>}}
 
</nowiki>}}
If you face problems with A2DP and PA 2.99 make sure you have {{pkg|sbc}} library:
+
If you face problems with A2DP and PA 2.99 make sure you have {{Pkg|sbc}} library.
# pacman -S sbc
+
  
 
=== Subwoofer stops working after end of every song  ===
 
=== Subwoofer stops working after end of every song  ===
 +
 
Known issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/494099
 
Known issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/494099
  
Line 522: Line 574:
  
 
=== Pulseaudio uses wrong microphone ===
 
=== Pulseaudio uses wrong microphone ===
 +
 
If Pulseaudio uses the wrong microphone, and changing the Input Device with Pavucontrol did not help, take a look at alsamixer. It seems that Pavucontrol does not always set the input source correctly.
 
If Pulseaudio uses the wrong microphone, and changing the Input Device with Pavucontrol did not help, take a look at alsamixer. It seems that Pavucontrol does not always set the input source correctly.
  
Line 538: Line 591:
  
 
=== No sound below a volume cutoff ===
 
=== No sound below a volume cutoff ===
 +
 
Known issue (won't fix): https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133
 
Known issue (won't fix): https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133
  
Line 545: Line 599:
 
</nowiki>}}
 
</nowiki>}}
  
However, be aware that it may cause another bug preventing pulseaudio to unmute speakers when headphones or other audio devices are unplugged
+
However, be aware that it may cause another bug preventing pulseaudio to unmute speakers when headphones or other audio devices are unplugged.
 +
 
 
=== Low volume for internal mic ===
 
=== Low volume for internal mic ===
 +
 
If you experience low volume on internal notebook microphone, try setting:
 
If you experience low volume on internal notebook microphone, try setting:
 
{{hc|/etc/pulse/default.pa|<nowiki>
 
{{hc|/etc/pulse/default.pa|<nowiki>
Line 552: Line 608:
 
</nowiki>}}
 
</nowiki>}}
  
==External links==
+
== See also ==
*[http://www.pulseaudio.org/wiki/PerfectSetup http://www.pulseaudio.org/wiki/PerfectSetup] - A good guide to make your configuration perfect
+
 
*[http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Alsa wiki on .asoundrc
+
* [http://www.pulseaudio.org/wiki/PerfectSetup http://www.pulseaudio.org/wiki/PerfectSetup] - A good guide to make your configuration perfect
*[http://www.pulseaudio.org/ http://www.pulseaudio.org/] - PulseAudio official site
+
* [http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Alsa wiki on .asoundrc
*[http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - PulseAudio FAQ
+
* [http://www.pulseaudio.org/ http://www.pulseaudio.org/] - PulseAudio official site
 +
* [http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - PulseAudio FAQ

Revision as of 11:43, 5 June 2013

PulseAudio is the default sound server that serves as a proxy to sound applications using existing kernel sound components like ALSA or OSS. Since ALSA is included in Arch Linux by default so the most common deployment scenarios include PulseAudio with ALSA.

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary end

Contents

Installation

Running

Note:
  • Pulseaudio requires D-Bus to function.
  • Most X11 environments start pulseaudio automatically with the X11 session.

In the unlikely event that pulseaudio is not automatically called upon entering X, it can can be started with:

$ pulseaudio --start

PulseAudio can be stopped with:

$ pulseaudio -k

Equalizer

Newer pulseaudio versions have an intergrated 10-band equalizer system. In order to use the equalizer do the following:

Load equalizer sink module

$ pactl load-module module-equalizer-sink

Install and run the gui frontend

Install python2-pyqt and execute:

$ qpaeq
Note: If qpaeq has no effect, install pavucontrol and change "ALSA Playback on" to "FFT based equalizer on ..." while the media player is running.

Load equalizer module on every boot

Edit the file /etc/pulse/default.pa with your favorite editor and append the following lines:

### Load the integrated pulseaudio equalizer module
load-module module-equalizer-sink

Backend Configuration

ALSA

Note: Optional packages are needed only if running x86_64 and wanting to have sound for 32 bit programs (like Wine).

For the applications that do not support PulseAudio and support ALSA it is recommended to install the PulseAudio plugin for ALSA. This package also contains the necessary /etc/asound.conf for configuring ALSA to use PulseAudio.

To prevent applications from using ALSA's OSS emulation and bypassing Pulseaudio (thereby preventing other applications from playing sound), make sure the module snd_pcm_oss is not being loaded at boot. If it is currently loaded (lsmod|grep oss), disable it by executing:

# rmmod snd_pcm_oss

ALSA/dmix without grabbing hardware device

Note: This section describes alternative configuration, which is generally not recommended.

You may want to use ALSA directly in most of your applications and to be able to use other applications, which constantly require PulseAudio at the same time. The following steps allow you to make PulseAudio use dmix instead of grabbing ALSA hardware device.

  • Remove package pulseaudio-alsa, which provides compatibility layer between ALSA applications and PulseAudio. After this your ALSA apps will use ALSA directly without being hooked by Pulse.
  • Edit /etc/pulse/default.pa.
Find and uncomment lines which load backend drivers. Add device parameters as follows. Then find and comment lines which load autodetect modules.
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
# load-module module-udev-detect
# load-module module-detect
  • Optional: If you use kdemultimedia-kmix you may want to control ALSA volume instead of PulseAudio volume:
$ echo export KMIX_PULSEAUDIO_DISABLE=1 > ~/.kde4/env/kmix_disable_pulse.sh
$ chmod +x ~/.kde4/env/kmix_disable_pulse.sh
  • Now, reboot your computer and try running alsa and pulseaudio applications at the same time. They both should produce sound simultaneously.
Use pavucontrol to control PulseAudio volume if needed.

OSS

There are multiple ways of making OSS-only programs play to PulseAudio:

ossp

Install ossp package and start ossp service.

padsp wrapper (part of PulseAudio)

Programs using OSS can work with PulseAudio by starting it with padsp:

$ padsp OSSprogram

A few examples:

$ padsp aumix
$ padsp sox foo.wav -t ossdsp /dev/dsp

You can also add a custom wrapper script like this:

/usr/local/bin/OSSProgram
#!/bin/sh
exec padsp /usr/bin/OSSprogram "$@"

Make sure /usr/local/bin comes before /usr/bin in your PATH.

GStreamer

To make GStreamer use PulseAudio, you need to install gst-plugins-good or gstreamer0.10-good-plugins.

OpenAL

OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so:
/etc/openal/alsoft.conf
drivers=pulse,alsa

libao

Edit the libao configuration file:

/etc/libao.conf
default_driver=pulse

Be sure to remove the dev=default option of the alsa driver or adjust it to specify a specific Pulse sink name or number. Alternatively, note that you could keep the libao standard of outputting to the alsa driver and its default device if you install pulseaudio-alsa since the ALSA default device then is PulseAudio.

ESD

PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.

Desktop environments

General X11

Note: As mentioned previously, PulseAudio is very likely launched automatically via either /etc/X11/xinit/xinitrc.d/pulseaudio or the files in /etc/xdg/autostart/ if users have some DE installed.

Check to see if PulseAudio is running:

$ ps aux | grep pulse
 facade   1794  0.0  0.0 360464  6532 ?        S<l  15:33   0:00 /usr/bin/pulseaudio --start
 facade   1827  0.0  0.0  68888  2608 ?        S    15:33   0:00 /usr/lib/pulse/gconf-helper

If Pulseaudio is not running and users are using X, the following will start PulseAudio with the needed the X11 plugins manually:

$ start-pulseaudio-x11

If you are not running Gnome, KDE or XFCE and your ~/.xinitrc does not source the scripts in /etc/X11/xinit/xinitrc.d (such as is done in the example file /etc/skel/.xinitrc) then you can launch PulseAudio on boot with:

~/.xinitrc
/usr/bin/start-pulseaudio-x11

GNOME

As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.

KDE 3

PulseAudio is not a drop-in replacement for aRts. Users of KDE 3 cannot use PulseAudio. However note, recent versions of PulseAudio may have eliminated the prohibition:

See: http://www.pulseaudio.org/wiki/PerfectSetup KDE 3 uses the artsd sound server by default. However, artsd itself can be configured to use an Esound backend. Edit kcmartsrc (either in /etc/kde or /usr/share/config for global configuration or .kde/share/config to configure only one user) like this:

[Arts]
Arguments=\s-F 10 -S 4096 -a esd -n -s 1 -m artsmessage -c drkonqi -l 3 -f
NetworkTransparent=true
SuspendTime=1

KDE Plasma Workspaces and Qt4

PulseAudio, it will be used by KDE/Qt4 applications. For more information see the KDE page in the PulseAudio wiki.

PulseAudio support has been merged into KMix, the default KDE sound mixer.

If the phonon-gstreamer backend is used for Phonon, GStreamer should also be configured to use PulseAudio by installing gstreamer0.10-good-plugins.

One useful tidbit from that page is to add load-module module-device-manager to /etc/pulse/default.pa.

Additionally, the kdeplasma-applets-veromixAUR is available in the AUR as a KDE alternative to KMix or pavucontrol.

Xfce

Applications running under Xfce can take advantage of PulseAudio. To manage PulseAudio settings you can use pavucontrol.

Applications

Audacious

Audacious natively supports PulseAudio. In order to use it, set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.

Java/OpenJDK 6

Create a wrapper for the java executable using padsp as seen on the Java sound with Pulseaudio page.

Music Player Daemon (MPD)

configure MPD to use PulseAudio. See also MPD/Tips_and_tricks#MPD_.26_PulseAudio.

MPlayer

MPlayer natively supports PulseAudio output with the "-ao pulse" option. It can also be configured to default to PulseAudio output, in ~/.mplayer/config for per-user, or /etc/mplayer/mplayer.conf for system-wide:

/etc/mplayer/mplayer.conf
ao=pulse

Skype (x86_64 only)

Install lib32-libpulse, otherwise the following error will occur when trying to initiate a call: "Problem with Audio Playback".

Troubleshooting

No sound after install

Muted audio device

If one experiences no audio output via any means while using ALSA, attempt to unmute the sound card. To do this, launch alsamixer and make sure each column has a green 00 under it (this can be toggled by pressing Template:Keypress):

$ alsamixer -c 0

Bad configuration files

If after starting pulseaudio, the system outputs no sound, it may be necessary to delete the contents of ~/.pulse. Pulseaudio will automatically create new configuration files on its next start.

Flash content

Since Adobe Flash does not directly support PulseAudio the recommended way is to configure ALSA to use the virtual PulseAudio soundcard.

Alternatively you may try out libflashsupport-pulseAUR from the AUR.

Note: This may invariably crash the flash plugin.

No cards

If PulseAudio starts, run pacmd list. If no cards are reported, make sure that the ALSA devices are not in use:

$ fuser -v /dev/snd/*
$ fuser -v /dev/dsp

Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.

The only device shown is "dummy output"

This may be caused by different reasons, one of them being the .asoundrc file in $HOME is taking precedence over the systemwide /etc/asound.conf.

The user file is modified also by the tool asoundconf or by its graphical variant asoundconf-gtk (the latter is named "Default sound card" in the menu) as soon as it runs. Prevent the effects of .asoundrc altogether by commenting the last line like this:

.asoundrc
# </home/yourusername/.asoundrc.asoundconf>

Maybe some program is monopolizing the audio device:

# fuser -v /dev/snd/*
                     USER       PID  ACCESS COMMAND
/dev/snd/controlC0:  root        931 F....  timidity
                     bob        1195 F....  panel-6-mixer
/dev/snd/controlC1:  bob        1195 F....  panel-6-mixer
                     bob        1215 F....  pulseaudio
/dev/snd/pcmC0D0p:   root        931 F...m  timidity
/dev/snd/seq:        root        931 F....  timidity
/dev/snd/timer:      root        931 f....  timidity

That means timidity blocks pulseaudio from accessing the audio devices. Just killing timidity will make the sound work again.

Another reason is FluidSynth conclicting with pulseaudio as discussed in this thread. The solution is to remove FluidSynth:

# pacman -Rnsc fluidsynth

KDE4

It may be that another output device set as preferred in phonon. Make sure that every setting reflects the preferred output device at the top, and check the playback streams tab in kmix to make sure that applications are using the device for output.

Failed to create sink input: sink is suspended

If you do not have any output sound and receive dozens of errors related to a suspended sink in your journalctl -b log, then backup first and then delete your user-specific pulse folders:

$ rm -r ~/.pulse ~/.pulse-cookie

Bluetooth headset replay problems

Some user report huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated.

$ cp /etc/pulse/default.pa ~/.pulse/default.pa
~/.pulse/default.pa
; load-module module-suspend-on-idle
$ pulseaudio -k && pulseaudio --start

More information

Automatically switch to Bluetooth or USB headset

Add the following:

/etc/pulse/default.pa
# automatically switch to newly-connected devices
load-module module-switch-on-connect

Pulse overwrites ALSA settings

Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to .xinitrc or .bash_profile or any other autostart file:

restore_alsa() {
 while [ -z "$(pidof pulseaudio)" ]; do
  sleep 0.5
 done
 alsactl -f /var/lib/alsa/asound.state restore 
}
restore_alsa &

Prevent Pulse from restarting after being killed

Sometimes you may wish to temporarily disable Pulse. In order to do so you will have to prevent Pulse from restarting after being killed.

$ echo autospawn=no > ~/.pulse/client.conf

Daemon startup failed

Try resetting PulseAudio:

$ rm -rf /tmp/pulse* ~/.pulse*
$ pulseaudio -k
$ pulseaudio --start

If there is no server running but pulseaudio fails to start with an error message "User-configured server at ... refusing to start/autospawn", the issue may be with PulseAudio settings from a previous login. Check to see if there are any stale properties attached to the X11 root window with pax11publish -d, and if there are, remove them with pax11publish -r before trying to start the server. This manual cleanup is always required when using LXDM because it does not restart the X server on logout; see LXDM#PulseAudio.

inotify issue

If the previous fix doesn't work, run the following:

$ pulseaudio -vvvv

If you see an error that looks like this:

E: [pulseaudio] module-udev-detect.c: You apparently ran out of inotify watches, probably because Tracker/Beagle took them all away. I wished people would do their homework first and fix inotify before using it for watching whole directory trees which is something the current inotify is certainly not useful for. Please make sure to drop the Tracker/Beagle guys a line complaining about their broken use of inotify.

Then you have run out of inotify watches.

This can quickly be resolved by running:

$ echo 100000 > /proc/sys/fs/inotify/max_user_watches

To have it permanently changed, add to /etc/sysctl.conf

# Increase inotify max watchs per user
fs.inotify.max_user_watches = 100000

padevchooser

If one cannot launch the PulseAudio Device Chooser, first restart the Avahi daemon (avahi-daemon).

Glitches, skips or crackling

The newer implementation of PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach.

Timer-based scheduling may expose issues in some ALSA drivers. On the other hand, other drivers might be glitchy without it on, so check to see what works on your system.

To turn timer-based scheduling off add tsched=0 in /etc/pulse/default.pa:

/etc/pulse/default.pa
load-module module-udev-detect tsched=0

Then restart the PulseAudio server:

$ pulseaudio -k
$ pulseaudio --start

Do the reverse to enable timer-based scheduling, if not already enabled by default.

Please report any such cards to PulseAudio Broken Sound Driver page

Setting the default fragment number and buffer size in Pulseaudio

More Information

Finding out your audio device parameters (1/4)

To find your sound card buffering settings:

$ echo autospawn = no >> ~/.pulse/client.conf
$ pulseaudio -k
$ LANG=C timeout --foreground -k 10 -s kill 10 pulseaudio -vvvv 2>&1 | grep device.buffering -B 10
$ sed -i '$d' ~/.pulse/client.conf

For each sound card detected by Pulseaudio, you will see output similar to this:

I: [pulseaudio] source.c:     alsa.long_card_name = "HDA Intel at 0xfa200000 irq 46"
I: [pulseaudio] source.c:     alsa.driver_name = "snd_hda_intel"
I: [pulseaudio] source.c:     device.bus_path = "pci-0000:00:1b.0"
I: [pulseaudio] source.c:     sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
I: [pulseaudio] source.c:     device.bus = "pci"
I: [pulseaudio] source.c:     device.vendor.id = "8086"
I: [pulseaudio] source.c:     device.vendor.name = "Intel Corporation"
I: [pulseaudio] source.c:     device.product.name = "82801I (ICH9 Family) HD Audio Controller"
I: [pulseaudio] source.c:     device.form_factor = "internal"
I: [pulseaudio] source.c:     device.string = "front:0"
I: [pulseaudio] source.c:     device.buffering.buffer_size = "768000"
I: [pulseaudio] source.c:     device.buffering.fragment_size = "384000"

Take note the buffer_size and fragment_size values for the relevant sound card.

Calculate your fragment size in msecs and number of fragments (2/4)

Pulseaudio's default sampling rate and bit depth are set to 44100Hz @ 16 bits.

With this configuration, the bit rate we need is 44100*16 = 44100 is disabled and needs to be changed to 96000:

# sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf

Restart pulseaudio to apply the new settings (4/5)

$ pulseaudio -k
$ pulseaudio --start

Finally check by recording and playing it back (5/5)

Let us record some voice using mic for say 10 seconds. Make sure the mic is not muted and all

$ arecord -f cd -d 10 test-mic.wav

After 10 seconds, let us play the recording...

$ aplay test-mic.wav

Now hopefully, there is no static noise in microphone recording anymore.

My Bluetooth device is paired but does not play any sound

See the article in Bluetooth section

Starting from PulseAudio 2.99 and bluez 4.101 you should avoid using Socket interface. Do NOT use:

/etc/bluetooth/audio.conf
[General]
Enable=Socket

If you face problems with A2DP and PA 2.99 make sure you have sbc library.

Subwoofer stops working after end of every song

Known issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/494099

To fix this, must edit: /etc/pulse/daemon.conf and enable enable-lfe-remixing :

/etc/pulse/daemon.conf
enable-lfe-remixing = yes

Pulseaudio uses wrong microphone

If Pulseaudio uses the wrong microphone, and changing the Input Device with Pavucontrol did not help, take a look at alsamixer. It seems that Pavucontrol does not always set the input source correctly.

$ alsamixer

Press Template:Keypress and choose your sound card, e.g. HDA Intel. Now press Template:Keypress to display all items. Try to find the item: Input Source. With the up/down arrow keys you are able to change the input source.

Now try if the correct microphone is used for recording.

Choppy Sound with Analog Surround Sound Setup

The low-frequency effects (LFE) channel is not remixed per default. To enable it the following needs to be set in /etc/pulse/daemon.conf :

/etc/pulse/daemon.conf
enable-lfe-remixing = yes

No sound below a volume cutoff

Known issue (won't fix): https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133

If sound doesn't play when Pulseaudio's volume is set below a certain level, try ignore_dB=1 in /etc/pulse/default.pa:

/etc/pulse/default.pa
load-module module-udev-detect ignore_dB=1

However, be aware that it may cause another bug preventing pulseaudio to unmute speakers when headphones or other audio devices are unplugged.

Low volume for internal mic

If you experience low volume on internal notebook microphone, try setting:

/etc/pulse/default.pa
set-source-volume 1 300000

See also