Vosk Configuration Support
See original GitHub issueIt would be nice to have better Vosk support built into the Docker image. In order to get Vosk support to work, I had to take the google required logic out of the file: jigasi/rootfs/etc/cont-init.d/10-config and modify the sip-communicator.properties template to include:
org.jitsi.jigasi.transcription.customService=org.jitsi.jigasi.transcription.VoskTranscriptionService
org.jitsi.jigasi.transcription.vosk.websocket_url=ws://172.31.52.35:2700
Rebuilt image and used that
Issue Analytics
- State:
- Created a year ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Vosk Installation - Alpha Cephei
The easiest way to install vosk api is with pip. You do not have to compile anything. We currently support the following platforms:...
Read more >Vosk Speech-to-Text - Voices | openHAB
Configuring the model. Before you can use this service you should configure your language model. You can download it from here ...
Read more >VOSK-API Speech to Text (STT) Setup in iPBX 2020/2021 ...
EDITED: 10/24/2022 - update vosk-asterisk configure.ac patch EDIT: 10/27/2022 - add compile ... 4) Check the service and start the docker.
Read more >VOSK Speech Recognition Toolkit - OpenBenchmarking.org
VOSK supports speech recognition in 17 languages and has a ... OpenBenchmarking.org metrics for this test profile configuration based on 419 ...
Read more >Vosk speech recognition tutorial
Vosk server is an open source speech recognition server which supports ... Text from VOSK is all lower-case, while the user configuration can...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
done: https://github.com/jitsi/docker-jitsi-meet/pull/1343
I think we can infer it, it the other gcloud variables are set, can’t we?
The rest sounds good to me! How about you open a PR and we can discuss any details there?