PulseAudio

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
 * Per-application volume controls
 * Better cross-platform support
 * Dynamic latency adjustment, which can be used to save power

PulseAudio allows for playing audio applications on the server, while hearing it through the client's soundcard. The application running on the server sends its audio output to the Pulse server instead of the server's soundcard. The Pulse client on the client receives this output and lets Alsa process it to the client's soundcard.

Installation
Portage knows the global USE flag pulseaudio for enabling support for PulseAudio in other packages. Enabling this USE flag will pull in automatically:

The USE flags of pulseaudio are:

After setting this you want to update your system so the changes take effect:

Permissions
If you have the USE flag acl enabled globally and are using ConsoleKit (i.e you're using a Desktop profile) permissions to sound cards will be handled automatically. You can check the permissions using getfacl:

{{Note|getfacl output shown above is only an example, if everything is working correctly, it should display username of whoever controls the active seat (that is, display/keyboard/mouse/etc set). {{Warning|This is the only supported configuration! If anyone loged on is in audio group, then that user can disregard acl (at least on non-selinux systems) and will likely not relinquish access after it has been obtained, effectively not allowing anyone else to output sound, if there's more than one such user, there can also an added random factor on who gets to control device}}

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.


 * ALSA

You need to install with pulseaudio USE flag enabled:

You need to enable the following module in :
 * OSS

You need to set serveral GConf keys:
 * GStreamer
 * You can use the graphical tool gstreamer-properties (part of ). Select under Audio Input and Audio Output each PulseAudio Sound Server.
 * Manuel with gconftool:

You need to enable the following module in :
 * ESD

Also you need to select with eselect the PulseAudio implementation:

You need to set the following in :
 * libao

You need to set the following in :
 * OpenAL

You need to set the following in :
 * MPlayer

Fast user switching
For fast user switching to work with PA where each session has its own PulseAudio process, ConsoleKit is used to know which session is active and therefore most likely to be the desired one to be granted exclusive control over device files in /dev/snd/. To make this possible Access Control Lists (or ACL for short) are required and because /dev is usually devfs, which is a form of tmpfs, ACL support for tmpfs is a must.

Without udev
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.

Headless server
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.

Server
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 1.2.3.0/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.

Client
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.

Usage
A handy cross-desktop graphical tool is available for setting various aspects of PA. Install it with

KDE users can to some extent use Phonon`s configuration but it is not a full replacement for pavucontrol.

Enable debug mode
To get more informations you need to set the following in :

Afterwards restart the daemon:

Dummy Output
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 und 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.

External resources

 * PulseAudio Homepage
 * Ubuntu Feisty LTSP PulseAudio Howto
 * PulseAudio: The Perfect Setup
 * Why you should care about PulseAudio (and how to start doing it)