darknet VS vosk-api

YoloV3/4 is C based if that counts: https://github.com/AlexeyAB/darknet

This is all well-known information, see any (and all!) previous discussions when YOLOv5 comes up. For details: https://github.com/AlexeyAB/darknet/issues/5920

2) YOLOv5 is both slower and less precise than YOLOv4. Why use YOLOv5? Source: https://github.com/AlexeyAB/darknet/issues/5920

So my recommendation is you stuck with Darknet/YOLO and use v4 of YOLO. The Darknet framework license is definitely suitable for commercial use: https://github.com/AlexeyAB/darknet/blob/master/LICENSE

Still to long. Here's my favourite license: https://github.com/AlexeyAB/darknet/blob/master/LICENSE

When YOLOv7 was out, I built a web app to test it against the classic YOLOv4 and shared it with my team, then deployed it online to share with the community.

If you're worried about performance, you shouldn't be using YOLOv5 since it is slower (and less accurate!) than YOLOv4. Source: https://github.com/AlexeyAB/darknet/issues/5920

I looked around online but I only found this post discussing a related issue, leading me to think there seems to be some sort of compatibility issue going on here. And I think this is the most recent version of the file I am trying to compile located on the exact same folder where my copy is and when I opened it it shows CUDA 11.1 in line 307.

It's coming! CMUSphinx used to have something like this, and there are some [1] solutions [2] on the horizon.

[1]: https://github.com/alphacep/vosk-api/issues/55

[2]: https://github.com/outlines-dev/outlines?tab=readme-ov-file#...

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.