3 ms·
It is a shame it took so long but it is finally here. The feeling may be similar to when pulseaudio arrived, but it is not the same thing; Pipewire implements e
by marcodiego 5y ago
It is a shame it took so long but it is finally here. The feeling may be similar to when pulseaudio arrived, but it is not the same thing; Pipewire implements everything that is needed; users will no longer need to care about handoff between alsa, pulseaudio and jack. It manages video streams too and the latest version of OBS even makes use of it to allow screen sharing on wayland running from flatpak. Finally!
I've been watching linux since the OSS days. I used oss, alsa, arts, esd, jack, pulseaudio... never it has been looking as well aimed as it is this time. Finally!
- buu700 5y agoI haven't read the article yet, but how big a deal is this? Is this something that distros are likely to adopt on top of or in place of PulseAudio? Does this make any existing part of the Linux audio stack/ecosystem redundant, or is it strictly solving a problem (or problems) that had yet to be addressed?
- necubi 5y agoYes, it replaces PulseAudio and Jack. Its goal is to provide a single audio daemon that can serve both consumer applications (where power consumption is typically most important) and pro applications (where latency is most important). Currently those are served by PulseAudio and Jack, so it's very exciting to have a single service that can cover both use cases. It also replaces part of ALSA, which is two things: the kernel interface to talk to audio devices, and a set of user libraries on top of that interface. PipeWire still uses the former, but has its own, better API for the latter (in addition to supporting ALSA, PulseAudio, and Jack APIs).