PipeWire progress report - JACK, ALSA and PulseAudio back-ends nearly complete! The future of Linux multimedia production is already looking brighter.
please, o please, Pipewire, finally put an end to the mess we call "linux sound subsystem".
> PulseAudio back-ends
So it'll be PipeWire on top of PulseAudio on top of ALSA?
Sounds like XKCD pic about standards.
i figure it totally depends how this will be done and implemented and how buggy it will be. i hope gnome will not be a dependecy etc. i'm wary of anything that's connected to red hat and gnome. pulse audio was a mess for quite a while.
i love separation (and compatibility) between jack (PRO!) and ALSA (average user). on the other hand it would be great if everything would *just work* low latency and talking to each other blahblah. so, i cheer for this!
@openmastering @unfa @dump_stack not sure.. pipewire devs recommend using the same (pulse/jack) APIs we do right now. I guess because not everyone is going to have pipewire installed, but they are going to have pulseaudio and/or jack.
But from a developer's perspective, JACK API is very simple yet allows to do a lot, so I do not see enough of a reason to directly use pipewire APIs since the custom pipewire libjack is staying with us for the long-term.
So pipewire would just be a kind of glorified bridge between end user protocols (jack & Pulse audio)?
I really hope that it transforms into a unified thing where users can have it all: low latency, patching, video, levels etc. Adding a complexity layer just in order to bridge services is questionable.
@unfa I saw that PipeWire packages are already on Manjaro Stable repos, is this already working??
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!