From 73b466fbc054e80b50e318b49643aee8a03c784b Mon Sep 17 00:00:00 2001 From: historia Date: Mon, 24 Aug 2026 03:41:57 -0400 Subject: feat: settings for ports in TUI --- app/docs/backend-qwen.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'app/docs/backend-qwen.md') diff --git a/app/docs/backend-qwen.md b/app/docs/backend-qwen.md index af5f63e..0db3214 100644 --- a/app/docs/backend-qwen.md +++ b/app/docs/backend-qwen.md @@ -1,6 +1,6 @@ # Backend Option 2: Qwen3-TTS -The easiest way is to run `python audiobook.py` → **Set up a backend… → qwen-tts** (or `python app/backends/qwen.py`): the TUI pip-installs `qwen-tts` into its managed venv (`app/envs/tts`), configures the two ports and the built-in speaker in `app/converter/config.py`, and prints the launch commands. You can also start the server from the hub's **Server** menu, or let a conversion start it automatically. +The easiest way is to run `python audiobook.py` → **Set up a backend… → qwen-tts** (or `python app/backends/qwen.py`): the TUI pip-installs `qwen-tts` into its managed venv (`app/envs/tts`), configures the two ports and the built-in speaker in `app/converter/config.py`, and prints the launch commands. You can also start the server from the hub's **Start/Stop Backend Servers** menu, or let a conversion start it automatically. If you prefer to install the backend yourself (in your own environment, not the managed venv), the manual steps are below. Either way the hub detects a running server by its port, so a manually-installed backend works once its server is up. -- cgit v1.2.3