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.
2.1 KiB
Support
Where to get help
| Channel | Best for |
|---|---|
Discord — #help |
Setup problems, quick questions, sharing results |
| GitHub Issues | Bugs and feature requests — use the templates; attach the diagnostic bundle (Settings → About → "Save diagnostic bundle") |
| GitHub Discussions | Design questions, ideas, show & tell |
| Security issues | Never a public issue — see SECURITY.md for private reporting |
Uninstalling / removing all data
VoiceStudio is fully local — there's nothing to deactivate, just folders to
delete. scripts/uninstall.sh (macOS/Linux) or scripts\uninstall.ps1
(Windows) lists every VoiceStudio folder with its size (dry-run first) and
removes them on --yes. The complete per-platform path list is in
docs/install/uninstall.md.
Model sources we support
VoiceStudio is built on the idea that everything it runs is open and available to everyone: free, public models with verifiable sources and licenses (Hugging Face repos, official project releases), so the whole community can use, test, and debug the same thing.
We do not support privately sold, paywalled, or gated model files. A model delivered privately can't be verified, reproduced, or shared — it doesn't fit the project's goals, and issues involving such models will be politely closed. As a general safety rule, never run executables bundled inside any model archive.
Before filing a bug
- Update to the latest release (or
mainif you follow previews) — fixes ship continuously. - Run the in-app self-check: Settings → About → Run self-check.
- Search existing issues; add a 👍 + your details to an existing one rather than opening a duplicate.
Response expectations
This is an open-source project maintained with the help of an automated triage bot: issues are typically triaged within hours and every report gets a human- approved response. Reproducible reports with a diagnostic bundle get fixed fastest.