If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The FUNDAMENTAL flaw in PulseAudio

PulseAudio may be the greatest thing since sliced bread in many respects, but here is one place where it FAILS TOTALLY:

From their web site:

---

You are expected to know your way around if you use system mode. You are using PA against the explicit recommendations of the maintainers, so don't expect particularly enthusiastic support from them in doing so.

---

HELLO! They should put PulseAudio EVERYWHERE. It should be in your TV and your headphones and your speakers and your MP3 player. I have NO IDEA how PulseAudio is going to succeed if the developers have this DUMB mind-set.

PulseAudio may be the greatest thing since sliced bread in many respects, but here is one place where it FAILS TOTALLY:

From their web site:

---

You are expected to know your way around if you use system mode. You are using PA against the explicit recommendations of the maintainers, so don't expect particularly enthusiastic support from them in doing so.

---

HELLO! They should put PulseAudio EVERYWHERE. It should be in your TV and your headphones and your speakers and your MP3 player. I have NO IDEA how PulseAudio is going to succeed if the developers have this DUMB mind-set.

PulseAudio may be the greatest thing since sliced bread in many respects, but here is one place where it FAILS TOTALLY:

From their web site:

---

You are expected to know your way around if you use system mode. You are using PA against the explicit recommendations of the maintainers, so don't expect particularly enthusiastic support from them in doing so.

---

HELLO! They should put PulseAudio EVERYWHERE. It should be in your TV and your headphones and your speakers and your MP3 player. I have NO IDEA how PulseAudio is going to succeed if the developers have this DUMB mind-set.

in system mode it runs as a system level daemon instead of a user level process. This allows it to accept connections from multiple users (without handing sound between multiple PA instances) but introduces security issues and the like. It is meant for embedded or single user systems, and is strongly discouraged for general desktop use.

in system mode it runs as a system level daemon instead of a user level process. This allows it to accept connections from multiple users (without handing sound between multiple PA instances) but introduces security issues and the like. It is meant for embedded or single user systems, and is strongly discouraged for general desktop use.

If you've ever looked at the pulse.conf files, its under the flag "daemonize." WebOS ran Pulse in "system mode" and I always had the impression (still have my HP Touchpad, Fire Sale model) that THATS why the Audio was so flaky because Pulse on desktop is fine but Pulse in system mode is a mess. Not sure why they ever ran it in system mode either... because you didnt run WebOS as root unless you turned on developer mode so a normal pulse setup shouldve been fine.

Moving on from that odd diversion (PA doesn't seem to be "failing totally" so far, and it's not like development has stalled), I wonder why the article summary includes the word "debated"? Seems like a wealth of adjectives could have been used there, and I thought we as a community were beyond blaming all issues on (Ubuntu's terrible implementation of) Pulseaudio?

Show me some other free software for GNU/Linux that lets me seamlessly and independently flip different audio streams between headphones, bluetooth and network audio devices with a nice GUI and I'll legally get "Pulseaudio Sucks" tattooed across my forehead. Until then, calling it names seems a little pointless…

If you've ever looked at the pulse.conf files, its under the flag "daemonize." WebOS ran Pulse in "system mode" and I always had the impression (still have my HP Touchpad, Fire Sale model) that THATS why the Audio was so flaky because Pulse on desktop is fine but Pulse in system mode is a mess. Not sure why they ever ran it in system mode either... because you didnt run WebOS as root unless you turned on developer mode so a normal pulse setup shouldve been fine.

Not at all - the system mode shouldn't make any difference to the sound quality. It's simply that running in that mode is a bad idea for security reasons, and you shouldn't do it unless you know what you're doing. For the case of an embedded device, system mode is probably the right thing to do, since most of those security issues are less applicable on a specialised device.

i dunno

Perhaps your English is not so good! Can you tell the difference between "making an observation" and "volunteering for work"?

You know that software like PulseAudio has security issues, and so it needs to be updated regularly?

If you patch up PulseAudio so you can embed it in your device, now you have a patch that needs to be maintained. If you sell a device that embeds PulseAudio, now you have added complication to your software update process and your users are going to be vulnerable for longer.

If you want your product to achieve market penetration you need to make it EASY for your code to propogate, not HARD.

Besides the PulseAudio developers would find their work to be EASIER if they supported a wide range of platforms because they will be will be talking to other copies of PulseAudio instead of whatever Apple is using and whatever Google is using and whatever samsung is using etc.

Yes indeed it is possible to open the hood and look at the engine and make observations and your name does not need to be John DeLorean or Ferdinand Porsche. It is indeed possible for potential users of product to decide "this mess is not worth my time" and they can only do that by looking with a critical eye.