PulseAudio (or PA for short) is a sound server that provides a number of features on top of the low-level audio interface ALSA on Linux, such as:
- Networking support (P2P and server mode).
- Per-application volume controls
- Better cross-platform support
- Dynamic latency adjustment, which can be used to save power
- 1 Installation
- 2 Configuration
- 3 Troubleshooting
- 4 External resources
PulseAudio uses either:
If you have an Intel HDA soundcard, you probably want the following kernel option to improve power-saving:
Portage knows the global USE flag pulseaudio for enabling support for PulseAudio in other packages. Enabling this USE flag will pull in media-sound/pulseaudio automatically:
The recommend USE flags of pulseaudio are:
|alsa||Yes||Yes||Adds support for media-libs/alsa-lib (Advanced Linux Sound Architecture)|
|caps||Yes||Yes||Use Linux capabilities library to control privilege|
|dbus||Yes||Yes||Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc)|
|gdbm||Yes||Yes||Use sys-libs/gdbm to store PulseAudio databases. Recommended for desktop usage. This flag causes the whole package to be licensed under GPL-2 or later.|
|glib||Yes||Yes||Add support to dev-libs/glib-based mainloop for the libpulse client library, to allow using libpulse on glib-based programs.|
|orc||Yes||Yes||Use dev-lang/orc for just-in-time optimization of array operations|
|udev||Yes||Yes||Enable sys-fs/udev integration (device discovery, power and storage device support, etc)|
Optional USE flags of pulseaudio are:
|X||Yes||Build the X11 publish module to export PulseAudio information through X11 protocol for clients to make use. Don't enable this flag if you want to use a system wide instance. If unsure, enable this flag.|
|asyncns||Yes||Use libasyncns for asynchronous name resolution.|
|avahi||No||Add avahi/Zeroconf support|
|bluetooth||Yes||Enables Bluetooth Support|
|doc||No||Build the doxygen-described API documentation.|
|equalizer||No||Enable the equalizer module (requires sci-libs/fftw).|
|gnome||No||Use GConf to store user preferences on streams and so on. Don't enable this flag if you want to use a system wide instance. If unsure, enable this flag.|
|gtk||Yes||Adds support for x11-libs/gtk+ (The GIMP Toolkit)|
|ipv6||Yes||Adds support for IP version 6|
|jack||No||Adds support for the JACK Audio Connection Kit|
|libsamplerate||No||No||Build with support for converting sample rates using libsamplerate|
|lirc||No||Adds support for lirc (Linux's Infra-Red Remote Control)|
|oss||No||No||Enable OSS sink/source (output/input). Deprecated, upstream does not support this on systems where other sink/source systems are available (i.e.: Linux). The padsp wrapper is now always build if the system supports OSS at all.|
|realtime||No||Makes PulseAudio use RealtimeKit (sys-auth/rtkit) to get real-time priority while running.|
|ssl||Yes||Use dev-libs/openssl to provide support for RAOP (AirPort) streaming.|
|system-wide||No||No||Allow preparation and installation of the system-wide init script for PulseAudio. Since this support is only supported for embedded situations, do not enable without reading the upstream instructions at http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode .|
|systemd||No||Build with sys-apps/systemd support to replace standalone ConsoleKit.|
|tcpd||Yes||Adds support for TCP wrappers|
|test||No||Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in make.conf/package.use anymore|
|webrtc-aec||Yes||Uses the webrtc.org AudioProcessing library for enhancing VoIP calls greatly in applications that support it by performing acoustic echo cancellation, analog gain control, noise suppression and other processing.|
|xen||No||Builds a special paravirtualized module for running in a Xen guest.|
After setting this you want to update your system so the changes take effect:
- media-sound/pavucontrol - Pulseaudio Volume Control, a GTK+ based mixer for PulseAudio.
- media-sound/paprefs - PulseAudio Preferences, a configuration dialog for PulseAudio.
- KDE's Phonon integrated PulseAudio configuration and mixing, but it is not as powerful as pavucontrol or paprefs.
PulseAudio uses udev and ConsoleKit to dynamically give access to the soundcards to the currently "active" user. If you are running Systemd it will also take care of this without needing to use ConsoleKit.
To make this possible ACLs (Access Control Lists) are required:
If not, enable it at boot time:
When you're finished, check, if your permissions are working correctly:
Configuring other applications
Some applications need to be configured to output to PulseAudio by default. A detailed list of these can be found on the PulseAudio wiki's PerfectSetup page.
You need to install media-plugins/alsa-plugins with pulseaudio USE flag enabled:
You need to enable the following module in /etc/pulse/default.pa:
You need to set several GConf keys:
- You can use the graphical tool gstreamer-properties (part of gnome-extra/gnome-media). Select under Audio Input and Audio Output each PulseAudio Sound Server.
- Manual with gconftool:
- Note that some programs might still require you to set the GStreamer output plugin manually to PulseAudio Audio Sink.
You need to enable the following module in /etc/pulse/default.pa:
Also you need to select with eselect the PulseAudio implementation:
You need to set the following in /etc/libao.conf:
You need to set the following in /etc/openal/alsoft.conf:
You need to set the following in /etc/mplayer/mplayer.conf:
In case that you are using ALSA as a PulseAudio sink (output) and routing ALSA apps to PA but not using udev, you must make sure to have set a specific device to be used. Else, PulseAudio will use ALSA device "default" as sink which may be routed back to PulseAudio, forming a loop. To avoid this, add the parameter device=hw:0,0 (you can find the correct IDs by running aplay -l). In the following example, we use two soundcards, of which card 0, device 0 is used as a sink (audio output, e.g. speakers) and card 1, device 0 as a source (audio input, e.g. microphone). PulseAudio will still be able to access other cards than these but it needs these settings to avoid looping the default device in this setup.
These instructions are for setting up a headless pulse audio server. Meaning a server which has no display on it but does have speakers. This provides the ability to use the remote server's speakers for audio output.
You will get warned in a dozen places for doing this, but it is the proper method.
First configure USE flags and emerge the package. The system-wide USE flag is masked, so we have to unmask it.
Add the following 2 lines somewhere in the system.pa file
Replace 126.96.36.199/24 with the network mask that you want to be able to access the server.
Tell the init script that we really do want to do this, and then start it up.
For a more permanent solution you can add the following to your default.pa file
Now in the pulse audio volume control you should see the remote server listed under Output Devices. Under playback you should have a button next to the Mute audio button that when clicked will let you switch that audio stream to whichever output you want.
No sound after installation
If you have no sound while using ALSA, consider unmute the sound card. Launch alsamixer and make sure each column has a green 00 under it (Use m to toggle mute/unmute). Install pavucontrol and check if there is any output on the pavucontrol panel when playing an audio.
Enable debug mode
To get more informations you need to set the following in /etc/pulse/daemon.conf:
Afterwards restart the daemon:
Audio/Video out of sync
When using PulseAudio over your local network, you can experience out-of-sync problems. Solve this by adding tsched=0:
This disables time scheduling. Afterwards restart the daemon:
If the only playback device is the Dummy Output, PulseAudio can not access your sound devices. Either the user has no permissions (see section Permissions or another program blocks the access. Try:
It shows the relevant program. Close the program and reconfigure it to use PulseAudio.
No guarantees on actual latencies
Currently PA provides whatever latency at that moment is possible be it some milliseconds to hundreds of milliseconds without regard to what applications ask for.
In case of buffer under-run latencies are never decreased
Currently, if a buffer under-run occurs, PA buffers for longer increasing latency, but it then never tries to buffer for less until restart.
Re-sampling using up a lot of CPU time
Re-sampling can require quite a lot of computational power, PA defaults are rather conservative but in certain cases can still take a significant toll, in such cases edit /etc/pulse/daemon.conf and consider changing resample-method to something less CPU intensive, default-sample-format and default-sample-rate can also affect CPU utilization with higher bit-depth and larger difference in sample-rate generally needing more resources (e.g. re-sampling 44.1 kHz to 48 kHz is faster than re-sampling either to 192 kHz). Since re-sampling is done per each channel per input, channel configuration and number of applications can affect performance as well.