Hi everyone, I have pipewire pulse, but I can’t seem to stop the crackling audio, and the Bluetooth distance is very low. I didn’t have these issues before installing pipewire. Initially, I thought the high CPU usage, possibly due to Steam, was causing the problem. However, after disabling shader caching, which reduced CPU usage by 30%, I am still experiencing issues. None of the playback codecs I’ve tried have fixed the problem. Here are my specs and the logs that I believe could be helpful. I’m new to Linux, so please be patient and feel free to request any additional information you may need. system specs dmesg journal
I’m a bit confused. This is a new install, and you manually installed pipewire? To my knowledge endeavourOS defaults to pipewire.
What were you using before then and did you do anything custom during the install to not install pipewire?
Hi, so I had PulseAudio on my previous Debian install and did not have this issue; the Bluetooth was able to go at least across the house without crackles or popping.
Sorry I was asking more along the lines of how did you install endeavourOS without installing pipewire? What led to you having to install it manually?
I used the graphical installer, and I’m saying that I never had issues like this on my previous Debian install. Sorry for the confusion.
I also have an additional log for you if that helps; it is my pipewire journal. I don’t really know what a lot of it means, but I still see an old output called Elgato which I removed several days ago…pipewire journal
My 5 cents: There’s so much crazy going on in the logs between the Sure mic, the Razer headphones, the Apple headphones, the Elgato thingy … that I would just unplug every USB audio device, remove every Bluetooth device, and then slowly adding back observing when things stop working or start spamming the logs with messages.
The only USB audio device I currently have installed is the Shure mic. I no longer have anything else USB-wise plugged in, just a Bluetooth connection to the Apple headphones. Is there a better way to clean the logs, you can suggest? The pipewire logs were posted just before I uploaded to mediafire I did the journalctl | grep pipewire > pipewire-journal
command to get the logs.
Also we have related discussion [1] which reminds me. Afair debian only ships with the SBC bluetooth codec because the other codecs are proprietary. So if you experience BT crackling on EOS the issue might be that other codecs are used which provide “better quality” but are susceptible to fail in difficult wireless environments.
I just plugged in my Ethernet cable, and I am still having issues. I definitely have SBC selected in my codec, and I tried both high fidelity and non-high fidelity settings for Bluetooth.
It might be totally unrelated to your specific problem but I solved a crackling problem a while back by adjusting gain in alsamixer. Gain should be 00.
https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture
From Wiki:
" The MM label below a channel indicates that the channel is muted, and OO indicates that it is open.
Scroll to the Master and PCM channels with the Left and Right keys and unmute them by pressing the m key.
Use the Up key to increase the volume and obtain a value of 0 dB gain. The gain can be found in the upper left next to the Item: field."
I’m looking at the wiki and have opened ALSA Mixer. I see the item labeled “Master” in the top left, but there are no gain values. When I use Pavucontrol and set the gain to 0, the issue persists. In fact, I don’t even see the Apple headphones listed in the sound card options when I try to select a sound card, so I just set it to default. I would take a screenshot, but my Flameshot isn’t working either, haha…
The next thing I tried was to turn off power management. I noticed I didn’t have wireless tools installed, so I installed that. Afterward, I turned off network power management, but I am still experiencing crackling. I only got the power mangement idea because of this thread.