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 480181
To read all comments associated with this story, please click here.
RE[2]: Broken audio hardware
by Yamin on Sat 9th Jul 2011 02:28 UTC in reply to "RE: Broken audio hardware"
Member since:

You shouldn't hate the ACID tests...

but imagine if the Google made their homepage make use of advanced HTML features requiring 100% ACID pass rate. Suddenly 90% of the world can't access Google when they previously could?

That would create a huge storm as well.

At the end of the day you make your products for your users. Google would never do that to it's users.

Neither should Linux distros.
The fault lies with the distros for packaging pulse audio when a lot of audio drivers didn't implements advanced functionality 100%.

Reply Parent Score: 3