Skip to content
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

Separate Passive/Active STT Engines #32

Open
GetGoodKid opened this issue Jan 16, 2015 · 0 comments
Open

Separate Passive/Active STT Engines #32

GetGoodKid opened this issue Jan 16, 2015 · 0 comments

Comments

@GetGoodKid
Copy link

I haven't found much documentation about having separate STT engines for passive/active mode.

It seems ideal to have a simple/offline STT (e.g. Sphinx) passively listen for a programmable wake-up word (e.g. "Jasper"). Then it would active listen using a different STT such as Google Speech API. There could be separate passive/active fields in the profile.yml file.

Correct me if I'm wrong, but it seems Jasper currently uses the same STT for both passive and active listening?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant