Sound glitch using Proton

[Svæltha]

So, I know technically this game has no linux support but this is the only issue I had so maybe it's worth taking a look.
There's something wrong during the self-destruct sequence, the sound mixer gets messed up somehow and play all the voice cues at the same time. This create an awful echo glitch like the one you'd get by putting a micro next to a speaker.
It's still affected by "effects volume" but so are many other sounds, muting that is a double edge solution. I'd consider muting only the SD voicelines a solution if there was a specific setting, unfortunately that's not the case here.

I tried using different versions of Proton or altering the pulseaudio setting, to no positive effect.
Running the game from Debian 10.

[nornware]

Interesting. I suspect that the reason for that is that those sound effects rely om being able to explicitly set the playback position, which I assume isn't supported under Proton.

[Svæltha]

I don't know if it'll help but here's an audio recording of the issue. Over 90 seconds of pure pleasure.
WARNING: harsh noise
https://vocaroo.com/i/s17F3zEa8Pb9

[Svæltha]

Originally posted by nornware:

Interesting. I suspect that the reason for that is that those sound effects rely om being able to explicitly set the playback position, which I assume isn't supported under Proton.

Could I have a few more details about how this was implemented , have you used a specific library or middleware ? I tried to see if I could do something about the issue, fiddling with driver
and wine/winetricks settings, but nothing had any effect so far. I've never seen anybody else complain about the issue, I suspect I might be an edge case.

If it's not too much work could it be possible to implement a way to disable the meltdown announcer voice ? Something like a yes/no switch in the option menu or a -nodoomvoice launch parameter.

[nornware]

Originally posted by Svælther:

Originally posted by nornware:

Interesting. I suspect that the reason for that is that those sound effects rely om being able to explicitly set the playback position, which I assume isn't supported under Proton.

Could I have a few more details about how this was implemented , have you used a specific library or middleware ? I tried to see if I could do something about the issue, fiddling with driver
and wine/winetricks settings, but nothing had any effect so far. I've never seen anybody else complain about the issue, I suspect I might be an edge case.

If it's not too much work could it be possible to implement a way to disable the meltdown announcer voice ? Something like a yes/no switch in the option menu or a -nodoomvoice launch parameter.

The sound code uses the DirectSound interfaces, and those specific sound effects rely on continual calls to SetCurrentPosition(): https://docs.microsoft.com/en-us/previous-versions/windows/desktop/mt708935(v=vs.85)

I'll add an option to disable the voice to my to-do list.

[Svæltha]

Originally posted by nornware:

Originally posted by Svælther:

Could I have a few more details about how this was implemented , have you used a specific library or middleware ? I tried to see if I could do something about the issue, fiddling with driver
and wine/winetricks settings, but nothing had any effect so far. I've never seen anybody else complain about the issue, I suspect I might be an edge case.

If it's not too much work could it be possible to implement a way to disable the meltdown announcer voice ? Something like a yes/no switch in the option menu or a -nodoomvoice launch parameter.

The sound code uses the DirectSound interfaces, and those specific sound effects rely on continual calls to SetCurrentPosition(): https://docs.microsoft.com/en-us/previous-versions/windows/desktop/mt708935(v=vs.85)

I'll add an option to disable the voice to my to-do list.

Thank you very much, it helped a lot, enabling wine's DirectSound support through protontricks fixed the glitch.
Oddly all sounds now have a second of latency, but it's a minor issue and I'll probably find a workaround.

[Svæltha]

Alright so rebooting seems to have reduced the latency a bit, slightly less than half-a-second.
Although it's still noticeable that small issue is much preferable over the absolute ear-rape that was the doomvoice glitch.
If anybody else gets that one , protontricks 357330 dsound

[Svæltha]

Originally posted by nornware:

I'll add an option to disable the voice to my to-do list.

Please do, although I managed to get rid of the glitch, the latency trade-off is something I'd rather not have.

[Afiren]

Thank you so much Svaeltha! The default Proton versions couldn't install the `protontricks 357330 dsound` but after I switched to ProtonGE7.29 and then I could install it without issues, and all the problems were fixed.