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 480050
To read all comments associated with this story, please click here.
RE[3]: Broken audio hardware
by _txf_ on Thu 7th Jul 2011 21:08 UTC in reply to "RE[2]: Broken audio hardware"
_txf_
Member since:
2008-03-17

Never mind that I use OpenBSD as my desktop and my only real audio need is to listen to my music, which I do quite easily. Never mind that I never need to "handle more than one client with different latency constraints" and that I've never done mixing or sample conversion. Never mind that it's a very very small subset of the people who use Linux who need to do those things anyway.


When you have a 5.1 stream and you want it in a 2.0/2.1 system you need to mix the channels. These days that is quite normal. Also in portable systems to save power and not wake the system as often you want very high latency audio which you cannot do with alsa or oss. As far as I'm aware WebOS, Maemo and meego all use pulseaudio versus raw alsa for this very reason

Reply Parent Score: 4