Benchmarks
Current provider results for Mumbli’s speech-to-text engines. Last updated: June 3, 2026TL;DR
Pricing was checked on June 3, 2026 from the official Groq pricing, ElevenLabs API pricing, and Deepgram pricing pages. Provider pricing changes; use the latency and quality results below as the durable part of the benchmark.
Current STT benchmark
We benchmarked the latest 50 saved Mumbli recordings: 896 seconds of real dictation, ranging from 0.9s to 90.7s per clip.
Conclusion: ElevenLabs remains the best default transcription engine for quality. Deepgram Nova-3 is reliable and often faster than ElevenLabs, especially on longer clips, but it did not beat ElevenLabs on judged quality and sometimes returned empty text on very short clips. Groq is still the fastest option by far and remains the right engine when low latency matters more than exact wording. Interfaze worked reliably, but it is too slow for the current app pipeline.
Quality judging used the original WAV audio when possible: 45 files used audio judging, 2 fell back to text-reference judging, and 3 very short clips were skipped because one provider returned empty text. Saved
.txt files were treated only as historical app transcripts, not ground truth.
Raw data is retained locally in benchmarks/results/raw.json for rejudging. It is not published because it contains recording-derived transcripts.
Engine configurations
Future optimizations
Methodology
- Python benchmark harnesses (
benchmarks/bench.py,benchmarks/interfaze_groq_bench.py) usinghttpxasync HTTP client - WAV recordings captured via Mumbli’s debug mode
- June 2026 STT comparison used 50 real recordings, 1 STT call per provider per file, and an audio-aware judge
- Benchmark harness output is written to
benchmarks/results/; recording-derived raw JSON is kept local - All benchmarks are reproducible from source
Custom vocabulary accuracy
Tested 11 commonly mistranscribed words (proper nouns, technical terms):
See Custom Vocabulary for details.
Archived local experiments
Older chunking, polishing-model, and end-to-end experiments are kept in the repository underreports/ and benchmarks/results/. They are useful for implementation history, but this page reflects the current provider choice.