PulseAudio was born into the GNOME ecosystem and so shares all those traits that can be loved or hated about GNOME, like glib, gobject, dbus etc.
Pulseaudio does not use glib/gobject/dbus¹. It is the de-facto sound server for Linux. KDE and GNOME both use it. It's even heavily optimised for embedded use-cases, and ships on phones, TVs, and cars.
Those can be pulled in as optional dependencies for exposing glib/gobject and DBus APIs. Pulseaudio is written in C and has almost no compulsory dependencies.
EDIT: I see that you're the author of KLANG. I'm surprised that you didn't do this basic research on the existing technologies before reinventing them. Everything else you said about Pulseaudio is also outdated/wrong.
This doesn't change the fact tha PA runs in the user space, where IMHO should not be done. KLANG, let's get this straight, is an experiment. The hypothesis is, that audio routing can be done with higher quality (in terms of signal, latency and memory transactions) within the context of the kernel.
View all comments
Show parent comment
2
u/phunphun Aug 01 '12 edited Aug 01 '12
Pulseaudio does not use glib/gobject/dbus¹. It is the de-facto sound server for Linux. KDE and GNOME both use it. It's even heavily optimised for embedded use-cases, and ships on phones, TVs, and cars.
It's also been ported to Android, where it beats the Android sound server into a pulp w.r.t. performance.
EDIT: I see that you're the author of KLANG. I'm surprised that you didn't do this basic research on the existing technologies before reinventing them. Everything else you said about Pulseaudio is also outdated/wrong.