Isio
Isio
UBUniversal Blue
Created by Isio on 3/15/2025 in #🛟bazzite-help
Guild Wars 2 : brief audio glitch on certain actions
Update : I forgot to mention there is also a small graphical hiccup/frame drop at the same time of the audio hiccup. I tried to change CPU scheduler (I tried all available) by changing it in /etc/default/scx and then sudo systemctl start scx (or restart) -> No improvement
3 replies
UBUniversal Blue
Created by Isio on 3/1/2025 in #🛟bazzite-help
Sound issue (latest stable)
------------------------- I also found this post : https://github.com/ublue-os/bazzite/issues/2348#issuecomment-2716135421 So I used this conf, and the issue is gone for now !
context.properties = {
default.clock.allowed-rates = [ 48000 ]
}
context.properties = {
default.clock.allowed-rates = [ 48000 ]
}
(all of that still valid for version 41.20250314) (Note : I will also post another issue I think is unrelated)
4 replies
UBUniversal Blue
Created by Isio on 3/1/2025 in #🛟bazzite-help
Sound issue (latest stable)
update : since PULSE_LATENCY_MSEC was fixing the issue for me, I tried to play with these parameters (so I would not need to set PULSE_LATENCY_MSEC for each game) :
context.properties = {
default.clock.rate = 48000
default.clock.quantum = 1024
default.clock.min-quantum = 128 # Alone or with other parameters
default.clock.max-quantum = 2048
}
context.properties = {
default.clock.rate = 48000
default.clock.quantum = 1024
default.clock.min-quantum = 128 # Alone or with other parameters
default.clock.max-quantum = 2048
}
and also
pulse.properties = {
pulse.min.req = 128/48000
pulse.default.req = 1024/48000
pulse.min.frag = 128/48000
pulse.default.frag = 1024/48000
pulse.default.tlength = 1024/48000
pulse.default.maxlength = 2048/48000
pulse.min.quantum = 1024/48000
}
pulse.properties = {
pulse.min.req = 128/48000
pulse.default.req = 1024/48000
pulse.min.frag = 128/48000
pulse.default.frag = 1024/48000
pulse.default.tlength = 1024/48000
pulse.default.maxlength = 2048/48000
pulse.min.quantum = 1024/48000
}
With no luck, the issue was still happening. With
pw-top
pw-top
, I noticed that when the crackling was present, another device that the one I was using as sound output was set to a different frequency rate and had a growing ERR count (alsa_output.pci-0000_01_00.1.hdmi-stereo vs alsa_output.pci-0000_06_00.0.analog-surround-21 the one I use)
4 replies