-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Kaldi is too fast #36
Comments
Try vad_padding_end_ms in kaldi_module_loader_plus.py. I myself have set it to 200ms up from 100 to avoid this problem. |
Yeah, adjusting |
@daanzu where do these parameters sit in the |
They are engine parameters for dragonfly, so they are set in the |
@daanzu i think the calls in Caster are https://github.com/dictation-toolbox/Caster/blob/master/castervoice/lib/ctrl/mgr/engine_manager.py and https://github.com/dictation-toolbox/Caster/blob/master/castervoice/lib/ctrl/configure_engine.py @LexiconCode do you know how we might expose this option in Caster? |
Yep it's something I've been trying to think how the best implement. |
dictation-toolbox/dragonfly#302 may help until Caster has a good way to pass engine parameters. |
Just modify the bat file for now List of kaldi engine parameters for configuration. |
I know that this is a very good problem to have! Several times (at least since the last update) I have found Kaldi will interpret my speech well before I'm done uttering a phrase. For example, in Caster we can say "go line sixteen" to navigate to line sixteen.
Sometimes the system will interpret this as "go line six" then interpret "teen" as something completely different as Kaldi almost always trys to interpret any real speech. For me, I get "teen" interpreted as "doon" (my word for page down), for example.
Is there a setting we can tweak to prevent this from happening?
The text was updated successfully, but these errors were encountered: