PulseAudio and I have a strained relationship

Ever since the Ubuntu folks switched their underlying sound architecture from ALSA to PulseAudio, I’ve had some manner of issue or another. At first, it was certain applications (e.g. Audacity) not running, due to never having been coded to use Pulse instead of its default, needing hours to hack around. Then after PulseAudio sorted out its own ALSA backward compatibility, it was the server crashing every time I opened an RDP connection using RDesktop (a recent version thankfully fixed that issue).

Today, I did some manual updates for my Jaunty installation, the first I’d done in about a week. I have automatic updates disabled on my work laptop for a number of reasons. One of the packages that came down was evidently PulseAudio, because after a reboot, sound wasn’t working. Nothing was showing as out of the ordinary on dmesg (the Linux command line based system event viewer — like in Windows going to My Computer > Manage > Event Viewer > System, or under Ubuntu you can go to System > Administration > Log File Viewer), and when I installed the PulseAudio Device Chooser applet to get access to the default device configuration, it was showing my sound card was functioning perfectly and was even outputting sound properly according to its internal diagnostics. My system volume was turned up, the laptop’s mute function was not active, and as far as I could see, everything else was working just fine, so I Googled the problem, and found this.

I wasn’t having the shutdown problem described in the bug report, but I’d had problems with ALSA disabling its own PCM in the past, so I opened my volume control via the sound icon and found that the PCM slider was all the way at the bottom, and the Mute button for it was ticked. PCM is the equivalent of the “Wave” slider under the Windows volume control — it’s the slider that handles most of the sound output aside from the “master” volume control, so basically anything that’s playing and isn’t a CD in the CD-Rom would be affected by it. I increased the volume on PCM and un-muted it, and magically sound started working again.

Now that I know this can happen because of a PulseAudio upgrade, I’ll think to look at this first, the next time this happens. But ultimately, why did it have to happen? I can’t think of a reason to ever change the PCM volume in the process of an upgrade — and if you have to default it to anything because the settings get wiped, it should default to 80% or something like that, something reasonable that doesn’t give a person the impression that something got broken over the course of an upgrade.

Don’t get me wrong. PulseAudio was a necessary and in fact laudable step toward unifying the Linux sound architecture world, where it can not only mix multiple sound streams, but can output to different sound devices or all sorts of devices simultaneously, including over the network. I will one day build a media centre that we can tune into from any computer in the house (probably including my Wii using Mplayer on the Homebrew Channel). But until that day, it’d be nice if they get the little things right before uploading their new versions.

Or maybe one day I’ll get around to learning C and step in myself…

PulseAudio and I have a strained relationship

3 thoughts on “PulseAudio and I have a strained relationship

  1. 1

    I have had difficulties with pulseaudio since it became the default for Ubuntu. Audacity is one issue, as you mentioned. Skype is yet another. The “pasuspender” command does work for some of these programs, but not with a great deal of reliability. I’ve taken the step of installing a second audio device for use by ALSA, which I have instructed pulseaudio to ignore completely.

    JACK would be a great alternative, but there are similar issues. With multiple audio servers available, and several programs that refuse to communicate with one or another, we’re not in an enviable position.

  2. 2

    I’ve managed to get Skype to play nicely with Pulseaudio, though at one point I had to use pasuspender to get it to work. Now, it actually uses my microphone properly. I have to manually change the sound settings to use “pulse” every time I start it for some reason, but that seems more like Skype not keeping its settings than anything.

    I think the problem with sound architecture on Linux is actually resultant from Linux’s biggest advantage — it’s so modular that multiple programs can do any single job or architecture component. Look at the desktop — even though Gnome and KDE are pretty well the biggest desktops, there’s still room for XFCE, fluxbox, etc. If PulseAudio emerges as a “big player”, then great. But if it doesn’t do its job, or is too heavy, you can still replace it on your system with ALSA or JACK.

  3. 3

    Why’d they switch from ALSA? Back in the day I had finally gotten it to work with all my systems. Note to self: dig out old Linux laptop and start playing again.

Leave a Reply

Your email address will not be published. Required fields are marked *