Linked by Thom Holwerda on Thu 7th Jul 2011 17:36 UTC, submitted by vivainio
Linux Linux.FR has an interview with Lennart Poettering of PulseAudio and systemd fame (among others). Regarding PulseAudio: "I can understand why people were upset, but quite frankly we didn't really have another option than to push it into the distributions when we did. While PulseAudio certainly wasn't bug-free when the distributions picked it up the majority of issues were actually not in PulseAudio itself but simply in the audio drivers. PulseAudio's timer-based scheduling requires correct timing information supplied by the audio driver, and back then the drivers weren't really providing that. And that not because the drivers were really broken, but more because the hardware was, and the drivers just lacked the right set of work-arounds, quirks and fixes to compensate for it."
Permalink for comment 480056
To read all comments associated with this story, please click here.
RE[4]: Broken audio hardware
by phoenix on Thu 7th Jul 2011 21:29 UTC in reply to "RE[3]: Broken audio hardware"
phoenix
Member since:
2005-07-11

As far as I'm aware WebOS, Maemo and meego all use pulseaudio versus raw alsa for this very reason


Ah, but is that because Pulse is so much better than everything else (OSSv3, OSSv4, FreeBSD OSS, OpenBSD sound, etc)? Or just because ALSA sucks so horribly?

The fact that projects use Pulse over raw ALSA just shows how bad raw ALSA is; it has no reflection whatsoever on any other audio stacks.

With the exception of Bluetooth audio, everything you can do with Pulse, I can do on FreeBSD using "that poor pathetic OSSv3", including all the different mixing of channels, redirecting of the network, multiple soundcards, multiple sources, etc.

Reply Parent Score: 3