vosk-browser VS dicio-android

Not the OP but I've been tinkering with the same concept (24/7 processing).

'm using vosk browser: https://github.com/ccoreilly/vosk-browser

To do speech to text locally and it works very well for English.

I believe this is called the Bergamot project, more can be found here: https://browser.mt/

The GitHub repo for it is here: https://github.com/browsermt/bergamot-translator

The repo contains some details about how to run it in WASM which is quite interesting for embedding it in pages. I've been playing around with using WASM to capture speech to text (https://github.com/ccoreilly/vosk-browser) and automatically translating it using Bergamot.

Results have been, ok. I don't think the tech is quite there yet and the speech to text obviously struggles with multiple speakers.

So perhaps it's a good day to call for contributors to add more actions to https://github.com/Stypox/dicio-android ? If Google wants to remove features, they can be replaced by something that doesn't have that problem.

I've just discovered Dicio, a promising voice assistant and speech-to-text app that is pure FOSS. I'd love to use the apps's speech-to-text capabilities system-wide. Reading through the Github page of the app tells me that this is possible.

Dicio is the onl one I know. Since version 0.8 it can be used as a general SST engine from any app (didn't test it personally tho)

Dicio (version Placeholder): Voice assistant: multilanguage, configurable and free

You can use open source assistant instead like Dicio https://github.com/Stypox/dicio-android and configure it the way you like.

Check it here

Hey! Best thing I know of at the moment is Dicio made by some of the same people behind NewPipe.