fix: 🐛 Make VAC default; soft-fix microphone issues #2861
Merged
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.
Not long ago I thought of completely replacing the microphone support on Windows with just Virtual Audio Cable, as it seems to be actually working, while VB Cable doesn't sometimes (it doesn't work when just installed, it requires a system restart, but better go with the more robust solution).
In this PR I keep VB Cable and VoiceMeeter as second options still. If after user testing VAC results stable and reliable, should I go ahead and make it the only preset option? (I would still allow for custom audio devices by substring)