Re-enable WASAPI by default#15195
Merged
Merged
Conversation
michaelDCurran
approved these changes
Jul 26, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Reintroduces #14697
Closes #10185
Closes #11061
Closes #11615
Summary of the issue:
WASAPI usage should be reenabled by default on alpha so wider testing can occur
Description of user facing changes
WASAPI is re-enabled - refer to #14697 for benefits
Description of development approach
change feature flag default value to enabled
Testing strategy:
Alpha testing
Known issues with pull request:
#15150 is a known issue with WASAPI
Change log entries:
refer to diff
Code Review Checklist: