You are not logged in.
Pages: 1
Hello! I want to reset all ALSA settings, but I wouldn't know how.
I was looking for ways to boost the audio beyond what's allowed in PulseAudio (audio started working at first-run days only and exclusively when I installed that), and I came across this configfile.
I don't recall any asound.conf being in my /etc/ folder prior to this. I did make the max_dB value much higher (wayyyyyyy higher), and I stuffed that in /etc/asound.conf, then rebooted.
Obviously, the audio now clips obligatorily. An unexpected side effect is that every time an audio source starts playing (Chromium, in this case, playing a YouTube video), it waits a few seconds in mute and fades in the sound, which is bothersome because when I pause the video for too long, once I unpause it, the video keeps playing during the seconds it's still silent.
I thought removing asound.conf and rebooting would fix the issue, but it's still the same after a restart. Additionally, I recall trying to delete /var/lib/alsa/asound.state, removing/purging (pacman -Rddn) alsa-lib to reinstall it again, and rebooting. It still persists, however. Maybe I did try to set max_dB at 0.0, but my memory's foggy.
Please help?
Last edited by PuppyFromLosAndes (2024-11-05 18:12:51)
Offline
I might have solved it. I used another OS in a live environment to get rid of the asound.state, and for good measure the ~/.config/pulse folder.
It no longer waits/fades-in the sound, so that's good. But as to whether it no longer clips, I wouldn't know, since the laptop's speakers already blew up from all the messing with volume settings. That doubt will remain unanswered for a good while, but I can't do much. Again my fault.
Last edited by PuppyFromLosAndes (2024-11-04 20:49:36)
Offline
FWIW, pulseaudio is technically limitless without messing with this. While most GUIs will default to a max of 150 there's no technical limitation to this, and you can just use
pactl set-sink-volume @DEFAULT_SINK@ 400%
if you so wish. And that will be the much better approach than fiddling with ALSA configs when the majority of your stuff isn't going to route over ALSA anyway.
If this is technically [SOLVED] please mark it as such by editing the title in your first post, might have to shorten it a little.
Offline
Pages: 1