Turned off browser auto gain control (AGC), more in doc #16
Conversation
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
…etection for low user volume plus a bit of logging
Owner
|
Thank you for the PR, Steven. I will need to do more research and testing on this, and come back to you later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
also added a bit of detection for low user volume plus a bit of logging.
I was having problem when running the app. It turned out that in my environment (MacOS, Chrome), somehow the previous browser AGC logic causes the recorded volume to be very low, and thus failing the OpenAI transcription request.
Please evaluate whether it is sensible to turn of the browser AGC. More explanation is in the newly added doc. Also feel free to remove some of the newly added logging if they are more verbose than necessary.
Thank you.