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."
Thread beginning with comment 480124
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Blame game
by jessesmith on Fri 8th Jul 2011 12:45 UTC in reply to "Blame game"
Member since:

That's pretty much LP's view on everything. Whenever there is a problem with one of his projects or compatibility issues come up it's always everyone else's fault.

He says it was a driver issue, no, wait, it's a hardware issue. Well if it was a hardware issue then why did audio work fine under other operating systems using the same hardware? If it was a driver issue, then why did ALSA work so well on systems where Pulse refused to function?

The fact was PulsAudio was broken on arrival and it took a long time for it to get sorted out, probably because the developer was in such denial.

Reply Parent Score: 1

RE[2]: Blame game
by Tuxie on Fri 8th Jul 2011 13:02 in reply to "RE: Blame game"
Tuxie Member since:

That's a very ignorant and unfair claim. If you look at the ALSA changlogs for the last years you will see that Lennart has committed a MASSIVE amount of bugfixes for ALSA drivers himself!

Also take a look at some audio driver source code sometime. The workarounds needed to make some hardware work are agonizing at times.

The manufactures provide Windows-drivers already complete with workarounds for hardware bugs but just because the bugs normally (when using Windows) aren't exposed to the end user doesn't mean that the hardware isn't buggy.

The FOSS world doesn't usually have the luxury of manufacturer support. Things like this are found by trial-and-error by committed people like Lennart.

Reply Parent Score: 2

RE[2]: Blame game
by _txf_ on Fri 8th Jul 2011 14:05 in reply to "RE: Blame game"
_txf_ Member since:

If it was a driver issue, then why did ALSA work so well on systems where Pulse refused to function?

Sigh. It has been explained many times. That is because pulse uses the soundcard in a different manner than plain alsa. Also note that there was hardware that failed to work in vista due to the new sound model (similar model to pulse and coreaudio).

Reply Parent Score: 2

RE[3]: Blame game
by segedunum on Sat 9th Jul 2011 16:09 in reply to "RE[2]: Blame game"
segedunum Member since:

The logical thing to do when faced with that is to fix ALSA or accept that using ALSA was wrong. Retro-fitting another userspace layer over the top and trying to justify it is the wrong choice.

I take it Pulse still isn't a system service?

Reply Parent Score: 2