VoiceBridge
Every synthesis request goes through one place: the VoiceBridge. That's what keeps engine details out of the rest of the app.
At a glance
- Routes requests to engines over HTTP.
- A remote bridge + client talk to the TTS Server.
- Honors engine enablement and readiness.
Routing
The bridge resolves the voice, validates readiness, builds the engine request, and normalizes the result. Nothing else calls engines directly.
Remote client
A bridge client speaks to the TTS Server over HTTP. Studio caches engine info from the server rather than importing engine code. See Plugin Architecture.