This kinda stems from this issue I asked about a while back, Pipewire an PulseAudio have caused me quite a bit of confusion lately as I recently started experiencing crackling/static sounds from my Bluetooth speaker when playing audio.
After days of digging and thinking that I’ve fixed the issue by editing /usr/share/piperwire.conf and /usr/share/pipewire-pulse.conf and following guides like this one (I know the link is for EndeavorOS) I have seem to come to the conclusion that Pipewire-ALSA is the issue to the crackling/static sounds I’m hearing.
I stumbled upon qpwgraph which appears to visualize the flow and when I disconnect Pipewire-ALSA from the flow the cracking sounds stop, now from my understanding Pipewire and PulseAudio cannot coexist which is causing my confusion because Pipewire-ALSA also appears to connect to a bunch of PulseAudio Volume Controllers.
I've run into the crackling problem recently as well. I think the ALSA module is improperly requesting a very low quant value causing applications to have a tiny audio buffer which they fail to keep filled, resulting in crackling.
To see if this is what's happening, try running pw-top and see if the quant column is a small number (~200). This is a very short audio buffer, it'll be low latency but if the source application can't keep the buffer filled then you will get the crackling effect. You can increase this value by setting a global minimum with:
It will set the audio buffer to 1024/48000 seconds (or .0434s, 43.4ms). It will introduce a bit of latency (you can decrease the quant to 512 for ~20ms if you need lower latency).
This will not persist past a reboot, you'd have to edit a config file for that (pipewire.conf, maybe?).