plaidml VS vosk-api

basically agree with all of this, however I do want to highlight that there is no 'ZKML protocol plan' - the panel here are all involved in quite different projects and interested in ZKML for a variety of reasons. As one of the authors of https://github.com/plaidml/plaidml I'm not expecting any kind of standard protocol to evolve for several years; the group behind the AMA though is optimistic about the potential of ZKML and this AMA is part of the start of developing useful protocols.

It understands my Swedish attempts at English really well with the medium.en model. (Although, it gives me a funny warning: `UserWarning: medium.en is an English-only model but receipted 'English'; using English instead.`. I guess it doesn't want to be told to use English when that's all it can do.)

However, it runs very slowly. It uses the CPU on my macbook, presumably because it hasn't got a NVidia card.

Googling about that I found [plaidML](https://github.com/plaidml/plaidml) which is a project promising to run ML on many different gpu architectures. Does anyone know whether it is possible to plug them together somehow? I am not an ML researcher, and don't quite understand anything about the technical details of the domain, but I can understand and write python code in domains that I do understand, so I could do some glue work if required.

Have you tried PlaidML https://github.com/plaidml/plaidml

This doesn't answer your question, but it would be cool if we had something based on MLIR for GPU compute. From what I've read, it closes the gap between NVIDIA and other GPU vendors a lot more than pure compute shaders. e.g. ONNX-MLIR, PlaidML, and IREE.

There is a library called PlaidML which is supposed to support Keras on a wide variety of GPUs, including the Iris. But it doesn't. I get the issue reported as Issue #168, which was first reported in 2018 and is still open. That's what I mean by not well supported.

Not really: https://github.com/plaidml/plaidml/commits/plaidml-v1

There are reports on github of plaidML conking out on older CPUs with a similar "illegal instruction err.

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.