protonscr

Launching BeatSaber via Proton causes Audio Issues

steamvrclosed
ValveSoftware/SteamVR-for-Linux#559 · opened 2023-01-26 by jqlifice · updated 2023-01-26 · 2 comments · github
Jjqlifice 2023-01-26 github

System Details:
Ubuntu 20.04.5 LTS 64Bit
Amd Ryzen 5 3600
B450 GAMING PLUS MAX (MSI)
RTX 2070 Super (asus dual fan)
(Audio driver: pulseaudio 13.99.1)

When selecting the Valve Index (which also does not show up as Index HMD in outputs, but rather DisplayPort4, while showing up as Index HMD in inputs) and running the Gnome Audio Tests (Settings > Sounds > Device > Test) I get clear audio.
When launching into the Steam Home the audio apears to be fine aswell (there is only ambient noise so it was kinda hard to tell, but I sounded clean)
The moment I launch BeatSaber through Proton 7.0-5 the audio starts crackeling and generating static noise, as well, as distorting the actually played sound. When alt-tabbing while in beat saber and running the audio test again I get the same static noise. After quitting SteamVR reopening it and testing again before launching BeatSaber again the audio is once again fine, yet proceeds to break again after launching BeatSaber. I therefor concluded that this is an issue with Proton and not the Index/SteamVR.

If you need any further information like logs, I will happily provide them!

Kkisak-valve maintainer 2023-01-26 github

Hello @jqlifice, the symptoms you've described sounds much more like pulseaudio re-configuring the audio feed going to the Index, and pulseaudio is letting it get configured to something that isn't usable. When you close and re-open SteamVR, that resets the HMD audio chip's configuration.

I'm not very familiar with troubleshooting this type of issue, but maybe checking pacmd list-sinks (from #175) would reveal a difference before and after the game is run?

As a blind guess, maybe give the workaround at https://github.com/ValveSoftware/SteamVR-for-Linux/issues/215#issuecomment-526791835 a try and see if it has an effect.

Jjqlifice 2023-01-26 github

Yup the suggested workaround fixed it, thank you very much! @kisak-valve

Proton versions