I’ve got an update for y’all. When I change the output from digital surround 7.1 to digital stereo and back in system settings>sound, the problem goes away until a reboot or perhaps even a logout.
can you try set pipewire / pulseaudio with a specific EQ like 44.4 khz or 48khz
i had issue long time ago , the sound would start “crackling” more and more until it was only noise
at first only rebooting would fix the issue
then i had to remove pulseaudio and switch to alsa with dmix to fix the issue
then i found by forcing pulseaudio to a specific EQ it would solve the problem
do you have another sound output with it 's own DAC does it do the same issue?
By EQ you mean sample rate I guess. No idea how to do that. Messing around in alsa config?
My 7600x cpu has an onboard gpu. Same problem when I switched back to it last week. Perhaps a amdgpu driver problem combined with pipewire-pulse?
i did in pulse audio config file but here it is pipewire i guess
I believe that pipewire-pulse is the compatibility layer for programs that do still uses pulseaudio to function. For example most webbrowsers.
Would you mind sharing your pulseaudio config file?
i lost it i don’t need it anymore for now ,
44400 or 48000 for example , you have to restart the deamon
but it should be something like this , you add for example: in file
/etc/pulse/client.conf or in your own file /home/{user}/.config/pulse/client.conf
default-sample-rate = 44400
page_module_protocol_pulse with pipewire
because it use pipewire with pulse layer i guess the config file is with pipewire
Did not solve it.
previous snapshot not working is weird
i guess the only way to avoid those wierd issue in linux is to use a computer like tuxedo with there tuxedoOS you have QA so it should work 99.99% time 
maybe you could try turn off pipewire and try direclty with alsa but you need to set dmix…
and also you need to use a script"apulse" to fake pulseaudio output to firefox for example
what is your soundcard ? realtek ? speaker/headphone with dac?
for pipewire-pulse.conf you could try but again likely the issue is something else
pulse.fix.rate = 48000
i dont know if firefox use pipewire directly ? vlc?
To much hassle. I use hdmi output 7800xt.
Probably uses pulseaudio through pipewire-pulse. The flatpack version doesn’t output sound when disabling pulseaudio in flatseal, thus enforcing pipewire. Same goes for chromium and librewolf.
Probably due to separate home partition that’s being unaltered.
1 Like
I’ve got an update for y’all. When I change the output from digital surround 7.1 to digital stereo and back in system settings>sound, the problem goes away until a reboot or perhaps even a logout.
Its possible, my fedora installation which uses an older version has no problems (on the same hardware)
I still have the issue btw, despite everything being update to date and having rebooted multiple times.
Will have a look tonight if it is fixed on my end.
1 Like
Still not fixed. Toggling output devices in system settings is still the workaround. Would be nice if a Suse dev or admin would shed some light on this problem. At least identify for certain what the cause is. Underlying audio technologies such as pipewire can’t be the problem since there where multiple updates released since the start of this topic. On the AMD side there where also kernel updates so I’m at a bit of a loss. I wonder if a fresh install would result in the same problem.
Since this is my gaming rig I’m planning to do a kde install as it is supposed to have better freesync support.
Greetings
SUSE Developers and/or Administrators don’t have anything to do with openSUSE, unless they’re working on the project on their own time.
If you really want to get openSUSE Developers input on the issue, I would suggest sending a message to openSUSE Factory - openSUSE Mailing Lists or possibly joining #opensuse-factory:opensuse.org on matrix, or #opensuse-factory on irc.libera.chat, and asking there.
There are the odd developers that participate on the forums, but generally hoping that they see things here on the forums and just decide to work on things mentioned here, just isn’t going to happen.
After the monthly update a few days ago the problem still exists.