3 ms·
Like I get that PulseAudio was unreliable for many years that fostered hate for it but it's absolutely crazy that people say that it's useless. You need someth
by Spivak 5y ago
Like I get that PulseAudio was unreliable for many years that fostered hate for it but it's absolutely crazy that people say that it's useless. You need something to collect sound streams from applications and mics, mix them, transform them, and output them to a bunch of different kinds of hardware with different requirements. Like Pipewire is fantastic but it's just a more reliable PA.
- BiteCode_dev 5y agoYes, it was a necessary endeavor, but the implementation never lived up to the task. I'm glad Pipewire is now getting traction, as I fear PulseAudio will never be able to be the stable and robust solution we need for audio on Linux. Particularly, it handles badly sleep modes, hot plugging sources, and BT, which in 2021 is not acceptable. I regularly have to set things up manually using pavucontrol. But yes, we needed it, and I thank the people that tried.
- handrous 5y ago> Like I get that PulseAudio was unreliable for many years that fostered hate Unreliable, and a shocking resource hog. Did that part ever get better, or did we just stop caring because memory sizes and core counts kept going op?
- jatone 5y agoneither, when pulseaudio was built there where problems all up and down the stack. from the kernel, alsa, and userspace. the effort around pulseaudio stabilized and resolved most of the problems in the kernel and alsa. leaving most of the problems in the implementation of pulseaudio. pipewire is now building off that giant amount of work pulseaudio effort resulted in and is able to reuse pulseaudio's IPC framework to seamlessly replace pulseaudio itself.
- heavyset_go 5y agoI stopped caring because PipeWire works well and ships as a drop-in replacement for PulseAudio and Jack by default.
- PaulDavisThe1st 5y agoIt's not quite a drop-in replacement for JACK yet, but I have very little doubt that it will get there.