except that hw mixing just works and does not introduce any delays. Hmmmm...
Printable View
Hardware mixing doesn't work. Why? Because my hardware doesn't do mixing. So how can it work?
Yeah, I'm joking. Point is, the hw mixing argument is just an excuse for shitty sw mixing implementations. In the age of dual core CPUs being the low end, not being able to do proper audio mixing sounds more like a bad joke to me.
Except that you would be wrong (in part). ALSA has *both* user-space and kernel side code. PA replaces ALSA's user-side (when in use) ie: things like dmix. and pa uses it's adapters to then handle it... But when using just ALSA - you will be using it's userspace components, instead of PA... You obviously don't really understand linux' sound systems/plumbing if you can make such a silly comment.
And regardless, my comparsion of zita-ajbridge/ALSA(user-space) vs. alsa_in/out/Pulseaudio in terms of stuttering, still stands.
Both PulseAudio and SystemD were created as approaches to help simplify and unify the Linux desktop and offer a greater set of desktop features. NetworkManger, although not by Lennart Poettering, was too and I often hear it be much maligned by some, even though for my use it is a killer feature of Linux. But in the end I see no need to argue the quality of his work with you, as you obviously have your own entrenched positions and already actively dislike the work he has done.
The real point of my post though is to simply point out that Ubuntu states these lofty goals but then puts little to no resources behind achieving them, while poor Poettering actually goes out and tries to get things accomplished to these ends and is decried as an evil for doing so by often the same people who hold Ubuntu in such high esteem. It is getting quite irritating.
Indeed, PulseAudio is very useful to have when dealing with peripheral audio devices like headphones or headsets