Hello, In the Message; Subject : Re: why pipewire-pulseaudio Message-ID : <60772b1c-36e9-0032-bafa-101222d1686b@earthlink.net> Date & Time: Thu, 3 Oct 2024 06:01:19 -0400 [FM] == Felix Miata <mrmazda@earthlink.net> has written: FM> Masaru Nomiya composed on 2024-10-03 18:11 (UTC+0900): [...] MN> > I think David is lucky because he doesn't use software that only MN> > supports alsa. MN> > In fact, there are no pipewire-alsa installation dependencies set. FM> It used to be not so long ago in KDE3 Sound System configuration, FM> the selections were: FM> 1-Autodetect FM> 2-Jack Audio Connection Kit FM> 3-No Audio Input/Output FM> 4-Open Sound System FM> 5-Threaded Open Sound System FM> That was changed to popping up an angry notice that only FM> autodetect is possible, and the select list only offers FM> Autodetect. At least, that's how it was before there existed FM> Pipewire and Wireplumber. How is one supposed to determine what FM> Autodetect detected? I think the only way to find out is to look at the source code of the software used. In other words, audacious and audacity are developed using pulseaudio, but in the pipewire system, playback is done at 192KHz, which exceeds the limit of the pulseaudio system (48KHz). MN> > Incidentally, kmix uses Pulseasdio, not alsa. FM> Which KMix is that? AFAIK, David is a KDE3 KMix user, not KDE6, FM> like me. And, what about when pipewire-pulseaudio is installed, FM> so that pulseaudio cannot be? Ah, I see. By the way, what about the answer to my questions? Best Regards & Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --