transcribe-cpp
Safe, idiomatic Rust bindings for transcribe.cpp, a C/C++ speech-to-text library built on ggml.
Status: in development (0.0.1). Core model, session, run, stream, cancellation, backend, and family-extension APIs are implemented and tested.
Install
The native library is compiled from source by the transcribe-cpp-sys crate, so
a first build needs a C++ toolchain and CMake. There is no external
compression dependency (the deflate codec is vendored), so no system zlib /
vcpkg setup is required on any platform. No prebuilt download and no environment
variables on the happy path.
Quickstart
use ;
let mut session = load?.session?;
// pcm: 16 kHz mono f32 in [-1, 1]
let result = session.run?;
println!;
# Ok::
Runnable examples:
The raw FFI layer is
transcribe-cpp-sys; this crate
is the safe wrapper.
Backends
Backends are selected with cargo features forwarded to transcribe-cpp-sys:
metal (default on Apple), vulkan, cuda, and openmp.
The default link is static and self-contained. Advanced packaging modes are
available through shared and dynamic-backends; see the transcribe-cpp-sys
README if you need runtime-loaded backend modules or custom
TRANSCRIBE_CMAKE_ARGS.
Packaging a distributable (shared / dynamic-backends)
With the default static build there is nothing to do — the native code is
baked into your binary. But if you enable shared or dynamic-backends, your
installer must ship the runtime libraries (and, for dynamic-backends, the
backend modules) next to your executable. Bundling for distribution (e.g. a
Tauri/Electron installer) happens at build time, so a runtime lookup is the
wrong tool — you need the artifact path while you build.
This crate forwards the native build's output directories to your build
script as DEP_TRANSCRIBE_CPP_* env vars. The one you usually want is
DEP_TRANSCRIBE_CPP_RUNTIME_DIR: a single directory holding the shared objects
to copy beside your exe (the DLLs on Windows, the .so/.dylib on Unix — no
per-OS logic needed). Also available: DEP_TRANSCRIBE_CPP_LIB_DIR,
_BIN_DIR, _MODULE_DIR (the dynamic-backends modules), and _INCLUDE_DIR.
The runtime keys are present only in a shared posture; in a static build they
are unset (nothing to bundle).
In your application's build.rs:
use ;
Threading
-
ModelisSend + Syncand cheap to clone (Arc-backed); the native model is freed only after the last handle and everySessiondrop. -
SessionisSendbut notSync; mutating calls take&mut self. -
In 0.x the C library allows at most one in-flight run across all sessions of a model; this crate enforces it with a per-model mutex, so concurrent calls queue rather than race. For real parallelism, use one
Modelper worker. -
License: MIT