Files

T

debpalashandClaude Fable 5 933743e336 fix: resolve open issue batch — #1172 #1173 #1174 #1185 #1186 #1188

- validate managed binaries before exec; 0-byte GGUF placeholders fail
  actionably instead of "Exec format error" (#1172)
- KittenTTS: tokenizer-measured chunking to the ONNX 512-token cap;
  clear 400 for unspeakable input (#1173)
- clean SIGTERM during weight load: shutdown-aware loader, benign
  cancelled-load classification, lifespan hardening, scoped log
  silencers (transformers load + alembic fileConfig) (#1174)
- broken ASR deep-imports (lightning_fabric) mark the engine
  unavailable with a repair hint and fall through (#1185)
- uv cache + managed Python follow the chosen install drive on
  Windows (cherry-picked cross-drive class fix + spaces/D: tests) (#1186)
- adaptive silence-removal ladder for quiet clone references; localized
  actionable error for truly silent clips, all 21 locales (#1188)
- CHANGELOG: consolidated Unreleased into the quiet one-liner style

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-19 04:29:33 +05:30

omnivoice-tts-darwin-arm64

feat(engines): real synthesis "Self-test" + copy-paste setup snippet for opt-in engines (#930 )

2026-07-03 17:02:08 +05:30

omnivoice-tts-darwin-x86_64

Phase 4 Plan 04-01: SPIKE-01 GGUF — GO + integration (#100 )

2026-05-20 17:51:31 +05:30

omnivoice-tts-linux-x86_64

Phase 4 Plan 04-01: SPIKE-01 GGUF — GO + integration (#100 )

2026-05-20 17:51:31 +05:30

omnivoice-tts-windows-x86_64.exe

Phase 4 Plan 04-01: SPIKE-01 GGUF — GO + integration (#100 )

2026-05-20 17:51:31 +05:30

README.md

fix: resolve open issue batch — #1172 #1173 #1174 #1185 #1186 #1188

2026-07-19 04:29:33 +05:30

README.md

Bundled binaries

This directory holds platform-specific binaries that ship inside the OmniVoice Studio installer. Today:

File	Built from	Purpose
`omnivoice-tts-darwin-arm64`	`ServeurpersoCom/omnivoice.cpp` @ pinned SHA	GGUF inference runtime — Apple Silicon
`omnivoice-tts-darwin-x86_64`	same	Intel Mac
`omnivoice-tts-linux-x86_64`	same	Linux
`omnivoice-tts-windows-x86_64.exe`	same	Windows
`checksums.sha256`	computed by `scripts/build-omnivoice-tts.sh`	SHA-256 manifest — verified by `OmniVoiceGGUFBackend.is_available()`

The pinned commit SHA for omnivoice.cpp lives in backend/engines/omnivoice_gguf/quant_map.json _meta.runtime_commit_sha.

Building locally

scripts/build-omnivoice-tts.sh --platform <slug> --commit-sha <40hex>

See .github/workflows/ci.yml build-omnivoice-tts job for the CI matrix that produces these artifacts on every PR. The Apple Silicon slot (macos-14) is marked continue-on-error: true because the upstream omnivoice.cpp README does not publish a buildmetal.sh (Pitfall 1 in 04-RESEARCH.md); a failed Metal build is documented and the macOS Apple Silicon cloning default falls back to the in-process OmniVoiceBackend.

Placeholder note

Until the CI matrix produces real binaries, this directory contains zero-byte placeholders — a plain git clone always gets those (real binaries ship via the installers / CI artifacts, and are never committed here). OmniVoiceGGUFBackend.is_available() validates the file before trusting it (services/binary_preflight.py: non-empty + a real Mach-O/ELF/PE magic, #1172) and returns (False, "...not a usable executable...") for a placeholder, so the engine reports honestly through the Engine Compatibility Matrix and the default selection falls back to the in-process OmniVoiceBackend. Selecting the engine anyway (e.g. model: "omnivoice-gguf" on /v1/audio/speech) yields an actionable 400/503 naming scripts/build-omnivoice-tts.sh, never a raw "Exec format error".