4 ms·
Jasper[1] is one such that popped up on HN a while back. I spent a wet weekend getting it going on a Raspberry Pi -- it was quite the effort to get all the mov
by Jedd 9y ago
Jasper[1] is one such that popped up on HN a while back. I spent a wet weekend getting it going on a Raspberry Pi -- it was quite the effort to get all the moving pieces working together.
At the time you had the option of using AWS or Google to handle the voice, or possibly (if you have the time and knowledge) train it up to use a local service - this was gently discouraged by the documentation (it was referenced, but not well explained what it involved).
I believe you can now use Watson to offload the voice to text, too.
But in all those cases you're sending data off-site, which may be a concern. And each of those services has some usage constraints that should be enough to cover household use, but I'm not sure what happens when you start to hit those limits.
[1] https://jasperproject.github.io/ https://jasperproject.github.io/
- digikata 9y agoInside the Jasper documentation, there is some discussion about the configuration of the Speech to text engine. They seem to list 5, 2 of which do not use off-site aids. http://jasperproject.github.io/documentation/configuration/ http://jasperproject.github.io/documentation/configuration/ I don't know if other portions of the code might use off-site access data processing. I wish more projects would create a system block diagram of their software.