* docs(install): per-OS install pages + drift validator + CI gate
Splits the 600-line README install section into self-contained per-OS docs
under docs/install/{macos,windows,linux,docker}.md plus a Top-10
troubleshooting index. Each OS doc is end-to-end: a user opens it and
reaches a working app following only commands inside that file.
Adds:
- docs/install/{macos,windows,linux,docker}.md (OS-specific install paths)
- docs/install/troubleshooting.md (top 10 install errors)
- docs/engines/cosyvoice.md (closes #55 docs half)
- docs/features/diarization.md (pyannote license flow)
- docs/setup/huggingface-token.md (3-source cascade guide)
- scripts/validate-install-docs.py (INST-06 docs-drift gate)
- tests/scripts/test_validate_install_docs.py (B-5: validator self-tests)
- .github/workflows/ci.yml step running the validator on every PR
Implements INST-02 (README routing), INST-03 (macOS Gatekeeper anchor),
INST-12 docs half (Windows torch-compile-oom anchor), DOCS-01..05.
The validator is a one-way diff: every `<!-- validate -->`-tagged line
in docs must appear in scripts/desktop-prod.sh after normalisation
(prompt-prefix strip, CRLF, trailing whitespace, blank-and-comment skip).
A `<!-- validate: skip -->` marker opts out for human-readability blocks.
Its own 10 unit tests catch regressions in the gate itself.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(deeplinks): links.py + error_docs_map (Python + TS mirror)
Adds the single source of truth for the project repo URL and the 4-class
error → docs taxonomy that both the in-app ErrorBoundary deeplink button
(Wave 2 Task 3) and the Phase 5 bug reporter will consume.
New:
- backend/core/links.py — PROJECT_REPO_URL + BLOB_MAIN resolver
(Tauri config first, pyproject fallback)
- backend/core/error_docs_map.py — lookup(error_class) → docs URL
- frontend/src/utils/errorDocsMap.ts (TS mirror with classifyError helper)
- tests/backend/core/test_links.py + test_error_docs_map.py
- frontend/src/utils/errorDocsMap.test.ts
Resolves checker B-6 (links.py ownership) and Open Question #3 (which fork
the deeplinks resolve to — the Tauri updater endpoint wins, which points
at the desktop app fork debpalash/OmniVoice-Studio).
The TS BASE constant is documented as the second hardcoded URL drift site;
the keys-sync test (`test_keys_match_python_map` equivalent) guards the
4-class taxonomy contract between Python + TS halves.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(ui): Settings → API Keys panel + ErrorBoundary docs deeplink
Wave 2 AUTH-03 UI half + ErrorBoundary deeplink wiring.
ErrorBoundary fallback now renders an "Open docs for this error" button
that classifies the thrown Error message (heuristic: pkg_resources → 401 /
HfHubHTTP → WebKit / white screen → quarantine / Gatekeeper) and opens the
matching docs anchor via Tauri shell.open (with a window.open fallback
in browser dev mode).
ApiKeysPanel consumes the Wave 1 resolver state endpoint:
- 3 source rows (App / Env var / HF CLI) with set/unset indicator,
masked token preview, whoami username + green check
- "Active" badge on whichever source is currently serving the cascade
- App-row only: Save (POST /api/settings/hf-token) +
Clear (DELETE with optional "also clear HF CLI" confirm dialog)
- "Test now" button refetches state (invalidates the resolver's
validation cache via the same endpoint hit)
Panel mounted in the existing Settings → Credentials tab; the legacy
HF_TOKEN row from CREDENTIAL_FIELDS is filtered out so the two paths
don't fight over the same key.
Threat T-02-02: the panel never displays the full token. The masked
value comes from the resolver state endpoint; the full token only
crosses the IPC boundary on Save (POST) and is cleared from local
state on success.
Closes AUTH-03 fully (Wave 1 backend + this Wave 2 UI).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(perf): INST-12 Disable torch.compile (Windows) toggle (backend + UI)
Wave 2 Task 4 — full INST-12 delivery per checker B-2/B-7 v0.3.0 fat-release
decision. Both the docs half (windows.md anchor, shipped in earlier commit)
and the runtime toggle are now in Phase 1.
Backend:
- backend/services/settings_store.py: adds get_text/set_text helpers for
non-secret config (refuses to write to the encrypted hf_token key).
- backend/api/routers/settings.py: GET + PUT
/api/settings/perf/torch-compile-disabled, both under the existing
loopback guard (threat T-02-04).
- backend/services/engine_env.py: new `build_engine_env()` helper that
centralises HF_TOKEN/YOUR_HF_TOKEN injection from the 3-source resolver
AND injects TORCH_COMPILE_DISABLE=1 when the flag is set on win32.
Phase 2 SubprocessBackend launchers should adopt the same helper.
- backend/services/sonitranslate.py: migrated to engine_env.build_engine_env()
while preserving the source-level `env["HF_TOKEN"]` sentinel that
test_sonitranslate_module_uses_resolver checks.
Frontend:
- frontend/src/components/settings/PerformancePanel.{jsx,css,test.jsx}:
toggle UI with the explainer for #65; renders disabled with a "not
applicable" badge on macOS/Linux.
- frontend/src/pages/Settings.jsx: mounts the panel into the Credentials
tab alongside the API Keys panel.
Tests:
- tests/backend/test_perf_settings.py: 7 backend tests (default state,
PUT persistence, T-02-04 non-loopback rejection, settings_store round-
trip, env injection on win32, NO injection on macOS/Linux, NO injection
when disabled).
- frontend PerformancePanel.test.jsx: 5 tests (renders from GET state,
PUT on toggle, disabled on non-Windows platforms, pre-enabled state).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs(planning): Wave 2 SUMMARY + REQUIREMENTS status updates
- .planning/phases/01.../01-02-SUMMARY.md: full implementation report
per template (truths, commits, tests, deviations, drift-site
acknowledgments per W-3, launcher seam name for Phase 2,
taxonomy keys for Phase 5).
- .planning/REQUIREMENTS.md: flips Wave 2 closures to Done:
AUTH-03, INST-02, INST-03 (docs half), INST-06, INST-12,
DOCS-01..05.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5.6 KiB
OmniVoice Studio — Install Troubleshooting
The top 10 errors users have actually hit on v0.2.x, with their causes and
fixes. Most have a deeplink anchor that the in-app error UI's "Open docs for
this error" button targets directly.
1. pkg_resources missing (ModuleNotFoundError)
Symptom: the splash screen shows ModuleNotFoundError: No module named 'pkg_resources' during WhisperX import, and the app never advances past the
"Setting up models" step.
Cause: WhisperX (and a couple of its transitive deps) still imports
pkg_resources, which was removed from setuptools >= 70. Older uv sync
runs would resolve setuptools to a version that no longer ships it.
Fix: pull the latest main. pyproject.toml now pins
setuptools>=70,<81 and the WhisperX dep is patched to import from
importlib.metadata first.
Linked issue: #58
2. HF 401 / pyannote license not accepted
Symptom: dubbing fails with HfHubHTTPError: 401 Client Error: Unauthorized for url …pyannote/speaker-diarization-3.1…, or
diarization silently falls back to a single speaker.
Cause: pyannote/speaker-diarization-3.1 is a gated model — even with a
valid HF token, you need to accept the model's license on its HuggingFace page
before the token works for downloads.
Fix:
- Open Settings → API Keys in the app and paste a working HF token (or set
HF_TOKENin your env). See docs/setup/huggingface-token.md. - Visit https://huggingface.co/pyannote/speaker-diarization-3.1 while signed in with the same HF account → click "Agree and access repository".
- Retry the job. The token state in Settings → API Keys should now show the "App" row with a green check next to your username.
Linked issue: #35
3. Gatekeeper quarantine on macOS
Symptom: "OmniVoice Studio.app is damaged and can't be opened."
Cause: the app is not yet notarised (tracked for v0.4) — macOS quarantines every download.
Fix: see macos.md#gatekeeper-quarantine.
4. AppImage white screen on Fedora 44 / Ubuntu 24.04
Symptom: the AppImage window opens fully white. No UI ever appears.
Cause: WebKitGTK 2.44 / 2.46 compositing-mode regression.
Fix: see linux.md#appimage-white-screen-on-fedora-44--ubuntu-2404.
5. Windows Triton / torch.compile OOM
Symptom: the first synthesis call fails with OutOfMemoryError: CUDA out of memory or RuntimeError: Triton compilation failed, especially on
<16 GB VRAM GPUs.
Cause: the engine's torch.compile step compiles Triton kernels with a
peak memory footprint that exceeds free VRAM. Windows-only quirk.
Fix: see windows.md#torch-compile-oom.
Linked issue: #65
6. uv venv Python download fails (restricted network)
Symptom: during first launch, uv exits with a network error pulling
python-build-standalone from GitHub. Common in China, intermittently in
Russia, sometimes on corporate proxies.
Fix: see linux.md#restricted-networks-china--russia
(same env vars work on macOS and Windows — UV_PYTHON_INSTALL_MIRROR,
UV_HTTP_TIMEOUT=120, UV_HTTP_RETRIES=5, UV_PYTHON_PREFERENCE=only-system).
7. .deb ffprobe path conflict on upgrade
Symptom: after upgrading from a pre-v0.3 .deb, ffprobe -version reports
"OmniVoice bundled ffprobe" instead of the system ffmpeg, breaking other apps
that rely on /usr/bin/ffprobe.
Fix: see linux.md#deb-ffprobe-conflict.
8. Docker LAN access — media preview 404
Symptom: OmniVoice loads on http://<lan-ip>:3900 but the audio preview
pane shows 404s for /media/....
Cause: pre-v0.3, the frontend hardcoded localhost:3900 for media-preview
URLs, which is wrong when the UI is reached from a different LAN host.
Fix: Plan 01-03 ships a fix that derives the media-preview base from
window.location.host. See docker.md#lan-access for the
override env var (VITE_OMNIVOICE_API) when running behind a reverse proxy.
9. Apple Silicon mlx-whisper unavailable on Intel mac
Symptom: on an Intel mac, OmniVoice logs mlx-whisper backend unavailable; falling back to faster-whisper.
Cause: mlx-whisper and mlx-audio only build for arm64 (Apple Silicon).
Fix: none needed — faster-whisper (CTranslate2) is the supported Intel
path and is still fast. If you want the latest CT2 wheels, run uv sync
from a fresh source checkout.
10. IndexTTS / CosyVoice / ChatterboxTTS clash
Symptom: installing one of these engines breaks the others — e.g. after installing CosyVoice, IndexTTS errors out with import conflicts.
Cause: these engines pin incompatible transformer / torch versions inside their own engine venvs. Pre-v0.3 they shared a single venv.
Fix: Phase 2 ships subprocess isolation per engine (each engine runs in its own venv). For v0.3, workaround: install only one of the conflicting engines per OmniVoice copy. See docs/engines/cosyvoice.md for the dedicated CosyVoice path.
Linked issue: #55