picovoice VS vosk-api

Download the Picovoice Unity package

Picovoice Platform GitHub Repository

Below are some useful resources: Open-source code Picovoice Platform SDK Picovoice website

git clone --recurse-submodules \ https://github.com/Picovoice/picovoice.git

You can use the demo code we open-sourced. It includes wake word and context files, so you can start with them.

You can check out the GitHub repo to see more open-source demos

Although interestingly enough, the README for the linked repo (https://github.com/Picovoice/picovoice) states that "The SDK is licensed under Apache 2.0 and available on GitHub to encourage independent benchmarking and integration testing." While source isn't provided and only compiled binaries are provided, that should give you permission to flip some bits to skip a license check.

Checkout https://github.com/Picovoice/picovoice I saw it on an article from before and it seemed easy to get started on.

Check out an article I wrote about it and the source code

So I don't know if my issue comes from my lack of knowledge of discord.js/voice or VOSK. so I guess the most important thing I need to see is if I am creating a proper stream for the Vosk API to capture the audio. if I can figure out how to capture an audio stream I can probably import that in to vosk and figure out how to use vosk myself. but right now I can't even get close! Thank you in advance...Sorry if this isn't the right place for this

I remember a while ago checking out the issues with Vosk speech recognition (written in C). A handful of it's issues are related to segfaults and null pointers.

first, good initiative! thanks for sharing. i think you gotta be more diligent and careful with the problem statement.

checking the weather in Sofia, Bulgaria requires cloud, current information. it's not "random speech". ESP SR capability issues don't mean that you cannot process it locally.

the comment was on "voice processing" i.e. sending speech to the cloud, not sending a call request to get the weather information.

besides, local intent detection, beyond 400 commands, there are great local STT options, working better than most cloud STTs for "random speech"

https://github.com/alphacep/vosk-api

I did a one-off text to speech tool for someone last year and had pretty good results with VOSK. One upside is that it works offline, although I imagine if you use TTS a lot you'll notice issues I didn't.

You can use vosk-api (https://github.com/alphacep/vosk-api) to listen to your audio, transform it to text, and then post the text to GPT-3, then using the vector sdk, have your responses said by vector.

The set up script wants to download https://github.com/alphacep/vosk-api/releases/download/v0.3.45/vosk-model-en-v0.3.45.zip, but this resource is not found. AFAICT all releases never contained a model file. Remedy: hardcode one model from https://alphacephei.com/vosk/models. I guessed and picked the one with the closest name, vosk-model-en-us-0.22.zip, just so I could continue.