-
Notifications
You must be signed in to change notification settings - Fork 452
Expose experimental WASAPI support as a user config toggle #6659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
smoogipoo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks okay to me but I haven't tested yet.
|
Should I be concerned we're initialising the bass device 4 times? My concern here is one of these 4 initialises potentially going in without the wasapi experimental flag. |
I've brought this up before. Not sure it's any worse with this PR. I think it's worth investigating since IIRC initialising bass is slightly time consuming. |
|
I did some additional investigation into the initialization issue, and it appears to be somewhat misleading. The InitBass function performs a preliminary check before doing any actual initialization work, so the logs can give the impression that initialization occurred even when it didn’t. osu-framework/osu.Framework/Audio/AudioManager.cs Lines 409 to 410 in a6692e6
This highlights two related issues:
|
No description provided.