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 480111
To read all comments associated with this story, please click here.
RE[5]: Broken audio hardware
by Neolander on Fri 8th Jul 2011 09:40 UTC in reply to "RE[4]: Broken audio hardware"
Neolander
Member since:
2010-03-08

"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"

And it makes perfect sense for them to do so, because what they need can't be supplied any other way. But they're not a normal desktop case.

I beg to differ. As laptops start to eat desktop's lunch more and more, battery life could well end up being a major "desktop" concern.

Then of course, optimizing the power consumption of something as light as audio streams while adding at the same time highly power-intensive GPU effects to the graphical stack is probably a bit hypocritical, but well...

Reply Parent Score: 2