< PulseAudio

PulseAudio/Examples

Creating user configuration files

System-wide configuration files are located under /etc/pulse while user configuration files are located under $XDG_CONFIG_HOME/pulse, which defaults to ~/.config/pulse. For the examples below which modify the user's configuration file it may be necessary to first create the file. This can be done either by copying the system file under /etc/pulse to the user's configuration directory, or by creating a new file that includes it with the syntax .include /etc/pulse/name. For simple changes the latter is preferred because the user will not be required to update the file when system-wide defaults change.

User client configuration file example

 
~/.config/pulse/client.conf
.include /etc/pulse/client.conf
# User's directives go here.

This syntax works for default.pa, daemon.conf and , even if the latter makes no sense as a user configuration file.

Set default input source

List available input sources

The in front of the index indicates the current default input.

To set a system wide default, add the source name in the default.pa file:

/etc/pulse/default.pa
...
set-default-source ''alsa_output.pci-0000_04_01.0.analog-stereo.monitor''
...

For temporary use

$ pacmd "set-default-source alsa_output.pci-0000_04_01.0.analog-stereo.monitor"
Tip: The default source can be referred as @DEFAULT_SOURCE@ in commands, for example: $ pactl set-source-mute @DEFAULT_SOURCE@ toggle.

Set the default output sink

To list the output sinks available, type the following command:

The in front of the index indicates the current default output.

To set a system wide default, add the source name in the default.pa file:

or per-user configuration default.pa file (which loads the default configuration from and overwrites the lines specified in this file:

When done then you can logout/login or restart PulseAudio manually for these changes to take effect.

Set the default output sink profile

Sometimes PulseAudio neglects to load the desired profile on start (e.g. a profile for having #Independent analog and digital outputs on the same card). To change the default profile, append the following to default.pa:

Note:

You could also use <cardindex> instead of <symbolic-name>, but using <symbolic-name> ensures referencing the correct device. <cardindex> is dynamic, and changes when a new device is plugged in.

Find by running pacmd list-cards:

In this case, I want to use the device with index number 2, so should be .

To find , set the desired profile manually, then run :

In this case, default.pa should now be changed to this:

You can test your configuration by running .

Independent analog and digital outputs on the same card

Sound cards may have both analog and digital (iec958) outputs. Pulseaudio does not generate combined profiles by default, you can choose either digital or analog profiles.

The easiest way to make both outputs available is to add a combined profile to the end of default profile configuration file:

This way a defined profile is added to the end of the list of available profiles.

Although this works, pulseaudio has a nasty habit of falling back to auto-generated profiles, so you may eventually need to set your card back to the combined profile. The best way to overcome this is by writing a custom configuration with disabled . Copy default.conf to , and edit it to suit your needs (this example is for stereo output/input):

Now that you have your custom profile you need to tell pulseaudio to use it. This can be done by defining an udev rule:

First get relevant information about your sound card:

Now create a configuration file:

Now tell udev to reload sound subsystem (as the root user) and restart pulseaudio. Your sound card should now use only the defined profile and have both analog and digital outputs available.

Simultaneous HDMI and analog output

PulseAudio allows for simultaneous output to multiple sources. In this example, some applications are configured to use HDMI while others are configured to use analog. Multiple applications are able to receive audio at the same time. ( is from the alsa-utils package.)

Or by using the the command:

The key to a configuration like this is to understand that whatever is selected in pavucontrol under Configuration > Internal Audio is the default device. Load pavucontrol > Configuration and select HDMI as the profile.

To setup the analog device as a secondary source, add the following to the configuration at the beginning, before any other modules are loaded: 

### Load analog device
load-module module-alsa-sink device=hw:0,0
load-module module-combine-sink sink_name=combined
set-default-sink combined

Restart PulseAudio, run pavucontrol and select the "Output Devices" tab. Three settings should be displayed:

  1. Internal Audio Digital Stereo (HDMI)
  2. Internal Audio
  3. Simultaneous output to Internal Audio Digital Stereo (HDMI), Internal Audio

Now start a program that will use PulseAudio such as MPlayer, VLC, mpd, etc. and switch to the "Playback" tab. A drop-down list should be available for the running program to select one of the three sources.

Also see this thread for a variation on this theme and PulseAudio FAQ.

Alternative solution using module-loopback with delay compensation

If the example above does not work for you, for instance because of echos / delays, you can try the following configuration.

In this case, the HDMI-Audio was 65ms behind analog when using module-combine-sink.

/etc/pulse/default.pa
[...]
load-module module-alsa-sink device=hw:0,0 sink_name=analog sink_properties=device.description=analog
load-module module-alsa-sink device=hw:0,1 sink_name=digital sink_properties=device.description=digital
load-module module-alsa-sink device=hw:0,3 sink_name=hdmi sink_properties=device.description=hdmi
load-module module-loopback sink=analog latency_msec=65
[...]
set-default-sink hdmi

HDMI output configuration

As outlined in https://download.nvidia.com/XFree86/gpu-hdmi-audio-document/index.html#_issues_in_pulseaudio unless the HDMI port is the first output, PulseAudio will not be able to have any audio when using certain graphics cards with HDMI audio support. This is because of a bug in PulseAudio where it will only select the first HDMI output on a device. A work around posted further down is to first find which HDMI output is working by using the utility from ALSA (in alsa-utils).

The original title for this section indicated the problem is specific to nVidia cards. As seen in this forum thread other cards are affected as well. The rest of the section will use an nVidia card as a case-study but the solution should carry over for people using other affected cards.

Finding HDMI output

Then find the working output by listing the available cards

In case your HDMI port is wired to the NVIDIA card, but does not detect an NVIDIA audio card, follow NVIDIA/Troubleshooting#No audio over HDMI.

Testing for the correct card

Now that we have a list of detected cards and devices, users will need to test for which one is outputting to the TV/monitor; for example, to test card 1, device 3 from the list above:

# aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav

If there is no audio, then try substituting a different card and/or device number (on my card I had to use card 1 device 7)

Manually configuring PulseAudio to detect the Nvidia HDMI

Having identified which HDMI device is working, PulseAudio can be forced to use it via an edit to :

# load-module module-alsa-sink device=hw:1,7

where the 1 is the card and the 7 is the device found to work in the previous section. Place this towards the bottom of the file, so that other sinks may still be auto-detected.

Restart PulseAudio:

$ pulseaudio -k
$ pulseaudio --start

Open the sound settings manager, make sure that under the hardware tab the graphics cards HDMI audio is set to "Digital Stereo (HDMI) Output" (My graphics card audio is called "GF100 High Definition Audio Controller").

Then, open the output tab. There should now be two HDMI outputs for the graphics card. Test which one works by selecting one of them, and then using a program to play audio. For example, use VLC to play a movie, and if it does not work, then select the other.

Automatically switch audio to HDMI

Create a script to switch to the desired audio profile if an HDMI cable is plugged in:

Make the script executable.

Create a udev rule to run this script when the status of the HDMI change:

To make the change effective do not forget to reload the udev rules:

udevadm control --reload-rules

A reboot might be required.

Surround sound systems

Many people have a surround sound card, but have speakers for just two channels, so PulseAudio cannot really default to a surround sound setup. To enable all of the channels, edit : uncomment the default-sample-channels line (i.e. remove the semicolon from the beginning of the line) and set the value to 6. For a 5.1 setup, or 8 for a 7.1 setup etc.

# Default
default-sample-channels=2
# For 5.1
default-sample-channels=6
# For 7.1
default-sample-channels=8

If your channels are not correctly mapped or the volume controls for the individual channels do not work as expected in pavucontrol, and you have a HDMI and an analog soundcard, then try to add the following line to 

load-module module-combine channels=6 channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe

Note that this example is for a 5.1 setup.

After doing the edit, restart PulseAudio.

Disabling UCM/"HiFi"

Most guides to making surround sound work with PulseAudio will tell you that you need to select the correct surround sound profile for your card/HDMI output, which you can do using the "Configuration" tab in . However, you may find that the only profile for your card is "HiFi: Play HiFi quality Music", which is not a surround sound profile. You may then waste far too much time trying to create a profile for your card, or set up udev rules correctly, neither of which will do anything.

What's actually happening here is that you have installed, and so PulseAudio is ignoring its own profiles and trying to use ALSA Use Case Manager profiles instead. Unfortunately, if ALSA UCM doesn't have a useful profile for your card, you're stuck with the default 2-channel "HiFi" instead. Fortunately, you can fix this by switching back to PulseAudio profiles, which default to a surround sound configuration for surround sound capable sound cards/HDMI outputs.

The easiest way to do this is to edit as follows: 

load-module module-udev-detect use_ucm=0

and then reload the pulseaudio.service user unit.

Your PulseAudio installation will then ignore UCM and use PulseAudio profiles, which, if you've changed your default-sample-channels as per the above instructions, will include a surround sound profile that you can use to output surround sound. You can verify by checking the configuration tab in , where you should no longer see "HiFi".

Splitting front/rear

Connect speakers to front analog output and headphones to rear output. It would be useful to split front/rear to separate sinks. Add to :

 load-module module-remap-sink sink_name=speakers sink_properties="device.description='Speakers'" remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right
 load-module module-remap-sink sink_name=headphones sink_properties="device.description='Headphones'" remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=front-left,front-right

Make sure to replace alsa_output.pci-0000_05_00.0.analog-surround-40 with the sound card name shown in 'pacmd list-sinks'. Now you have 2 additional sinks which can be used separately. You can choose 'sink_name' freely, as long as there is no sink with that name already. The 'remix' parameter controls whether the audio should be down-/upmixed to match the channels in the sink.

Splitting 7.1 into 5.1+2.0

Similar to the example above, you can also split a 7.1 configuration into 5.1 surround and stereo output devices. Set your card to 7.1 mode, then add the following lines to :

 load-module module-remap-sink sink_name=Surround sink_properties="device.description='Surround'" remix=no master=alsa_output.pci-0000_00_14.2.analog-surround-71 channels=6 master_channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe
 load-module module-remap-sink sink_name=Stereo sink_properties="device.description='Stereo'" remix=no master=alsa_output.pci-0000_00_14.2.analog-surround-71 channels=2 master_channel_map=side-left,side-right channel_map=front-left,front-right

Make sure to replace alsa_output.pci-0000_00_14.2 with your sound card name, get it by running 'pacmd list-sinks'. This configuration will use the front/rear/center+lfe (green/black/orange) jacks for the 5.1 sink and the side (grey) jack for the stereo sink. It will also downmix any audio to stereo for the stereo sink, but will not touch the 5.1 output.

Disabling LFE remixing

By default, PulseAudio remixes the number of channels to the default-sample-channels and since version 7 it also remixes the LFE channel. If you wish to disable LFE remixing, uncomment the line:

; enable-lfe-remixing = yes

and replace yes with no:

enable-lfe-remixing = no

then restart Pulseaudio.

Binaural Headphones

 
provides a plugin to simulate surround sound on stereo headphones. To use it, find your headphones with:

Load the plugin (new sink_name is up to you, master=headphone's sink name):

pacmd load-module module-ladspa-sink sink_name=binaural master=bluez_sink.00_1F_82_28_93_51 plugin=bs2b label=bs2b control=700,4.5

Use to transfer streams to the new sink, or:

pactl move-sink-input $INPUTID $BINAURALSINKNAME

PulseAudio over network

One of PulseAudio's unique features is its ability to stream audio from clients over TCP to a server running the PulseAudio daemon reliably within a LAN. Ensure that client and server systems agree on the time (i.e., use NTP), or audio streams may be choppy or may not work at all. For a more detailed guide visit the Official PulseAudio Documentation

Enable the TCP module on the server(the computer that actually outputs sound), edit to add or uncomment:

load-module module-native-protocol-tcp

Or you can use the gui application (root is not required):

 Go to Network Server -> Enable network access to local sound devices

To make sure module-native-protocol-tcp is loaded on the server, you can use:

pacmd list-modules | grep module-native-protocol-tcp

It is a requirement that both the client and server share the same cookie. Ensure that the clients and server share the same cookie file found under . It does not matter whose cookie file you use (the server or a client's), just that the server and client(s) share the same one.

If it is undesirable to copy the cookie file from clients, anonymous clients can access the server by passing to on the server (again in ):

load-module module-native-protocol-tcp auth-anonymous=1

It is also possible to authenticate based on client IP address:

load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/24

Change the LAN IP subnet to match that of those clients you wish to have access to the server.

Selecting the server

For a single shell or command you can set the PULSE_SERVER environment variable to the host name or IP address of the desired PulseAudio server:

$ env PULSE_SERVER=server_hostname_or_ip mplayer test.mp3

Alternatively, you can create or modify ~/.config/pulse/client.conf or to set a default-server persistently:

default-server = server_hostname_or_ip

Selecting the server with Zeroconf

For the remote PulseAudio server to appear in the PulseAudio Device Chooser (), load the appropriate zeroconf modules, and enable the Avahi daemon. On both machines, the client and server, install the package. Start/enable afterwards.

On the server, add to . On the client, add to . Now redirect any stream or complete audio output to the remote PulseAudio server by selecting the appropriate sink.

If you have issues with the remote syncs appearing on the client, try restarting the Avahi daemon on the server to rebroadcast the available interfaces.

Run the graphical PulseAudio Volume Control . Under the Output Devices tab, you should see the local and remote output devices. Under the Playback tab, to the left of the "X" Mute Audio button, you should see a box containing the name of an output device. That box is actually a button, which will display a drop-down radio-button list of the available output devices, with one output device selected. Selecting an output device from the list will allow the audio stream to be switched to the PulseAudio server associated with that output device. This control is not at all obvious until you have used it, and is especially useful with a remote Headless sound server.

Similarly, under the Input Devices tab, local and remote input devices will be seen. And under the Recording tab, there will be a box, to the left of the "X" Mute Audio button, with the name of an input device which is actually a button which will display a drop-down radio-button list of available input devices.

Run on the local or remote host associated with the audio stream to be directed. For instance, run on the remote host to direct the remote audio output to the local host. Run on the local host to direct the local audio output to some remote host.

Setting up simultaneous inputs or outputs is a different thing. Search about "monitor" and "module-combine-sink" for that.

Switching the PulseAudio server used by local X clients

To switch between servers on the client from within X, the pax11publish command can be used. For example, to switch from the default server to the server at hostname foo:

$ pax11publish -e -S foo

Or to switch back to the default:

$ pax11publish -e -r

Instead of telling the PulseAudio server to stream audio (as described above), this will edit PulseAudio variables on the X11 root window, which will instruct the PulseAudio client libraries to connect to a PulseAudio server other than . As such, the programs will no longer interact with the local pulseaudio process, which can then be stopped. Programs such as , or will need to also run with the appropriate PULSE_SERVER environment/X variable to control the remote PulseAudio server.

Note that for the switch to become apparent, the programs using Pulse must be restarted, or their PulseAudio client library otherwise reinitialized (completely stopping and restarting playback may be enough). To make this setting permanent, edit in ~/.config/pulse/client.conf or .

When everything else seems to fail

The following is a quick fix and NOT a permanent solution

On the server:

$ paprefs

Go to Network Access -> Enable access to local sound devices (Also check both 'Allow discover' and 'Don't require authentication').

On the client:

$ export PULSE_SERVER=server.ip && mplayer test.mp3

Using RTP/UDP instead of native-protocol-tcp

There are serious issues with trying to send data in real time over TCP, especially over lossy connections like wifi. This is why RTP over UDP was invented. It can be used to increase reliability and reduce latency.

When RTP is working properly, late or dropped packets will just create a few milliseconds of silence instead of a long pause while TCP is orchestrating the packet resend logistics. As an added bonus, if the remote server is ever restarted, the connection will be re-established automatically. However there will no longer be a way to remotely control the server's master volume, with each client machine having its own independent master volume instead.

To use RTP instead of , pulseaudio clients must connect to a local pulseaudio server first. This local server then connects to the remote pulseaudio server through RTP.

To use RTP in pulseaudio, install on the remote and local servers.

To configure the remote pulseaudio server, add the following to (or to if running pulseaudio in mode):

load-module module-rtp-recv latency_msec=10 sap_address=0.0.0.0

sap_address=0.0.0.0 is important to prevent pulseaudio from trying to use multicast, which doesn't work at all over wifi. Use to tune the receiving buffer size on the remote end. If you find the audio is spotty, try increasing this number. If you care more about latency, try decreasing it. Restart the remote server to cause the changes to take effect.

To configure the local pulseaudio server, add the following to :

load-module module-null-sink sink_name=rtp sink_properties="device.description='RTP'"
load-module module-rtp-send source=rtp.monitor destination_ip=<remote host>

<remote host> is the host name of the remote pulseaudio server.

After restarting the local server, a new sink labelled "RTP" will appear in pavucontrol. To route a particular client's output to it, find the client under the "Playback" tab, then change the client from its current sink (e.g. "Built-in Audio Analog Stereo") to "RTP". To use the RTP sink by default for all clients, add this to , then restart the local pulseaudio server:

set-default-sink rtp

Enable autodiscover AirPlay (raop) server support

To autodiscover and use a AirPlay server, ensure the is installed and Avahi is running (this is for autodetection itself). Also install (for the raop protocol). Then, add the following to :

load-module module-raop-discover

Restart pulseaudio.service and devices should automatically appear in the list of sinks.

This example is taken from julianxhokaxhiu's gist.

ALSA monitor source

To be able to record from a monitor source (a.k.a. "What-U-Hear", "Stereo Mix"), use to find out the name of the source in PulseAudio (e.g. ). Then add lines like the following to or :

pcm.pulse_monitor {
  type pulse
  device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
}

ctl.pulse_monitor {
  type pulse
  device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
}

Now you can select pulse_monitor as a recording source.

Alternatively, you can use pavucontrol to do this: make sure you have set up the display to "All input devices", then select "Monitor of [your sound card]" as the recording source.

Monitor specific output

It is possible to monitor a specific output, for example to stream audio from a music player into a VOIP application. Simply create a null output device:

pactl load-module module-null-sink sink_name=<name> sink_properties=device.description=<description>

In Pulseaudio Volume Control (pavucontrol), under the "Playback" tab, change the output of an application to <name>, and in the recording tab change the input of an application to "Monitor of <name>". Audio will now be outputted from one application into the other.

PulseAudio through JACK

The JACK Audio Connection Kit is popular for audio work, and is widely supported by Linux audio applications. It fills a similar niche as PulseAudio, but with more of an emphasis on professional audio work. It can offer lower latency audio monitoring along with greater control of input and output of multi-i/o sound devices.

The KXStudio method

This configuration requires the package.

JACK now has native features for bridging between ALSA, PulseAudio, and JACK. This will allow you to simultaneously have JACK and PulseAudio running with both outputting at the same time, with no configuration editing or terminal commands required.

If you have installed, make sure that it is not running (it might be running minified in the system tray). Also ensure that no process is running (use ps xw in a terminal to check).

Install , as well as . Once installed and started, JACK bridge configuration is found in the bottom right of the window. The ALSA audio bridge should be set to ALSA -> PulseAudio -> JACK, and the PulseAudio bridge should be enabled. Make sure in that all output devices besides Jack sink are muted, and all input devices besides Jack input are muted. Start JACK using the Force Restart button, and if it starts successfully PulseAudio programs should begin outputting to JACK.

The manual sink configuration method

This configuration provides a method of allowing JACK and PulseAudio to run at the same time and output to each other. It uses manual configuration of the systems that bridge between JACK and PulseAudio. This configuration has no reliance on scripts or commands and is entirely based in configuration.

This configuration only works with jack2. To use this configuration, just install the package. is already configured to load the modules in if they are present. If you want to be sure, open the file and look for the line:

load-module module-jackdbus-detect options

Where can be any options supported by this module, usually .

As described on the Jack-DBUS Packaging page:

Server auto-launching is implemented as D-Bus call that auto-activates JACK D-Bus service, in case it is not already started, and starts the JACK server. Correct interaction with PulseAudio is done using a D-Bus based audio card "acquire/release" mechanism. When JACK server starts, it asks this D-Bus service to acquire the audio card and PulseAudio will unconditionally release it. When JACK server stops, it releases the audio card that can be grabbed again by PulseAudio.

dynamically loads and unloads module-jack-sink and module-jack-source when jackdbus is started and stopped.

If PulseAudio sound does not work, check with to see if the relevant programs appear in the playback tab. If not, add the following to or to redirect ALSA to PulseAudio:

pcm.pulse {
    type pulse
}

ctl.pulse {
    type pulse
}

pcm.!default {
    type pulse
}
ctl.!default {
    type pulse
}

If it still does not work, check with in the playback tab and make sure the relevant programs are outputting to PulseAudio JACK Sink instead of your audio card (which JACK has control of, so it will not work). Also ensure that in the JACK graph the PulseAudio JACK Source is connected to the system audio output.

The shell script method

This method allows JACK and PulseAudio to output at the same time. It mostly relies on shell scripts that are automatically run by QJackCTL to manage aspects of how the JACK sinks and PulseAudio behave.

The basic idea is that killing PulseAudio is a bad idea because it may crash any applications using PulseAudio and disrupt any audio playing.

The flow of how this setup works:

  1. PulseAudio releases the sound card
  2. JACK grabs sound card and starts up
  3. script redirects PulseAudio to JACK
  4. manually send PulseAudio applications to JACK output (pavucontrol may come in helpful for this)
  5. use JACK programs etc
  6. via script, stop redirecting PulseAudio to JACK
  7. stop JACK and release sound card
  8. PulseAudio grabs sound card and reroutes audio to it directly

With QJackCTL, set up these scripts:

set it up as the execute script on startup script
#!/bin/bash
pacmd suspend true

pulse-jack-post-start.sh set this one up as execute script after startup

#!/bin/bash
pactl load-module module-jack-sink channels=2
pactl load-module module-jack-source channels=2
pacmd set-default-sink jack_out
pacmd set-default-source jack_in
"execute script on shutdown"
#!/bin/bash
SINKID=$(LANG=C.UTF-8 pactl list | grep -B 1 "Name: module-jack-sink" | grep Module | sed 's/[^0-9]//g')
SOURCEID=$(LANG=C.UTF-8 pactl list | grep -B 1 "Name: module-jack-source" | grep Module | sed 's/[^0-9]//g')
pactl unload-module $SINKID
pactl unload-module $SOURCEID
sleep 5
"execute script after shutdown"
#!/bin/bash
pacmd suspend false

The PulseAudio kill method

This method relies on shell scripts to automatically kill PulseAudio when JACK is started, and automatically restart it when JACK is stopped. This will result in lower CPU usage than having both running, but can cause errors in already running PulseAudio application and does not allow simultaneous output of both.

Using the settings listed above, use QjackCtl to execute a script upon startup and shutdown to load/unload PulseAudio. Part of the reason users may wish to do this is that the above changes disable PulseAudio's automatic hardware detection modules. This particular setup is for using PulseAudio in an exclusive fashion with JACK, though the scripts could be modified to unload and load an alternate non-JACK setup, but killing and starting PulseAudio while programs might be using it would become problematic.

The following example could be used and modified as necessary as a startup script that daemonizes PulseAudio and loads the padevchooser program (optional, needs to be built from AUR) called : 

#!/bin/bash	
#Load PulseAudio and PulseAudio Device Chooser
pulseaudio -D
padevchooser&

as well as a shutdown script to kill PulseAudio and the Pulse Audio Device Chooser, as another example called also in the home directory: 

#!/bin/bash	
#Kill PulseAudio and PulseAudio Device Chooser		
pulseaudio --kill	
killall padevchooser

Both scripts need to be made executable.

then with QjackCtl loaded, click on the Setup button and then the Options tab and tick both "Execute Script after Startup:" And "Execute Script on Shutdown:" and put either use the ... button or type the path to the scripts (assuming the scripts are in the home directory) and making sure to save the changes.

PulseAudio through JACK issues

When JACK is started Firefox, Chrome and other applications stop playing video and audio

Firefox/Chrome/etc. is using PulseAudio soundcard sink instead of the JACK sink. Open and on the Playback tab switch all audiostreams from something like "Built-in Audio Analog Stereo" to something like "Jack sink (PulseAudio JACK Sink)".

After I start JACK the sound from PulseAudio becomes distorted

In QjackCtl click Setup and on the Settings tab, Parameters subtab untick "Realtime". In addition, tweaking Sample Rate, Frames/Period and Period/Buffer may help. Look for latency in the bottom right corner, as you still want minimal latency for audio production. Also, I think Sample Rate should match one of the rates supported by your audio interface ( and look for rates, there could be multiple occurrences).

PulseAudio through OSS

Add the following to :

load-module module-oss

Then start PulseAudio as usual, making sure that sinks and sources are defined for OSS devices.

PulseAudio from within a chroot

Since a chroot sets up an alternative root for the running/jailing of applications, PulseAudio must be installed within the chroot environment itself.

PulseAudio, if not set up to connect to any specific server (this can be done in , through the PULSE_SERVER environment variable, or through publishing to the local X11 properties using module-x11-publish), will attempt to connect to the local pulse server, failing which it will spawn a new pulse server. Each pulse server has a unique ID based on the machine-id value in /var/lib/dbus. To allow for chrooted applications to access the pulse server, the following directories must be mounted within the chroot:-

/run
/var/lib/dbus
/tmp
~/.config/pulse
should also be mounted for efficiency and good performance. Note that mounting /home would normally also allow sharing of the  folder.

PulseAudio selects the path to the socket via XDG_RUNTIME_DIR, so be sure to drag it along when you chroot as a normal user using sudo (see Sudo#Environment variables).

Remapping sinks

The module-remap-sink module creates a virtual sink, which is identified as a unique sink, but is connected to the master sink by a virtual stream. In doing so, it has the ability to remap how the master sink's channels are used for playback.

Remapping select audio sources

Naturally, the virtual sink has its own monitor, which can be used as a source only capturing applications using the virtual sink. sink_name can be determined by looking at the name field in . As with other modules, it can be invoked from , or using :

$ pacmd load-module module-remap-sink sink_name=secondary master=sink_name

For instance, to record a program's output without including any other system sounds, you could:

  • Load the module by running the command.
  • Using pavucontrol, in the Playback tab, change the desired program's output device to the remapping. Repeat for any other programs whose audio should be included.
  • Activate the recording program.
  • In pavucontrol, in the Recording tab, change the recording program's input to the Monitor of option for the remapping.

Remap stereo to mono

Remap a stereo input-sink to a mono sink by creating a virtual sink. It would be useful if you only have one speaker. Add to :

load-module module-remap-sink master=alsa_output.pci-0000_00_1f.5.analog-stereo sink_name=mono sink_properties="device.description='Mono'" channels=2 channel_map=mono,mono
# Optional: Select new remap as default
set-default-sink mono

(replace alsa_output.pci-0000_00_1f.5.analog-stereo in the sound card name shown from )

Switch player between virtual mono sink and real stereo sink.

Remap left or right to mono

Particularly useful in the case an audio stream has different content in the left and right channels, such as Japanese television broadcasts with bilingual audio.

# For Japanese bilingual TV
load-module module-remap-sink sink_name=Left-to-Mono sink_properties="device.description='Left to Mono (5.1 AC3 on ALC892 Digital)'" master=alsa_output.pci-0000_00_1b.0.iec958-ac3-surround-51 channels=2 master_channel_map=mono,mono channel_map=front-left,rear-left
load-module module-remap-sink sink_name=Right-to-Mono sink_properties="device.description='Right to Mono (5.1 AC3 on ALC892 Digital)'" master=alsa_output.pci-0000_00_1b.0.iec958-ac3-surround-51 channels=2 master_channel_map=mono,mono channel_map=front-right,rear-right

Replace (5.1 AC3 on ALC892 Digital) with your own card ().

Remap for broadcasting software

If you do not want to capture sound from the application you need to create Remap sink:

### Create Remap sink
load-module module-remap-sink sink_name=Remap_sink master=SINK_NAME channels=2 remix=no
set-default-sink Remap_sink

Then restart PulseAudio daemon:

$ pulseaudio -k
$ pulseaudio --start

Now you need set the as the default sound source in broadcast software

Remap left (or right) input to mono for stereo use

Sometimes the incoming audio is only present on one channel (e.g. when using a mono XLR microphone on a two channel audio interface that is configured as stereo input by default). Using module-remap-source, the left channel can be remapped to be a mono source for further use:

load-module module-remap-source master=alsa_input.usb-BEHRINGER_UMC204HD_192k-00.analog-stereo channels=1 master_channel_map=front-left channel_map=mono

Swap left/right channels

This is the same as "reverse stereo", where the left and right channels are to be swapped.

First, identify the card you want its channels swapped:

$ cat /proc/asound/cards

and use the name string for the device you wish to use (the one in square brackets, e.g. [Intel]).

Edit and comment out module-hal-detect and module-detect lines.

Search for the commented-out line that starts "#load-module module-alsa-sink", uncomment it and change it to

load-module module-alsa-sink device=hw:"device_name" channel_map=right,left

Restart the pulseaudio deamon by running

pulseaudio -k; pulseaudio -D

Pulseaudio FAQ: How can I reverse my left and right speaker channels?

Using default.pa

Another approach to swapping channels is suggested in :

~/.config/pulse/default.pa
#!/usr/bin/pulseaudio -nF

.include /etc/pulse/default.pa

load-module module-remap-sink sink_name=reverse-stereo master=0 channels=2 master_channel_map=front-right,front-left channel_map=front-left,front-right
set-default-sink reverse-stereo

Pipe a source directly into a sink

Sometimes you want an input to be replicated to an output, e.g. if you want to play back your mic on your speakers for troubleshooting, or want to hear your capture card's captured audio. Here is how to set that up dynamically using pactl:

$ pactl load-module module-loopback source=input_source sink=output_source

This command will print the module's ID so that you can stop the piping later like this:

$ pactl unload-module id

If you lose the ID, you can obtain it from .

Capture digital input from S/PDIF and play on analog output in (nearly) real time

Sometimes you have a digital sound source that outputs S/PDIF signal encoded in PCM or AC3 (for example a smart TV) and you would like to use your Linux box as a converter for this singal to analog audible signal that you can play on your speakers. The challenge is to have no audible delay between your digital source and analog output (which can result in audio/video out of sync in our smart TV example).

You can use tool for that purpose.

The usage is fairly simple. Just connect S/PDIF cable to your sound card digital input and issue:

$ audio_async_loopback $my-digital-input-device $latency-in-microseconds

For example:

$ audio_async_loopback alsa_input.pci-0000_04_00.0.iec958-stereo 12500

To find out your digital device name, use command:

$ pacmd list-sources |grep 'name:'

Usually the digital input contains iec958 substring. If still unsure, remove grep part from command and check field:

properties:
   device.description

latency-in-microseconds is a matter of trial and error to determine, depending highly of your hardware speed. You can try to ommit this parameter, letting audio_async_loopback to determine the latency automatically. If you hear clicks and cracks, increase the value. If sound is clear but audio is out of sync or delayed, decrease the value. You can also do a fine-tuning of different buffers in before building the package but this should not be neccesary.

Author also recommends setting input volume to 100% (you can do it in your favourite pulseaudio mixer) and setting pulseaudio to work with 48kHz sampling rate for this tool to function correctly.

To set the sampling rate, edit /etc/pulse/daemon.conf and change line:

default-sample-rate = 44100

to:

default-sample-rate = 48000

To apply changes, restart pulseaudio.service.

PulseAudio as a minimal unintrusive dumb pipe to ALSA

Some people do not want to run PulseAudio all the time for various reasons. This example will turn the full fledged audio server into an unobstrusive dumb pipe to ALSA devices that automatically starts and stops itself when done, allowing applications that requires PulseAudio to fully function while not touching any ALSA setting nor setting itself as the default ALSA device.

This configuration tells native PA clients to autospawn the daemon when they need it, then the daemon is configured to autoexit as soon as all clients have disconnected. The daemon itself uses a plain simple static configuration that uses your configured ALSA devices and nothing more. No replacement of ALSA's default, no playing with mixer levels, nothing but record/playback. Also make sure is not installed so standard ALSA clients do not default to pulse. Since contains only a configuration file , if it is installed as dependency, one could simply comment all contents in . functions properly as well as any other ALSA clients. Also make sure common frameworks like Xine, Gstreamer and Phonon are configured to use ALSA: by default if they detect PulseAudio is installed they will try to use it before ALSA.

/etc/pulse/client.conf
# Replace these with the proper values

# Applications that uses PulseAudio *directly* will spawn it,
# use it, and pulse will exit itself when done because of the
# exit-idle-time setting in daemon.conf
autospawn = yes

Having both speakers and headphones plugged in and switching in software on-the-fly

By design, Pulseaudio automatically turns off Line Out when headphones are plugged in and uses Headphone slider instead. You can observe this behavior in . What we want is to have Headphone and Line Out sliders working separately and at the same time. This is extremely useful if you want to remap Realtek's jacks to have, say, Rear Green for headphones and Blue for speakers (with the help of hdajackretask from ).

To achieve this, you should directly edit Pulseaudio mixer's configuration.

1. We tell pulseaudio that headphones are always plugged in. Edit:

Find:

Change to

2. By default, Line Out's volume controlled only by Master, and not by Line Out slider itself. We want to merge Line Out with Master.

Add this snippet to the end of the file:

3. We need to completely cut off Line Out when we use headphones. Edit:

Add this snippet to the end of the file:

[Element Line Out]
switch = off
volume = off

4. Like Pulseaudio, Alsa itself cuts off speakers when headphones are plugged in. Open (in case of Realtek HDA ) and change to .

5. Restart Pulseaudio

$ pulseaudio -k
$ pulseaudio --start

Now you have two separate ports on the same sink in pulseaudio. They mute each other, so you can switch to headphones and this will mute Line Out, and vice versa. To switch between ports you can use Gnome or Plasma sound mixer, or install appropriate desktop extension.

Allowing multiple users to share a PulseAudio daemon

Normally each system user runs their own instance of PulseAudio and the instance is only accessible by the user running it. This is a security measure which prevents other users from accessing potentially sensitive audio channels such as voice calls. However, there are situations in which it is desirable to isolate an application by running it as a separate user. For example, one may wish to run a web browser as a different user while still being able to listen to audio from the browser while using the primary user account. Another use is to share a Bluetooth headset among multiple system users.

This can be achieved by creating a UNIX socket to allow other users to access the primary user's PulseAudio daemon. With this setup, the primary user account runs the PulseAudio daemon and the other user accounts connect to it and share it. Note that the following assumes that the environment variable `XDG_CONFIG_HOME` points to the default location `~/.config`. If this is not the case, replace `~/.config/` with the correct path in the examples below.

Primary user setup

The primary user should add the following directive to to create a UNIX socket and accept connections from other users:

Note that this will allow all users on the system to access the primary user's PulseAudio server and thus all audio data. A more secure solution is to create a custom user group for shared audio and limit the socket to it. For example, to allow only users in the group "sharepulse" to access the socket, change the line to

After adding the line, start the PulseAudio daemon on the primary user's account.

Secondary user setup

The secondary user should add the following line to :

~/.config/pulse/client.conf
default-server = unix:/tmp/pulse-socket

where /tmp/pulse-socket is the path to the UNIX socket set in the primary user's default.pa file above. If the primary user has restricted the socket to a specific system group, the secondary user must be added to it. Note that if a logged-in user is added to the group, it will not take effect until the user logs out and logs in again.

The secondary user will also need to copy the primary user's PulseAudio daemon cookie () to in their configuration directory. Alternatively, the primary user can copy the cookie to a location accessible by the intended system users (e.g. /tmp/sharepulse/pa_cookie) and the secondary user can access it by adding the following line to the client configuration file:

The secondary user should now have full access to the primary user's PulseAudio daemon and all audio should be accessible to bother users. To grant access to more users, simply repeat the setup for the secondary user on each user account.

Alternative setup

If there is no primary user to reliably run the shared PulseAudio daemon, the following script can be used by all users in a group (sharepulse in this example) to check if a shared server is already running and launch one if not.

Each user will need to add the following lines to their PulseAudio configuration files to configure the daemon and clients to use the shared socket and cookie:

~/.config/pulse/client.conf
default-server = unix:/tmp/sharepulse/socket
cookie-file = /tmp/sharepulse/cookie

pulseaudio-shared should be run by each user when logging in (e.g. via their Bash profile or their desktop environment's autostart file) to start the daemon when needed. Any arguments passed to the script will be passed through to the PulseAudio daemon. When any shared daemon is stopped, pulseaudio-shared will automatically restart as the current user and all other users should reconnect to the new daemon automatically.

No sound when switching TTY

If the sound stops when switching between users on different TTYs or desktop environments (<ctrl>+<alt>+Fx) then the users likely do not have access to the sound hardware when their TTY session is not selected. This can be fixed by adding the users to the audio group: Users and groups#Pre-systemd groups

Mixing additional audio into the microphone's audio

Using a setup of null sinks and loopbacks you can mix arbitrary applications' audio output into your microphone's audio, for example to play sound effects or music on voice chat applications.

The setup suggested here will also play your sound effects back to you and use PulseAudio echo cancellation to prevent the effects from feeding back into your microphone.

PulseAudio management with pulse-autoconf

As of August 2020 there is , a PulseAudio server dynamic configuration daemon that supports this setup with its 'EchoCancellationWithSourcesMix' preset and that comes with further benefits, such as dynamically reacting to changes in the PulseAudio server, for example when a headset or a webcam is plugged in or unplugged.

If does not work out for your use case, read on for the manual way.

PulseAudio configuration

Symbology: , , , {m} = Monitor of audio sink, , 

{Microphone}
    ||
{src_ec} -----------------> [sink_mix]{m}=={src_main}* -----> (Voice chat)
              Loopback            ^                                |
                                  | Loopback                       |
                                  |                                v
(Soundboard) ---------> [sink_fx]{m} -----------------------> [sink_main]*
                                             Loopback             ||
                                                              [Speakers]
{src_ec}, [sink_main]
Echo cancellation "clones" of the microphone and speakers
[sink_fx]
Virtual sink into which the sound effects are played
[sink_mix]
Virtual sink where the microphone and the sound effects are mixed together
{src_main}
Remap of "Monitor of sink_mix", to work around applications that do not allow recording from monitor sources

Applications configuration

The applications providing the sound effects must

  • Output to "sink_fx"

All other applications, including the voice chat, must

  • Record audio from "src_main"
  • Output to "sink_main"

Accordingly, these devices will be set as defaults. Controlling which application uses which audio source/sink can usually be done in the graphical PulseAudio control panel.

For some applications changing their sources or sinks in has no effect. In this case you can typically select the source or sink in the applications' audio settings.

No application whatsoever must record from, or output to, the "real" microphone or speakers, as this would bypass the echo cancellation.

Any echo cancellation or other audio processing provided by the voice chat application should be disabled – PulseAudio is doing this already, and as the application is not aware of the sound effects being played on the speakers, it will likely be ineffective in filtering them from the microphone anyway.

Setup steps
  1. Connect your microphone and headphones and make sure PulseAudio is configured correctly for their use, for example in the "Configuration" tab in
  2. First time only:
    1. Save the template script below to an executable file of your choice
    2. Find the names of your microphone and headphones with and , respectively
    3. In the script, replace the values of "microphone" and "speakers" with the names of your microphone/headphones
  3. Run the script
  4. Run your voice chat application and make it record audio from "src_main" and output audio to "sink_main"
  5. Run your sound effects application(s) and make them play to "sink_fx"

As for applications that can play sound effects, has been found to work quite well. It however needs to be closed and re-opened when PulseAudio is restarted.

Teardown

The changes that the script makes to the running PulseAudio server are not permanent and will be lost when PulseAudio terminates.

To ditch the custom configuration, just restart PulseAudio, e.g. with pactl exit. (PulseAudio is socket-activated and will automatically start on demand.)

Template script

 
#!/bin/bash

microphone="alsa_input.pci-0000_00_1b.0.analog-stereo"
speakers="alsa_output.pci-0000_00_1b.0.analog-stereo"

echo "Setting up echo cancellation"
pactl load-module module-echo-cancel use_master_format=1 aec_method=webrtc \
      aec_args="analog_gain_control=0\\ digital_gain_control=1\\ experimental_agc=1\\ noise_suppression=1\\ voice_detection=1\\ extended_filter=1" \
      source_master="$microphone" source_name=src_ec  source_properties=device.description=src_ec \
      sink_master="$speakers"     sink_name=sink_main sink_properties=device.description=sink_main

echo "Creating virtual output devices"
pactl load-module module-null-sink sink_name=sink_fx  sink_properties=device.description=sink_fx
pactl load-module module-null-sink sink_name=sink_mix sink_properties=device.description=sink_mix

echo "Creating remaps"
pactl load-module module-remap-source master=sink_mix.monitor \
      source_name=src_main source_properties="device.description=src_main"

echo "Setting default devices"
pactl set-default-source src_main
pactl set-default-sink   sink_main

echo "Creating loopbacks"
pactl load-module module-loopback latency_msec=60 adjust_time=6 source=src_ec          sink=sink_mix
pactl load-module module-loopback latency_msec=60 adjust_time=6 source=sink_fx.monitor sink=sink_mix
pactl load-module module-loopback latency_msec=60 adjust_time=6 source=sink_fx.monitor sink=sink_main

This script has been inspired by https://askubuntu.com/a/915064 , for more in-depth information also see that post's author's pulseaudio-config GitHub repository.

Using module-remap-source to work around applications that do not accept a monitor as source is taken from https://unix.stackexchange.com/a/608482 .

Invert phase of one audio channel

This is useful for compensating when one of your speakers is wired with the wrong polarity. To test if this is needed, see .

Adapted from a more general example of Assigning a LADSPA filter to a single audio channel. Requires .

#!/bin/bash
master=alsa_output.pci-0000_07_00.0.analog-stereo
pacmd load-module module-ladspa-sink sink_name=ladspa_out sink_master=$master plugin=inv_1429 label=inv
pacmd load-module module-remap-sink sink_name=remapR master=ladspa_out channels=1 master_channel_map=front-right channel_map=front-right
pacmd load-module module-remap-sink sink_name=remapL master=$master channels=1 master_channel_map=front-left channel_map=front-left
pacmd load-module module-combine-sink sink_name=invert sink_properties=device.description='"Invert\ phase"' slaves=remapL,remapR channels=2

Renaming devices

Sound devices will sometimes have confusing names assigned to them by default. Names like "CM106 Like Sound Device" are not very descriptive. This can be easily fixed and it works for both Pulseaudio sources and sinks.

The easiest method is to add the following lines to the end of the file.

To update a source name:

 update-source-proplist <DEVICE_NAME> device.description="<NEW_NAME>"

And to update a sink name:

 update-sink-proplist <DEVICE_NAME> device.description="<NEW_NAME>"

The device name can be queried using the command for sources, or for sinks.

This configuration can also be persisted on a per-user basis and be written to like so:

 #!/usr/bin/pulseaudio -nF
 
 ## Include defaults
 .include /etc/pulse/default.pa
 
 ## Rename devices
 update-source-proplist <DEVICE_NAME> device.description="<NEW_NAME>"

The default Pulseaudio configuration needs to be included, otherwise the daemon will not start.

gollark: Good for you?
gollark: ‭
gollark: ⁤
gollark: They aren't "letter birds", they're RFC1149 Avian Carriers.
gollark: My carrier pigeons ran out of food.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.