Update README.md (mic delay after awake.wav) #121
Conversation
This file contains 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
|
I agree, i manually set to 0.1 due to my « to fast responding sentence » after wake word |
|
could you specify how you did that? |
|
@B4rtLB if you're running this on docker, you'd accomplish this by passing the flag/value of: |
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.
--mic-seconds-to-mute-after-awake-wavbeing 0.5 by default was the single biggest factor into why I thought Whisper wasn't processing my text to speech correctly. Not complaining, just wanted to highlight it might be good for users to know this is defaulted to a large pause before speaking, so they don't fall into my same mistakes. I assume "after-awake-wav" means after the .wav file is completely played, right? Changing this to 0.1 really helped me, but obviously there are many use cases, not just my own.