> I think the long term plan is for Pipewire to replace PulseAudio
No that's not it at all. It's a framework that will use Pulseaudio OR Jack. Jack is only for low latency needs AKA Professional audio production.
"Pipewire is used to build a modular daemon that can be configured to: be a low-latency audio server with features like pulseaudio and/or jack.
What about that quote makes it seem like it will use pulse audio or JACK rather than acting as a replacement for them?
Checked on their Freenode channel. They are looking at not total replacement but will replace certain features.
Thanks for the heads-up, that is indeed useful and interesting to know .. hadn't heard much of it, but I suppose its because A) my Linux DAW is rock solid and I don't need to change it much, and B) I'm an iOS/AVFoundation developer by day-job, so this is not on my radar as much as it should be. Therefore, I'm quite grateful for the introduction to Pipewire; its going to make a very interesting, Monday-morning/train-ride read .. ;)
Re:PulseAudio under the hood
by throwaway2048 on Friday September 22, 2017 @11:22AM
(#15312969)
cant wait for another 10 years of broken linux audio.
Why not fix what we have rather than yet another rewrite with all its attendant exciting bugs.
For 15 years, I've had a totally stable, rock-solid, perfect Audio environment on Linux. My main DAW is Linux-based, and completely stable. Best latency of any platform, to boot.
So, just as a counterpoint, I'm guessing you're a Pulseaudio user ..
You probably won't have to. I think the long term plan is for Pipewire to replace PulseAudio (and be an alternative to JACK). Pipewire also does video. The initial release of Pipewire is video only with audio support to come:
https://blogs.gnome.org/uraeus/2017/09/19/launching-pipewire...
http://pipewire.org/
https://github.com/PipeWire/pipewire