OpenVoiceOS STT HTTP Server
Turn any OVOS STT plugin into a micro service!
Install
pip install ovos-stt-http-server
Companion plugin
Use in your voice assistant with OpenVoiceOS companion plugin
Configuration
the plugin is configured just like if it was running in the assistant, under mycroft.conf
eg
"stt": {
"module": "ovos-stt-plugin-deepgram",
"ovos-stt-plugin-deepgram": {"key": "xtimes40"}
}
Usage
ovos-stt-server --help
usage: ovos-stt-server [-h] [--engine ENGINE] [--port PORT] [--host HOST]
options:
-h, --help show this help message and exit
--engine ENGINE stt plugin to be used
--lang-engine LANG_ENGINE
audio language detection plugin to be used (optional)
--port PORT port number
--host HOST host
--lang LANG default language supported by plugin (default comes from mycroft.conf)
--multi Load a plugin instance per language (force lang support, loads multiple plugins into memory)
--gradio Enable Gradio Web UI
--cache Cache models for Gradio demo
--title TITLE Title for webUI
--description DESCRIPTION
Text description to print in UI
--info INFO Text to display at end of UI
--badge BADGE URL of visitor badge
Note:
ffmpegis required for Gradio
eg ovos-stt-server --engine ovos-stt-plugin-fasterwhisper --lang-engine ovos-audio-transformer-plugin-fasterwhisper
Docker
you can create easily create a docker file to serve any plugin
FROM python:3.7
RUN pip3 install ovos-stt-http-server==0.0.1
RUN pip3 install {PLUGIN_HERE}
ENTRYPOINT ovos-stt-server --engine {PLUGIN_HERE}
build it
docker build . -t my_ovos_stt_plugin
run it
docker run -p 8080:9666 my_ovos_stt_plugin
Each plugin can provide its own Dockerfile in its repository using ovos-stt-http-server
Metadata
Release files for ovos-stt-http-server 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ovos-stt-http-server-0.1.4.tar.gz | 524.1 kB | Without provenance | Details for ovos-stt-http-server-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ovos_stt_http_server-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for ovos_stt_http_server-0.1.4-py3-none-any.whl |
Total release size: 1.0 MB
Release files / ovos-stt-http-server-0.1.4.tar.gz
| Download URL | ovos-stt-http-server-0.1.4.tar.gz |
|---|---|
| Size | 524.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
139ec80831d2f759b7d31f21578e4ada6086a5afd4bca85c8dab7adce1823513
|
|
BLAKE2b-256 checksum How to use checksums |
ee4bebcd938cef86e742d97bde19d7eb27602d1f5dbc91c6c1af456328fdd6c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Release files / ovos_stt_http_server-0.1.4-py3-none-any.whl
| Download URL | ovos_stt_http_server-0.1.4-py3-none-any.whl |
|---|---|
| Size | 523.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1cc055e2a81988d6e86829a8f40743239ff2f006270ead4efbbe928f52655857
|
|
BLAKE2b-256 checksum How to use checksums |
05507cd4356181d3c5044904a892db4c67ecc7c67c02b060c9481d04196ff7ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for ovos-stt-http-server 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.