wtay

5 ms·

1.
by wtay 2y ago
It's a reimplementation of a pulseaudio server and a reimplementation of the jack client library. See https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ...
2.
by wtay 2y ago
1. PulseAudio needed a redesign, there was no fixing to be done. It was utterly impossible to support low-latency audio, the protocol was not right, the client API was wrong, the backend was not right etc.. Also, ALSA is the wrong place to
3.
by wtay 2y ago
> but if you keep changing things that don't need changing (ALSA -> PulseAudio -> pipewire -> whatever is already in the works to replace pipewire) instead of ACTUALLY FIXING THEM This is possibly the dumbest thing I read i
4.
by wtay 4y ago
Awesome plan!
5.
by wtay 4y ago
Hi, I'm maybe one of those moronic retards you talk about. Please, please help us out! The world is eagerly awaiting your super non-garbage solutions. Please show us the way... You could be a hero!
6.
by wtay 4y ago
People like to use the pulseaudio API because it has features people want, compares to ALSA or JACK: See here: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ...
7.
by wtay 4y ago
OSS relies on mixing in the kernel, which is bad for reasons explained here: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ... Also with OSS you still can't seamlessly switch between d
8.
by wtay 4y ago
The answer is, surpisingly maybe, no. JACK (and PipeWire) manage to add features without adding any latency to what ALSA can provide. Will it consume more CPU? yes, it does...
9.
by wtay 5y ago
Yes, you need to uninstall the PulseAudio server, it is not used anymore. PipeWire implements its own pulseaudio server that talks to PipeWire.