epd_display VS vosk-api

Plugins can display any content you want and the structure is open and we'll documented. Check it out here: https://github.com/txoof/epd_display

https://github.com/txoof/epd_display for anyone searching for a written link

I opened an enhancement ticket here.

PaperPi runs on Raspberry Pi OS Buster or Bullseye and supports almost every EPaper Screen WaveShare sells from the 2" monochrome to 10" HD grayscale right out of the box with a simple setup, configuration easy use.

I use PaperPi to show what's playing.

I've been working on a modular e-paper display loop called PaperPi. It's written in Python and supports configurable modules with different layouts. The layout automatically scales the plugin contents to the dimensions of whatever waveshare screen you attach.

Well. Now im Going to need to update my PaperPi to use these great looking HD screens. I can't wait to dig into your code and learn how you do this magic.

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.