Original title: transcribe.cpp
Article
transcribe.cpp is presented as a ggml-based speech-to-text library built to replace a fragile Whisper-plus-ONNX workflow for cross-platform apps like Handy. The author says the project aims to trustfully run local ASR on Mac, Windows, and Linux by prioritizing speed, verified accuracy, and easy distribution, then opened it as a v0.1.0 release with known rough edges. The library advertises support for 16 ASR families and 60+ models, plus Vulkan, Metal, CUDA, and TinyBLAS acceleration, streaming and batch modes, and first-party bindings in Python, JavaScript/TypeScript, Rust, and ObjC/Swift. The maintainer describes a validation process that includes numerical checks plus WER sweeps versus reference implementations on Ryzen Vulkan and Apple M4 Max hardware, with benchmarks and results published in-repo and on Hugging Face. It is designed as a mostly drop-in replacement for whisper.cpp, including compatibility with whisper .bin files, but with some unsupported flags and features still to be added. The post ties the project to a broader push for private, efficient local inference, arguing that this improves practicality by removing cloud dependency and lowering power budgets for real-time transcription. It includes community-facing transparency on ecosystem support, mentions credits and infrastructure partners, and repeatedly invites community contributions and bug reports for remaining gaps, including model and workflow completeness.
Commenters widely praised the release, noting Handy’s practical value and reporting successful local, near-real-time use cases on older phones and cross-platform desktop needs. They view the library as potentially useful for building broader local AI workflows, including combinations with TTS and document-editing loops. At the same time, several users raised direct implementation questions, especially around speaker separation and speaker identification, and asked about performance questions such as Metal versus Vulkan gaps. Python users confirmed the feature set looks promising but requested a binary wheel path, pointing out that the current package still depends on a separately installed library. Multiple comments stressed long-term sustainability, asking how a mostly one-person project should be funded and maintained. Some asked for clearer positioning versus whisper and whether faster-whisper remains preferable in some GPU scenarios. A few users also said they are waiting for stronger demos and wished for more frontier-model coverage and integration polish.