Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

GigaSTT Workbook

Scenario-driven recipes for gigastt, the local Russian speech-to-text server powered by GigaAM v3. Each chapter follows the same shape: scenario → prerequisites → recipe → verifying the result → common pitfalls → links.

This book is a cookbook, not a reference. The canonical references stay in docs/ — the workbook links to them instead of duplicating them.

Documented against gigastt 2.14.x. Prefer resolving the latest release tag in install scripts (gh api …/releases/latest) rather than hard-coding older minors.

I want to…

GoalTimeChapter
First transcript on this machine~5–15 minGetting started
Batch a folder / watch a drop box / async jobs~15–30 minCLI and batch processing
Transcribe PBX / Opus / raw telephony; stereo speakers~20 minTelephony & VoIP
Live captions or a voice bot over WebSocket~30 minStreaming over WebSocket
Ship a macOS / Electron / mobile app~30–60 minDesktop & embedded
Run production with metrics, upgrades, model hot-reload~45 minDeployment & ops
Pick head / INT8 / GPU / pool size / punct / hotwords~20 minModels and backends
Label speakers on mono meetings(in ch.3)Telephony — diarization
Decode an HTTP/WS error code~2 minAppendix A — Error codes
Ship air-gapped / offline~30 minAppendix B — Offline checklist
Install on Windows~10 minGetting started — Windows

Chapters

  1. Getting started — install (macOS/Linux/Windows/Docker/air-gap), first transcription. Beginner · ~5–15 min
  2. CLI and batch processing — CLI, batch, and watch-mode recipes for audio files. Beginner · ~15–30 min
  3. Telephony & VoIP — G.711/G.722/Opus, PBX recordings, stereo split, and diarization. Intermediate · ~20 min
  4. Streaming over WebSocket — real-time transcription over WebSocket (partials, VAD endpointing, session caps). Intermediate · ~30 min
  5. Desktop & embedded — Swift/SPM, sidecar, Electron, UniFFI. Intermediate · ~30–60 min
  6. Deployment & ops — production deployment, monitoring, upgrades, admin reload. Ops · ~45 min
  7. Models and backends — model variants, quantization, execution providers, punctuation/ITN, hotwords. Intermediate · ~20 min

Appendices

The Russian version mirrors this book chapter by chapter.

Documentation map

Full inventory of the documentation in this repository: what each file is and where it lives.

References (canonical — never duplicated in the workbook)

FileContentsFate
docs/api.mdHTTP / WebSocket / SSE API referencestays
docs/asyncapi.yamlAsyncAPI schema for the WS protocolstays
docs/openapi.yamlOpenAPI schema for the REST APIstays
docs/cli.mdCLI reference (serve, download, transcribe, …)stays
docs/architecture.mdArchitecture overviewstays
docs/benchmarks.mdWER / RTF measurementsstays
docs/privacy.mdPrivacy and data-flow statementstays
docs/troubleshooting.mdSymptom → cause → fix tablestays
docs/observability/Prometheus alerts and Grafana dashboard assetsstays

Guides (current)

FileContentsFate
docs/deployment.mdReverse proxy, TLS, systemd, Dockerstays
docs/quickstarts.mdIn-process embedding quickstarts (FFI bindings)stays
docs/runbook.mdOperator runbook for productionstays
docs/self-hosted-runner.mdSelf-hosted CI runners for benchmarksstays
docs/embedding-packaging.mdonnxruntime linking and packagingstays
docs/verifying-releases.mdVerifying release artifactsstays
docs/ane-backend.mdANE (Core ML) backend note — live --features ane codestays
docs/candle-backend.mdCandle/Metal backend note — live --features candle codestays
sdks/go/README.mdGo WebSocket client SDKstays
sdks/js/README.mdTypeScript WebSocket client SDKstays

Historical (archived)

Completed design/plan documents kept for archaeology in docs/archive/:

FileContentsFate
docs/archive/candle-metal-backend-plan.mdCandle/Metal backend implementation plan (completed)archived
docs/archive/candle-metal-backend-design.mdCandle/Metal backend design (superseded by the shipped backend)archived

Rules for contributors

  • The workbook holds recipes; docs/api.md, docs/cli.md, and the AsyncAPI/OpenAPI schemas remain the canonical references. Link to them — do not copy their content.
  • Every command and example in a chapter must be verified before merge.
  • Inside the book (chapter ↔ chapter, chapter ↔ intro) use relative .md links — they work both on GitHub and in the rendered book. Links from the book to repository files (docs/, crates/, …) must be absolute GitHub URLs — relative ones 404 on the published site. No mdBook-specific templating.
  • New chapters follow the _template.md structure.
  • English is canonical. The Russian book (docs/workbook/ru/) mirrors this one with identical file names; both versions are updated in the same PR.
  • When a feature changes the documented surface (CLI flags, error codes, audio formats), update the chapter, the book SUMMARY.md, and the canonical references in the same PR — and keep the docs-drift gate green: python3 scripts/check-docs-drift.py (advisory in CI; it compares CLI flags, WS error codes, audio formats, mdBook TOCs, EN/RU parity, relative links, OpenAPI/SECURITY/crate pins, and workbook version currency + required recipe tokens against the code).