-
Notifications
You must be signed in to change notification settings - Fork 228
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
Any plans to support Mozilla Deepspeech STT #513
Comments
XD, there is no end at adding a new STT or TTS. Even if kalliope already support a lot of different one, there is always a new issue to add a new one :). |
OK, I'll have a look into that |
Is there anything other than sphinx for STT that is open source? It seems the rest are all cloud services |
The only one self hosted so far. |
I'm starting to work on implementing Mozilla DeepSpeech and Mozilla TTS when I get Mozilla TTS to run at all |
Cool! Are you facing any issues with the deep speech side? I could put up a server for that. |
@OmegaRogue Any progress ? |
I would like to bring everyone's attention to this post and more importantly to this one. @Sispheor would you consider such a change ?
Do we need to make a PR for it ? |
Replacing a well known lib by a 2 stars fork? |
The problem is that well known lib https://github.com/Uberi/speech_recognition is not maintained anymore. Pull requests are not accepted. Last commit was 2 years ago. Many important technological advances are not implemented. |
Ok. Switching to a fork could be a good idea. But the owner of this particular one is saying himself that he has no experience on this. |
@Sispheor, one of the two stars is from me so I guess this is a one star fork. |
I tried for a few days to get DeepSpeech working, but didn't make any progress at all, so I gave up on it, maybe I'll try at some point |
here is an example of streaming transcription from microphone in python with deepspeech |
Is anyone working on or planning to support https://github.com/mozilla/DeepSpeech as a STT in kalliope?
The text was updated successfully, but these errors were encountered: