Getting Started with PulseAudio in Arch Linux

PulseAudio is a popular sound server for Linux that allows advanced audio functionality like mixing, network streaming, and per-application volumes. In this comprehensive guide, we‘ll cover everything you need to know to install, configure, and effectively utilize PulseAudio on an Arch Linux system.

Installing PulseAudio

Before installing PulseAudio, it‘s best practice to refresh your package database to ensure you download the latest available version:

sudo pacman -Syu

Once completed, install PulseAudio with:

sudo pacman -S pulseaudio

This will download and install the pulseaudio package and its dependencies.

Launching the PulseAudio Daemon

With PulseAudio installed, the next step is ensuring the PulseAudio daemon is running. This background process handles all audio routing and manipulation.

To start the daemon, run:

pulseaudio --start

To confirm it‘s running, use:

pulseaudio --check

If it returns daemon running, PulseAudio is up and running.

Graphical Configuration Tools

While PulseAudio can be configured via the command line, there are several handy GUI tools that make adjusting settings much easier:

pavucontrol

pavucontrol provides advanced control over input, output, and configuration options in an easy-to-use GTK interface:

sudo pacman -S pavucontrol

With pavucontrol, you can adjust the volume of playback devices, change audio profiles, redirect output to different devices, and much more.

paman

For simpler volume control and basic configuration, paman provides a minimalist Qt interface:

yay -S paman

While less fully-featured than pavucontrol, paman makes adjusting the master volume easy.

kmix

For KDE desktop users, kmix integrates directly with the Plasma desktop:

sudo pacman -S kmix  

Like paman, kmix focuses mainly on volume control but fits seamlessly into a KDE environment.

Key PulseAudio Concepts

Before diving into advanced configuration, it helps to understand some key concepts in PulseAudio:

• Sources – Sources represent audio input devices like microphones or applications producing sound.
• Sinks – Sinks refer to audio output devices like speakers or headphones.
• Modules – Modules process and route audio between sources and sinks.
• Profiles – Profiles optimize audio quality for different use cases like music playback or VoIP.
• Network Streaming – PulseAudio allows forwarding audio over a network to remote sinks.

These ideas represent the core building blocks of the PulseAudio sound architecture.

Useful PulseAudio Commands

In addition to the graphical tools, there are many helpful PulseAudio commands available from the CLI:

• pactl list sources – View available audio sources
• pactl list sinks – List output audio sinks
• pactl list modules – See loaded PulseAudio modules
• pactl list cards – Display recognized sound cards
• pactl set-default-sink – Set the default audio output device
• pactl set-sink-volume – Adjust sink volume
• pactl set-source-mute – Mute/unmute sources

These commands provide precise control over the PulseAudio environment.

System-Wide vs Per-User Operation

By default, PulseAudio runs on a per-user basis – each user session gets its own daemon instance. However, PulseAudio can also be configured to start for the entire system.

There are tradeoffs to each approach:

• Per-User

  • Isolates crashes/issues
  • Separate audio for each user
  • Increased memory usage

• System-Wide

  • Consistent across users
  • Limit one output sink
  • Applications can block others

In most desktop cases, per-user works best. But for specialty setups like audio workstations, system-wide can simplify routing.

To toggle system-wide operation, edit /etc/pulse/client.conf and modify:

; system-wide = yes

Optimizing Performance

Especially on low-power machines, PulseAudio can consume a considerable amount of resources. To improve performance, there are several key tuning steps:

1. Install thread priority tweaks:

sudo pacman -S pulseaudio-ctl

2. Enable realtime priority:

pulseaudio-ctl resrt-faster

3. Set the daemon to only launch when needed:

Edit /etc/pulse/client.conf to set:

autospawn = no

4. Disable unnecessary modules:

Unload Bluetooth, RTP, HTTP modules if unused.

These tweaks significantly lower PulseAudio resource usage for lighter-weight systems.

PulseAudio over the Network

A unique feature of PulseAudio is transmitting audio over a LAN to another system. This allows sending music from one PC to another or listening on multiple devices.

Here‘s an example config to stream to another Linux machine:

Sender system:

1. Install Avahi for hostname resolution

2. Find the target system hostname:

avahi-browse -artp

3. Load and configure the RTP sender module:

pacmd load-module module-rtp-send source=[source] \
  sink=rtp.[target_ip]

pacmd set-default-source [source]

Receiver system:

1. Load and configure the RTP receiver module:

pacmd load-module module-rtp-recv \
  source=rtp.[sender_ip] \
  sink=pulsesink

pacmd set-default-sink pulsesink

With that, audio played on the sender will now be forwarded to the receiving machine. This demonstrates PulseAudio‘s flexible routing capabilities.

Troubleshooting FAQs

There are a few common issues users tend to encounter with PulseAudio. Here are troubleshooting tips for frequent problems:

No sound from some applications

If some programs (like Firefox) have no audio, check pactl list sinks and set the default sink accordingly:

pactl set-default-sink [sink_name] 

Choppy/distorted audio

Choppy playback is often caused by resource contention. Try the performance tuning steps outlined above. Also adjust buffer metrics:

pacmd set-buffer-time 50000
pacmd set-latency-msec 150 

Playback crashing/device switching failure

If audio playback stops unexpectedly, toggle exit-idle-time to prevent PulseAudio from suspending idle streams:

pactl set-exit-idle-time 0

Also try resetting the sound server logic:

pulseaudio -k
pulseaudio --start

Following troubleshooting basics like checking logs, monitoring resources, and isolating issues can also help identify the root cause.

Next Steps with PulseAudio

This guide just scratches the surface of everything possible with PulseAudio. A few suggested next topics to explore include:

• Input source routing for multi-mic setups
• Audio networking via Bluetooth modules
• VOIP integration with custom profiles
• Writing PulseAudio modules in C
• Jack compatibility via module-jackdbus-detect
• Per-application EQs and audio effects

As one of the most advanced sound engines available on Linux, PulseAudio offers almost endless customization and tweaking potential. Hopefully this article has provided a solid foundation for setting up and utilizing this versatile utility. Let me know in the comments if you have any other topics you‘d like to see covered regarding PulseAudio on Arch Linux!