On Thu, Oct 3, 2024 at 10:08 AM David C. Rankin <drankinatty@gmail.com> wrote:
On 10/2/24 10:55 PM, Andrei Borzenkov wrote:
03.10.2024 05:09, David C. Rankin wrote:
Nope, I'm 100% pipewire on Tumbleweed and happy with it.
$ ps axf | grep wire 6508 ? S<sl 0:00 \_ /usr/bin/pipewire 6509 ? S<sl 0:00 \_ /usr/bin/wireplumber 6510 ? S<sl 0:00 \_ /usr/bin/pipewire-pulse
If you are using 100% pipewire, what "pipewire-pulse" does here?
No clue - Tumbleweed did that on it's own... And frankly, I'm not sure why:
$ ps axf | grep pulse 6510 ? S<sl 0:00 \_ /usr/bin/pipewire-pulse
There is no pulse-audio running. There are pulse audio packages:
$ rqa pulse libpulse-devel-17.0-4.4.x86_64 libpulse-mainloop-glib0-17.0-4.4.x86_64 libpulse0-17.0-4.4.x86_64 pipewire-pulseaudio-1.2.4-1.1.x86_64 pulseaudio-setup-17.0-4.4.x86_64
But there is nothing pulse enabled in systemd, e.g.
You apparently misunderstand pipewire architecture. The pipewire *server* replaces the pulseaudio *server*. Pipewire never aimed (at least, to my best knowledge) at replacing the *client* part. Clients do speak pulseaudio protocol with pipewire server, like they do speak jack protocl with pipewire server. This is actually quite a valuable feature of pipewire - it is a drop-in replacement that does not require you to modify every existing program. So, returning to the original question that triggered my remark - are you sure kmix in your case is using native pipewire and not pulseaudio or anything else? Because as long as pipewire-pulse is active, you cannot be claiming 100% pipewire for every client.