Hello, In the Message; Subject : Re: We pipewire users can EASILY get better sounds! Message-ID : <20240925210856.915fa1bf4af383eb15b6da65@trixtar.org> Date & Time: Wed, 25 Sep 2024 21:08:56 -0400 [BTF] == bent fender <slowroller@trixtar.org> has written: BTF> Wed, 25 Sep 2024 16:51:19 +0900 BTF> Masaru Nomiya <nomiya@lake.dti.ne.jp> : MN> > I just listen to music. MN> > BTW, isn't this helpful? MN> > https://www.reddit.com/r/linuxaudio/comments/1eqni5i/pipewire_is_surprisingl... BTF> Not really :-) BTF> It just tells me how impressed some users were with pipewire two years BTF> ago I think it was only recently that the person recording started to evaluate pipewire, right? If you use pipewire for recording, I think it's better to use this pipewire, don't you? https://download.opensuse.org/repositories/home:/X0F:/branches:/multimedia/o... Some of its features include: * Capture and playback of audio and video with minimal latency; * Real-time Multimedia processing on audio and video; * Multiprocess architecture to let applications share multimedia content; * GStreamer plugins for easy use and integration in current applications; * Sandboxed applications support. [...] MN> > I don't use an audio interface. BTF> With a musical instrument it's necessary (or so I'm told) and in any BTF> event since I use an effects board and since it is already an audio BTF> interface as well, that question doesn't really arise. If you install lv2-gxplugins-0.9-2.54.x86_64.rpm, you may be happy using the GX-100. MN> > Does “pulse control panel” mean pavucintrol (or pavucontrol-qt)? BTF> pavucontrol MN> > If it's pavucontrol, when you select MIC under Input Devices, is the MN> > Mic recognized? BTF> Yes MN> > If it is, there shouldn't be a problem, right? BTF> Right, but there is: I cannot hear it unless I launch Audacity and BTF> start recording. There was a Leap version that needed no other BTF> intervention, but I stopped using Leap when its future became BTF> uncertain. IT was doing it the way it should be done and I think it BTF> was the only distro to do so. This means that pipewire does not recognize the microphone, and the microphone is recognized via pulseaudio, which is called when Audacity is started. How about this? 1. $ mkdir ~/.config/wireplumber $ mkdir ~/.config/wireplumber/scripts $ mkdir ~/.config/wireplumber/scripts/monitors 2. $ cp /usr/share/wireplumber/scripts/monitors/alsa.lua ~/.config/wireplumber/scripts/monitors 3. edit ~/.config/wireplumber/scripts/monitors/alsa.lua --- alsa.lua.orig 2024-09-26 15:16:03.144780625 +0900 +++ alsa.lua 2024-09-26 15:17:05.531345910 +0900 @@ -23,6 +23,7 @@ function applyDefaultDeviceProperties (properties) properties["api.alsa.use-acp"] = true + properties["api.alsa.use-ucm"] = true properties["api.acp.auto-port"] = false properties["api.dbus.ReserveDevice1.Priority"] = -20 end 4. $ systemctl --user daemon-reload $ systemctl --user restart pipewire pipewire-pulse wireplumber Best Regards. --- ┏━━┓彡 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) --