The default maximum latency was reduced from 170ms to 42ms. This should
improve overall latency for application that ask for a large latency,
such as notifications.
max-quantum is now also scaled with the rate. A new quantum-limit property was added as a hard limit for the quantum. This makes it possible to configure for larger than 8192 buffer sizes. Note than many JACK applications have a hardcoded 8192 limit. (#1931)
The max-quantum was reduced to 2048, This gives a 42ms default latency. (#1908)
I could wait until the new pipewire release but then Iād have that crackling until then of course. What packages do I need to downgrade so I can get pipewire working to when it didnāt stutter for the meantime?
I mean Iād like to keep using pipewire, this is the only problem Iām having with it and I hope it will be resolved. I can either downgrade or remove the pipewire I have and replace it with the git versions. If I did that would it work immediately after a reboot or?
I experienced that tooā¦but there was an update to something in pipewire system at the time (donāt remember what), so easily explainable. Glad to see someone else got it
I downgraded to 0.3.43 today and found it was MUCH worse. like 20 times worse. I downgraded to 0.3.42 and it was the same. (I couldnāt downgrade pipewire-jack to anything below 0.3.43 though)
I have no idea what I should do
Iāve upgraded to 0.3.44 again and it still persists but isnt as bad as the other versions.
I have however learned something important.
The audio stuttering in OpenSpades only occurs when cmus is opened while itās running. If Iām listening to my music and then open OpenSpades thereās no issues. same for if Iām running cmus, start openspades, then close cmus and re-open it. So it only happens if cmus is started while openspades is running.
Edit: All of this applies to Audacious as well
I think for now the best solution is to just start cmus before starting OpenSpades until thereās a new PipeWire release and (HOPEFULLY) it will be fixed.