Files

T

Palash Debnath 5cab8e0149 feat: rename the product to VoiceStudio (previously OmniVoice-Studio)

Renames what users see. The app, the installers, the window title, the
docs and all 21 locales now say VoiceStudio, with "(previously
OmniVoice-Studio)" noted near the title of each doc surface so people
recognise it.

Deliberately NOT renamed, because renaming any of them silently breaks
an existing install — there is no legacy-path fallback anywhere in this
codebase:

  - bundle identifier com.debpalash.omnivoice-studio (MSI UpgradeCode,
    macOS TCC grants, managed venv, WebView localStorage, the
    single-instance lock)
  - data directories OmniVoice / .omnivoice and omnivoice.db
  - the ~150 OMNIVOICE_* environment variables
  - the X-OmniVoice-* HTTP headers (a wire protocol)
  - the published Docker image paths
  - the OmniVoice ENGINE, which is a model name and not this product

tests/test_identity_paths_survive_the_rename.py pins every one of those
so a future well-meaning sweep cannot orphan a user's library.

Linux .deb users install a new package name and should apt remove
omnivoice-studio; that note is in the changelog.

2026-08-07 01:30:58 +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

feat: rename the product to VoiceStudio (previously OmniVoice-Studio)

2026-08-07 01:30:58 +05:30

README.md

Bundled binaries

This directory holds platform-specific binaries that ship inside the VoiceStudio 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 `VoiceStudioGGUFBackend.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 VoiceStudioBackend.

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). VoiceStudioGGUFBackend.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 VoiceStudioBackend. 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".