The Two Environments

Studio uses two Python environments. Keeping them apart prevents the app and the heavy engine dependencies from fighting each other.

At a glance

./venv: the web app and orchestrator.
~/xtts-env: the heavier local-engine dependencies.
Separation avoids dependency conflicts.

Why two?

The app and the local engine have very different dependencies. The local cloning engine pulls in large machine-learning packages that can conflict with the app's lighter stack. Isolating them keeps both stable.

What lives where

./venv: the FastAPI app, orchestrator, and tooling.
~/xtts-env: the local engine and its model dependencies.

The TTS Server (which hosts engines) runs against the engine environment, while the app runs in its own. See TTS Server & Watchdog.

Tip: If engine dependencies ever get into a bad state, you can recreate ~/xtts-env without touching the app. See The XTTS Environment.