Hello, In the Message; Subject : Re: Found better customizing way! Message-ID : <CAA91j0W5cJ9NSr7kav4GmQkM+WpS_cb2fmyRgqdgMSVsKtuy8Q@mail.gmail.com> Date & Time: Thu, 3 Oct 2024 10:18:03 +0300 [AB] == Andrei Borzenkov <arvidjaar@gmail.com> has written: AB> On Thu, Oct 3, 2024 at 10:08 AM David C. Rankin <drankinatty@gmail.com> wrote: DCR> > $ ps axf | grep pulse DCR> > 6510 ? S<sl 0:00 \_ /usr/bin/pipewire-pulse DCR> > DCR> > There is no pulse-audio running. There are pulse audio packages: DCR> > DCR> > $ rqa pulse DCR> > libpulse-devel-17.0-4.4.x86_64 DCR> > libpulse-mainloop-glib0-17.0-4.4.x86_64 DCR> > libpulse0-17.0-4.4.x86_64 DCR> > pipewire-pulseaudio-1.2.4-1.1.x86_64 DCR> > pulseaudio-setup-17.0-4.4.x86_64 DCR> > DCR> > But there is nothing pulse enabled in systemd, e.g. AB> You apparently misunderstand pipewire architecture. The pipewire AB> *server* replaces the pulseaudio *server*. Pipewire never aimed (at AB> least, to my best knowledge) at replacing the *client* part. Clients AB> do speak pulseaudio protocol with pipewire server, like they do speak AB> jack protocl with pipewire server. This is actually quite a valuable AB> feature of pipewire - it is a drop-in replacement that does not AB> require you to modify every existing program. [...] You are entirely correct. One of the main features of pipewire is its support for pulseaudio, jack, alsa and gstreamer, which is implemented via pipewire-pulseaudio, pipewire-libjack, pipewire-alsa and gstreamer-plugin-pipewire. I think David is lucky because he doesn't use software that only supports alsa. In fact, there are no pipewire-alsa installation dependencies set. Incidentally, kmix uses Pulseasdio, not alsa. Best Regars. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "During testing, Sakana found that its system began unexpectedly attempting to modify its own experiment code to extend the time it had to work on a problem." -- Research AI model unexpectedly attempts to modify its own code to extend runtime (ars TECHNICA) --