Sounds to me like maybe the sample rate is changing away from what your application expects (44.1 vs. 48 kHz). I used to have this problem with Pulse quite often, but I don’t remember if I fixed it before switching to PipeWire.
Pulse has a “preferred sample rate” setting in its config files, but it seems to only really be a suggestion, and Pulse tends to ignore it.
So, how do I force it to use a particular sample rate? Cuz I think the streams are 44.1KHz (as is with most audio) and if it speeds up, the sample rate should be set to 48KHz if my logic serves me correctly.
This is just a temporary fix, I’ll switch to PipeWire as soon as I can, I just wanna do some work in my workshop and listen to music…
I think defining the default and alternative sample rate mostly solved the problem, the other settings were just in case, I didn’t check if it worked with or without them.
Not really, sorry, but it reminds me of a timeout. Something trying to load something from a service not responding. I’d check if one of the components is trying to reach a server which is unresponsive and if DNS resolution is ok. Sometimes delays occur if a wrong DNS server is configured and the system uses a fallback DNS when the primary one is unresponsive. Or an applet trying to access a resource which is not available. E.g. trying to show free space of a drive which is not mounted.
Oh, right. I downloaded it from voidbuilds so didn’t visit that page. I couldn’t find anything in the void documentation ( docs.voidlinux.org/installation/…/index.html ) so I tried duckduckgo which led me to reddit.
voidlinux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.