kenarsa

10 ms·

61.
Private voice recognition running locally in browser(picovoice.ai)
4 points by kenarsa 7y ago|1 comments
62.
The Case for Voice AI on the Edge(picovoice.ai)
1 points by kenarsa 7y ago|0 comments
63.
Offline Voice AI on an MCU(youtube.com)
1 points by kenarsa 7y ago|0 comments
64.
NLU on a Microcontroller(youtube.com)
3 points by kenarsa 7y ago|1 comments
65.
by kenarsa 8y ago
This is a really good point. That is why we partially open-sourced our technology to enable unbiased third party evaluation. You can run the exact same demo on a Linux box or Raspberry Pi (any variant) using what's available on the pro
66.
by kenarsa 8y ago
The device you are referring to is quite different. I am taking this is the board you are using? https://www.arrow.com/en/reference-designs/imx6slevk-imx-6so... It was an ARM Cortex-a9 with NEON extension instead
67.
by kenarsa 8y ago
Yes, we will publish an article about our speech-to-intent engine and add a link to it on our website. This should happen before the new year. You can find some information about the wake-word engine here https://medium.com/
68.
by kenarsa 8y ago
Thank you. The engine is definitely domain-specific. This would apply to vocabulary and also inference. For example, if you want to use the tech for smart lighting then you would need a different model/context. The demo is done with so
69.
by kenarsa 8y ago
Thanks a lot for the link. I'll be sure to take a look into it in more detail. Keyword spotting is one of the modules we run in this demo. That's how we detect "Hey Barista". We also run an engine we can "Speech-to-
70.
by kenarsa 8y ago
Pruning is a great idea to reduce memory usage. One thing to be careful with is that pruned matrices use irregular memory access and they might be slower as we don't have SIMD support for sparse matrix multiplication on generic CPU&#x2
71.
by kenarsa 8y ago
Hello. This is Alireza. I am the founder of Picovoice. I totally understand the need to support makers community. We do have GitHub repositories for engines demoed here which allows you to use these technologies to some extent (not the full
72.
by kenarsa 8y ago
You are absolutely right. Compressing (using this for lack of better terminology) is extremely important for power-efficient applications as one of the main power draws on a device is external RAM. We had to come up with a bunch of ideas on
73.
Offline voice AI within 512 KB of RAM [video](youtube.com)
142 points by kenarsa 8y ago|40 comments
74.
Private on-device voice ai(picovoice.ai)
2 points by kenarsa 8y ago|0 comments
75.
by kenarsa 8y ago
two reasons: 1- the business model 2- in some cases, it actually needs some engineering. for example a new brand name, etc.
76.
by kenarsa 8y ago
I suggest doing a quick read on one of the demos (Python for example) that should clear things up. If not you can always open an issue...
77.
by kenarsa 8y ago
Sweet! Go for it!
78.
by kenarsa 8y ago
Agreed. We try to put the price for easy cases. I rather to not put estimates. It probably ends up making customers unhappy.
79.
by kenarsa 8y ago
This is really good feedback. Agreed. What I have seen work is to put common cases. It probably makes our life on Picovoice side easier as answering repeating price questions is not a fun day to spend our time. We will address this soon. I
80.
by kenarsa 8y ago
Numbers and complex words (I am assuming you mean something like "ok blah"?) are doable easily. I am not sure what you mean by unknown words. Could you elaborate? Obviously, you can just grab the audio stream after the phrase is d
81.
by kenarsa 8y ago
Thanks for the feedback :) Hopefully, we find a way to make you like our project!
82.
by kenarsa 8y ago
the project you mentioned is wake-word for ARM only. Great project, BTW. For wake word, we provide on-demand model generation. We do also more than wake word. Finally, we can run on other CPUs/OSs as well.
83.
by kenarsa 8y ago
you are welcome!
84.
by kenarsa 8y ago
Sound classification is in our roadmap in 2019.
85.
by kenarsa 8y ago
Agreed. The reason for not supporting grammar in this product is that we want to keep it extremely lightweight. We do have upcoming products that support grammar as well.
86.
by kenarsa 8y ago
If you have a commercial application we can build you the model for any wake word. Since this requires some engineering work on our side we can only offer it to commercial customers at this point.
87.
by kenarsa 8y ago
The demo is using WebAssembly which is supported by Chrome. It also uses Web Audio API which I believe is again supported by Chrome. I just used the demo on my Android phone using Chrome. I wonder what could be a problem. It the mic on? :)
88.
by kenarsa 8y ago
For speech-to-text right? I provided the quote for voice control engine: https://picovoice.ai/#wake-word-detection The voice control comes in two variations standard and tiny. The tiny one consumes even fewer resources. I p
89.
by kenarsa 8y ago
RPi3 is definitely faster. We also run on RPi 1/zero/etc.
90.
by kenarsa 8y ago
Stay tuned. We will add two more repositories (1) speech-to-intent (2) speech-to-text

More ›