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 480155
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Also, why?
by phoenix on Fri 8th Jul 2011 20:50 UTC in reply to "RE[3]: Also, why?"
Member since:

No more fighting the system to be able to have more than one application produce sound at a time.
No more stuttering when the system is under heavy load.
No more rebooting because a file handle didn't get freed up correctly, effectively locking the sound card.

This was due to a fault in the OSSv3 support in Linux, and the half-bakedness of ALSA. All non-Linux Unix-like systems using OSSv3 have been able to mux multiple inputs into a single output.

Odd that people praise "yet another layer on top" for fixing this issue, when everyone else fixed it in OSSv3.

Will be interesting to see what happens in 2012 when "yet another layer" comes out to replace Pulse, instead of fixing ALSA itself.

Reply Parent Score: 4