-
Notifications
You must be signed in to change notification settings - Fork 2
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
Where is the Annyang lib? #1
Comments
This is not a wrapper around annyang. As the README.md says "This is partial port of the amazing annyang client side library". The thing that has been ported was the phrase routing, not the speech recognition itself. Annyany is dependent on Chrome's speech recognition system, which obviously has not been ported to Node. |
If you would like to help support speech recognition please do. Contribution is always welcome. |
If you think I should republish this module as Additionally, if you want to help me add the features you are looking for I will accept pull requests and add any features I can add. |
I personally believe that I would love to work on the speech recog. bit, but I am not sure I have the time presently to invest in that, if it's not something we can get from a library. I'm not sure where it's built into |
https://docs.npmjs.com/files/package.json But a name that denotes that this only works on Node would be okay with me, which is why I suggested The speech recognition aspect of Chrome streams flac files to Google servers for transcription creation. The actual speech recognition is not built into Chrome. This is what client side annyang uses. We can transcode and send those same files over to Google servers with Node, but a flac converter would have to be installed on the machine using this library. |
Thanks for the clarification(s) @alanjames1987. I think Transcoding would be a fun project. I would like to look into this, but I don't have bandwidth for that undertaking, right now. |
This node module looks like a wrapper around the Annyang library, but the library is apparently not present in your repo.
Did you forget a checkin? If not, could you share how you are running the lib in node process to have the module work as expected?
The text was updated successfully, but these errors were encountered: