This is pretty exciting. There have been loads of stability issues in the past, and it's always nice to see those issues addressed. I like the systemd integration too, that's a nice touch.
At this point, they should just rename it svchost.exe.
This Gentoo Linux user is getting along juuuuuust fine without systemd. :)
Edit: To bring it on-topic: It's a damn shame that PA -apparently- doesn't let you set playback/record device preference lists that let you specify which of the potentially many sound devices in your system should be used when some or many of them are unavailable. It seems that KDE4 and -IIRC- 5 use Phonon to add this on top of PulseAudio. (Or, actually, they add this on top of whatever sound playback system you're using... whether it is JACK, ALSA, PA, or something else. I've never written software that interacts with Phonon, but -from an end-user perspective- it's pretty great.)
I did have a lot of problems with distorted audio on Linux games, but "killall -9 pulseaudio" before starting a game (forcing it to respawn) usually fixes it.
Hai! :D
> I was avoiding PulseAudio on my desktop, but it's feels necessary on a laptop, especially if you use Bluetooth.
You know, I was gonna say "But I had A2DP working JUST FINE with bluez-alsa, and JACK knows about anything that ALSA knows about!"... and then I started digging around and learned that bluez-alsa hasn't worked since BlueZ 4.x. :/ [0]
Guess I have another project in my queue. :P Hope I can get it in-tree without too much hassle.
[0] I guess that tells me how long it has been since I've paired a Bluetooth headset with my laptop! ;)
Good luck, i can't say i have my hopes up.
Because of its political nature, this is a topic that's best not discussed unless you have some very specific questions or observations, and you are already very well informed about the merits and faults of both the systemd project and most of the other pieces of software that provide similar functionality. :)
Agreed. Emphasis on pieces of software, plural.
Sound on linux is a mess. And pulse audio is vastly blamed for it. Complex circonvoluted architecture that overpromised and under delivered..
The guy loves to brag about how he is the messiah of a problem and will fixt it, make galaxy like software that are unstable and leave a mess after his doing saying my job is done, let's work on another project where my genius is needed.
But, after utterly messing up once, notably at the (lack of) design level, he has been entrusted to no overpromise again and make the ultimate revolution for the init process. A lot of coders did not believe in his repentance for the mess in pulse audio : he may be as arrogant as linus torvalds he is as smart and a good coder as rasmus lerdorf.
The PID1 on linux is now known as a solar system of processes with nice chaotic trajectories and astronomers are seriously planning to use systemd alone as a nth body interaction simulator.. unexpected .
I experience about zero problems. Maybe it's because I don't run pulseaudio.
That said, at its core Pulseaudio depends on ALSA for the hardware handling.
Frankly the only useful thing Pulseaudio does it handle inputs and outputs when dealing with multiple sound devices. But then so does JACK.
Everything else, from volume control (hello hearing damage with default settings) to bit rate mangling, is massively superfluous.
The main reason that does come up that's not really a non-reason (but, I should note, is hard for me to validate as a dispassionate neutral observer) is a fear that systemd is being rammed down users' throats against their wills, partly by distros deciding "there's no alternative" and partly by systemd incorporating ever more tools.
For example, more recent versions of upower are just a wrapper around logind. Thus to have a laptop sleep when you close the lib, you need to replace your init process.
Do that in any way sound sane?
./configure --help
SYSTEMD_LIBS
linker flags for SYSTEMD, overriding pkg-config
I'm not sure what discussion you think we're having, but the conversation that was present ~four hours prior to your comment appears to be largely on-topic, informative, and civil. :)