-
Notifications
You must be signed in to change notification settings - Fork 245
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
WASAPI driver reorganization #839
WASAPI driver reorganization #839
Conversation
…aller process context
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.
Ok, this looks pretty good already. Thank you! I have two points:
- The unit tests are failing. For a possible reason, see below.
new_fluid_wasapi_audio_driver2
should wait until the synth thread has finished basic initialization, before returning the audio driver to the caller. On my laptop, WASAPI always fails because the default sample rate 44.1 khz is not supported by my soundcard. Previously, fluidsynth was exiting correctly with error. Now, it just stays open doing nothing. So, if the synth thread fails before it enters thefor(;;)
loop,new_fluid_wasapi_audio_driver2
should return NULL.
fixed new_fluid_wasapi_audio_driver2 waiting until the initialization or the synthesis thread has finished
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.
I've tested it and it works as expected. Thanks! I have one point though:
…imeout for the start event to 1000 ms
…e wait timeout for the start event to 1000 ms" This reverts commit 81c139c.
Kudos, SonarCloud Quality Gate passed!
|
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.
I made some tiny changes. Sorry for the confusion. I'll wait for the CI to complete and then I'll take it. Thanks!
Avoid initializing COM in the caller's thread context.
See also: #833