http://www.cio.com.au/article/320807...fp=&fpid=&pf=1
In short: PA is not bad. It exposes bugs in lower-level layers, and gets flamed by the end-users.I am not too concerned about most of the criticism and flames that erupt from time to time on various channels. All the big Linux distributions have adopted PulseAudio and it is an integral part of both the Palm Pre and the Nokia N900 devices, as well as Intel's Moblin. That basically means that PulseAudio has been adopted by about everyone who could adopt it. There is not really anyone who doesn't do PulseAudio anymore.
<... ...>
More specifically some applications were still using audio APIs [OSS] that are almost impossible to virtualize. And also PulseAudio makes use of a lot of driver functionality that was previously unused and hence little tested.
In fact, for quite a few parts of the lower level ALSA APIs PulseAudio is the first user of all. And of course, it cannot be a surprise that we expose bugs that were previously unknown in the drivers this way.
It's not my intention to shift the blame around though. PA and the other layers of our stack should not be viewed as independent parts. If PA uses a new or previously unused feature of the drivers then we need to fix the drivers at the same time.
If we make PA expect more correct behaviour from the apps, or that applications stop making particular assumptions about the audio stack, we need to fix the applications at the same time.


Reply With Quote


