Better initial audio device choice on Linux

[bdach]

Continuing a thread from game-side, at least to have something to refer users to in the future.

There have been a few recurring cases with fresh-installing linux users where an unfortunate choice of audio device would stall lazer due to not being able to progress clocks at intro. There's little detail to go on, so it's hard to say for sure, but it does seem to indicate that audio device selection code is somehow flawed and could use some more poking.

It's possible that this is just alsa being alsa (pretending a device is active to BASS but actually not ingesting any audio input), but given that our aim is supporting cross-platform, we might want to have a look at the problem in the long run.

[Jummit]

Still relevant after three years. I think this is a major issue because it results in a clean osu! install to freeze before startup with no clear sign why.

[bdach]

obviously it's relevant. the issue wasn't closed, was it?

the reason why this isn't fixed is that it's not clear as to when or why this happens. i, for instance, cannot reproduce myself, i just saw user reports of it. if you want to be actually helpful, then any assistance in tracking down the cause would be appreciated. passive aggressive "+1" bump comments are not helpful.

[Jummit]

I think letting the game start even if the audio server stalls would be an improvement, as users can then individually figure out sound is not working and try use a different sound server.

For people not being able to start the game looking for a fix: Changing the Audio Device in the config worked for me:

AudioDevice = PulseAudio Sound Server

[bdach]

the best solution would be to choose the correct device from the get go so that sound works.