It always takes about one second to start any sound after staying silent for a little while. I managed to figure out it was a power savings mode putting the service to sleep and not waking up fast enough, for pulse it seems to be as easy as to change a true for a false to a power savings option inside a config file, I guess that in pipewire is the same but I couldn’t find the option, that line probably needs to be added somewhere and I’m not sure where and what to write exactly.
The part about the muted notifications was because all the sounds shorter than one second end before the thing wakes up.
Thank you!
It always takes about one second to start any sound after staying silent for a little while. I managed to figure out it was a power savings mode putting the service to sleep and not waking up fast enough, for pulse it seems to be as easy as to change a true for a false to a power savings option inside a config file, I guess that in pipewire is the same but I couldn’t find the option, that line probably needs to be added somewhere and I’m not sure where and what to write exactly.
The part about the muted notifications was because all the sounds shorter than one second end before the thing wakes up.
Looks like this is a common enough issue:
https://wiki.archlinux.org/title/PipeWire#Noticeable_audio_delay_or_audible_pop/crack_when_starting_playback
When in doubt, look into the Arch and Gentoo wikis they have good information that’s usually applicable to you even if you’re not using them (mostly).