Language Selection

English French German Italian Portuguese Spanish

Should Pulseaudio Die? What do you think?

Filed under
Linux

When I was installing and testing Mandriva 2010 Cooker (new development) releases this last Fall season, I kept having persistent problems with sound. Eventually, the advice in the Mandriva Cooker forum for KDE users became: "Disable Pulseaudio, and set Xine as the preferred back end over GStreamer (in the KDE multimedia settings).

Unlike the latest 'buntu, Mandriva does supply a checkbox in their Control Center Sound configuration utility to enable/disable Pulseaudio.

Then Mandriva 2010 final came out, and Pulseaudio more or less works, (and GStreamer works fine for the KDE back end). Some users report that flash videos have no sound with Pulseaudio enabled. Certainly there's some sound lag with Pulseaudio.

Today I was listening to the latest tllts podcast (The Linux Link Tech Show). Tllts member Patrick Davila started his "rant" segment, and said:

Quote:
Pulseaudio sucks. The experiment [with Pulseaudio] has gone far too long. It's time to admit that it's a f*ing failure and every implementation sucks. The guy who runs it [Pulseaudio]--any time anybody tries to talk to him, is very negative and tells you you're an idiot. Canonical should hire Paul Davis, the developer of Jack and Ardour and Jack should become the default sound daemon."

What do you think? I tend to agree with Davila, however Linux sound is not my area of expertise. But I've certainly been plagued and frustrated over the years with Linux sound issues, and Pulseaudio seems to make things worse.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I use Sidux AMD64 with KDE

I use Sidux AMD64 with KDE 4.3 and I have a proper sound card - an M-Audio Revolution 5.1. I do not have any Pulseaudio installed. My sound works perfectly. In part this is because my sound card supports hardware mixing. KDE uses Phonon not Pulse.

Now, this week I built a second machine from old bits for the purpose of video editing. I wanted to try OpenShot so I installed Karmic Koala, as OpenShot requires Python 2.6 and so it will not run on anything Debian (yet). After installation I had no sound at all. The Pulseaudio controlled sound applet showed everything was working, but nothing emanated from the speakers. I installed Gnome Alsamixer and found that the output was not selected, a simple click of the mouse and music poured forth. To me the biggest fault here is Gnome using this new mixer applet instead of the traditional Alsa one. Ubuntu, or Gnome in general, have also removed the older Gnome Sound properties dialog with a Pulse based one. You can no longer change the default output easily. If it does not work there is now nowhere to go unless you are an experienced Linux user. I removed Pulseaudio as I had other issues with input from Aux (but that one was an ALSA issue), but in doing so lost the speaker applet. I disabled the onboard sound and put in a PCI sound card and reinstalled Pulseaudio and now it all works.

Is this the fault of Pulseaudo, Gnome or Ubuntu - or all of them. When Pulseaudio works it is a good tool, when it does not it is an utter pain. Unfortunately it seems to fail way too often for my liking. The failures are often simple and can be overcome with simple access to good Alsa based mixer. This then is the fault of Gnome and the distro builders. Bring back the old sound properties dialog and install Gnome Alsamixer by default. Give the noobs a fighting chance.

My last peeve is definitley distro based. Why is my sound constantly muted by updates? Not Sidux - the others. Why on earth would you set mute as the default? Ever?

enough ranting

It is junk.

I agree too. Pulse audio is junk just like udev, hal, dbus and polkit. Useless crap that don't work right.

Depends on the distro

I have an older Creative card that uses the snd-emu* drivers. It and PA (PulseAudio) work fine with certain distros, like Mandriva 2010 and Ubuntu 9.10. It and PA don't work well with others, like Fedora 12 and openSUSE 11.2. In those distros, system sounds come out layered in static. Flash and other audio playback can sometimes be staticky as well. Why one distro gives me no problems while another does, I have no idea.

The reaction of the PulseAudio dev is as follows: "Regarding snd-emu*: Creative doesn't like Open Source -- there are no docs available. If you buy Creative it is hence a bit your own fault."

Fair enough, except the card works fine with ALSA. Why the difference? The PulseAudio dev again: "As long as you only play MP3 music directly on the device and use the traditional sound card interrupt based wakeups the bogus timing information the sound drivers export doesn't matter. That's why you won't notice this issue without PA but it becomes very visible (or audible...) when PA is used."

Whoopee.

PulseAudio can do all kinds of cool things, but I'd just like to have an alternative to using it. I've tried but I can't replace it with any other backend in openSUSE 11.2 and have working sound, even in KDE 3/4.

re: depends distro

Yeah, I had trouble with a creative card and opensuse 11.2 too. Sound would only come out of one of the four speakers. That didn't go over too well with me.

I haven't had too much trouble with most of others distros except that Flash sound wouldn't work in the latest Mandriva. The only solution really offered was to disable pulseaudio. That did indeed do the trick.

Distros' fault

Pay attention to what PulseAudio's dev has said many times. Ubuntu in particular, he argues, does a HUGE disservice to the reputation of PulseAudio.

re: Distros fault

Yes, Linux Excuses 101.

Whenever something sucks, blame everyone (the distro, the user, the girlscouts) but the monkey who codes it.

its every distro?

I've only read the horror stories of PA but I've no experience myself. However, its constantly repeated that it is the distros' fault in their implementations. Perhaps the developer needs to provide more-clear examples or documentation so that his product doesn't get such a bad reputation?

On the flip side, which distros are implementing this correctly according to the PA developer(s)?

PulseAudio...

I've been using Linux on and off for the past four years and since my first stab at it, everyone always suggest that I stay away from PulseAudio. Because of that, I've always stuck with Alsa. It works and it works great. I'm personally a fan of building minimal Debian systems and I've always relied Alsa for sound. Most of it is because I've heard nothing but bad stories about PulseAudio. Lots of promise but just as much letdown. Does this project really lack that much direction/ it clearly isn't moving forward if this debate is still going on four years later.

yep

Pulse audio is garbage. I actually do blame the distros a little bit. If the crap isn't tested and working on common hardware, why put it in a so called stable release.The developer can test it all he wants, can ask for testers, or keep it on his hard drive for all I care. When the major distros release new versions, something as basic as sound should work. Period. I suppose the community working together on improving what we already have working would be too much to ask.

PulseAudio

I'm going to be murdered for posting this, but I think we should all go back to OSS, with version 4 and later version 5. I'm on Arch, so I can pick and choose from the beginning what I want to use. I have tried PulseAudio, which seems to lag, ALSA works but it sounds weak, compared to sound in OSS4 and Windows 7. I dare say it sounds better in OSS4 than Windows 7. I even have a Creative card and it works better in OSS than the rest with BETA drivers. Granted I don't do any recording or anything complicated that doesn't involve listening to FLAC audio, movies and youtube, with a 5.1 surround system. Adding to this, OSS is so easy to configure, everything residing in /usr/lib/oss and while the wiki is not updated as often, it has the usual problems that I encountered listed and in the forums, there are friendly people who have helped me, up to the extent of modifying source code and recompiling OSS on Arch in order to get a USB sound card working. I know what the developer did in the past still makes some people angry or distrustful but I don't think that's going to happen again, everyone can make mistakes and I think if we show more support with development and testing, OSS can be the greatest thing for sound in Linux and all of *nix systems. Freebsd uses it, maybe a modified version but to me OSS is both user and developer friendly.

I have not tried JACK, but if that works good, I don't have any complaints. I just want to move to something that is not ALSA or Pulseaudio and more importantly, that it works as intended.

http://www.4front-tech.com/forum/index.php
http://www.4front-tech.com
http://www.opensound.com/wiki/index.php

I agree

I find PC-BSD with OSS has the best sound on my system. I should try this with Chakra. JACK sounds interesting as well.

I also agree with Anonymo

I read "State of Sound in Linux not so Sorry After All"

http://insanecoding.blogspot.com/2009/06/state-of-sound-in-linux-not-so-sorry.html

I switched Ubuntu to OSS and everything was better / cooler / easier. i.e. the sound quality was better, the user interface was nicer too. (Although there was no OSS HDMI driver at the time.)

I also have used OSS on Solaris. It was the exact same experience. I plugged in a USB DAC and viola! It just worked.

Pulse made me busy all this year

Hi. I don't know if pulse have to die, but I sure hate its guts. I work for an OEM company who sell various machines with Linux/KDE installed. Pulse failed on basically all the HW configs that I saw.

At home, here's what I have to say : Pulse is not ready. When I manage to get it to work, it hangs.

I totally agree with the guy who proposed to replace pulse with jack, maybe with a simple frontend ? Jack is the only software that I know of that actually aknowledge that a user can have more than ONE soundcard.

More in Tux Machines

GNOME News: Black Lab Drops GNOME and Further GNOME Experiments in Meson

  • Ubuntu-Based Black Lab Enterprise Linux 11.0.1 Drops GNOME 3 for MATE Desktop
    Coming about two weeks after the release of Black Lab Enterprise Linux 11, which is based on the Ubuntu 16.04.2 LTS (Xenial Xerus) operating system using the HWE (hardware enablement) kernel from Ubuntu 16.10 (Yakkety Yak), Black Lab Enterprise Linux 11.0.1 appears to be an unexpected maintenance update addressing a few important issues reported by users lately.
  • 3.26 Developments
    My approach to development can often differ from my peers. I prefer to spend the early phase of a cycle doing lots of prototypes of various features we plan to implement. That allows me to have the confidence necessary to know early in the cycle what I can finish and where to ask for help.
  • Further experiments in Meson
    Meson is definitely getting more traction in GNOME (and other projects), with many components adding support for it in parallel to autotools, or outright switching to it. There are still bugs, here and there, and we definitely need to improve build environments — like Continuous — to support Meson out of the box, but all in all I’m really happy about not having to deal with autotools any more, as well as being able to build the G* stack much more quickly when doing continuous integration.

Fedora and Red Hat

Debian and Derivatives

  • Reproducible Builds: week 108 in Stretch cycle
  • Debuerreotype
    The project is named “Debuerreotype” as an homage to the photography roots of the word “snapshot” and the daguerreotype process which was an early method of taking photographs. The essential goal is to create “photographs” of a minimal Debian rootfs, so the name seemed appropriate (even if it’s a bit on the “mouthful” side).
  • The end of Parsix GNU/Linux
    The Debian-based Parsix distribution has announced that it will be shutting down six months after the Debian "Stretch" release.
  • Privacy-focused Debian 9 'Stretch' Linux-based operating system Tails 3.0 reaches RC status
    If you want to keep the government and other people out of your business when surfing the web, Tails is an excellent choice. The Linux-based operating system exists solely for privacy purposes. It is designed to run from read-only media such as a DVD, so that there are limited possibilities of leaving a trail. Of course, even though it isn't ideal, you can run it from a USB flash drive too, as optical drives have largely fallen out of favor with consumers. Today, Tails achieves an important milestone. Version 3.0 reaches RC status -- meaning the first release candidate (RC1). In other words, it may soon be ready for a stable release -- if testing confirms as much. If you want to test it and provide feedback, you can download the ISO now.

OSS Leftovers

  • Chef expands its cloud and container menu
    Chef, a leading DevOps company, announced at ChefConf 2017 that it was adding new capabilities to it flagship Continous Automation/DevOps program, Chef Automate. This enables enterprises to transition from server- and virtual machine- (VM) based IT systems to cloud-native and container-first environments with consistent automation and DevOps practices.
  • Nextcloud 12: The bigger, better, in-house small business cloud
    It's not even been a year since Frank Karlitschek, co-founder and former CTO of ownCloud, forked ownCloud into Nextcloud. Since then, this do-it-yourself, open-source Infrastructure-as-a-Service (IaaS) cloud has become increasingly popular. Now, its latest version, Nextcloud 12, the program is adding more Software-as-a-Service (SaaS) features.
  • The Spirit of Open Source
  • What happened to Mastodon after its moment in the spotlight?
    More than a month later, the buzz over Mastodon has quieted. But though it may not be making headlines, the service continues to grow.
  • Mozilla: One Step Closer to a Closed Internet
    We’re deeply disheartened. Today’s FCC vote to repeal and replace net neutrality protections brings us one step closer to a closed internet. Although it is sometimes hard to describe the “real” impacts of these decisions, this one is easy: this decision leads to an internet that benefits Internet Service Providers (ISPs), not users, and erodes free speech, competition, innovation and user choice.
  • The eternal battle for OpenStack's soul will conclude in three years. Again
    After six years as a formal project, OpenStack has survived numerous raids and famines and now finds itself in a not-too-weird space of being boring, on-premises infrastructure. That is, “boring” in the good way of focusing on what users want and fixing existing problems, only chasing shiny objects – cough, PaaS, cough, containers, cough, orchestration – as much as needed.
  • With version 2.0, Crate.io’s database tools put an emphasis on IoT
    Crate.io, the winner of our Disrupt Europe 2014 Battlefield, is launching version 2.0 of its CrateDB database today. The tool, which is available in both an open source and enterprise version, started out as a general-purpose but highly scalable SQL database. Over time, though, the team found that many of its customers were using the service for managing their machine data and, unsurprisingly, decided to focus its efforts on better supporting those clients.
  • NewSQL CockroachDB Ready for Prime Time
    There's a new open source database on the block. Although it has a name that will most likely make you cringe for the first dozen or so times you hear it -- CockroachDB -- I have a feeling that if it isn't already on your radar, it will be soon.
  • Windows 10 S Won't Support Fedora, SUSE Linux, and Ubuntu
  • Manage Linux servers with a Windows admin's toolkit [Ed: Well, the solution is learning GNU tools, not relying on proprietary stuff with back doors from Microsoft]
  • FreeBSD quarterly status report
  • openbsd changes of note 622
  • Book Review: Relayd and Httpd Mastery

    Overall an excellent book which is typical Michael W Lucas writing style. Easy to follow, clear cut instructions, and tons of new stuff to learn. If one must use OpenBSD or FreeBSD, then the chances are high that one will stick with the defaults that come with OpenBSD. No need to use fat Apache, or Nginx/Lighttpd web server especially when httpd and relayd audited for security by OpenBSD core team.

  • Guix System Distribution (GuixSD) 0.13.0 GNU/Linux OS Supports 64-bit ARM CPUs
    The GNU Guix and GuixSD 0.13.0 releases are here about five months after the December 2016 launch of version 0.12.0, and it appears to be a major milestone implementing a few important changes. First off, this release can now be installed on computers powered by AArch64 (64-bit ARM) processors.
  • The Good And Bad In WikiTribune, Wikipedia Founder's Open-Source News Site
    Countering the fake news threat has become a real challenge for social media platforms, which also serve as avenues of news dissemination along with the traditional media outlets.
  • Android Studio 3.0 Canary 1
  • Jaded by Java? Android now supports Kotlin programming language
  • Rcpp 0.12.11: Loads of goodies
    The elevent update in the 0.12.* series of Rcpp landed on CRAN yesterday following the initial upload on the weekend, and the Debian package and Windows binaries should follow as usual. The 0.12.11 release follows the 0.12.0 release from late July, the 0.12.1 release in September, the 0.12.2 release in November, the 0.12.3 release in January, the 0.12.4 release in March, the 0.12.5 release in May, the 0.12.6 release in July, the 0.12.7 release in September, the 0.12.8 release in November, the 0.12.9 release in January, and the 0.12.10.release in March --- making it the fifteenth release at the steady and predictable bi-montly release frequency.
  • Master Haskell Programming with Free Books
    Haskell is a standardized, general-purpose, polymorphically statically typed, lazy, purely functional language, very different from many programming languages. Recent innovations include static polymorphic typing, higher-order functions, user-definable algebraic data types, a module system, and more. It has built-in concurrency and parallelism, debuggers, profilers, rich libraries and an active community, with approximately 5,400 third-party open source libraries and tools.
  • [Older] Manifesto: Rules for standards-makers

    If we work together on a project based on open tech, these are the principles I will try to stick to. I wanted to put all this in one place, so I can pass it along to future software developers.