Replies: 3 comments 1 reply
-
|
Cool, thanks for this! When I get time I'll give it a try (assuming I can also get that observabily app running dependably. (Maybe you have tricks for this as well as it seems tricky in wsl 😅). I was setting up something similar for wsl PAI to windows communications so I could use a local install of xtts. Only got as far as getting the monitoring server to notify it had started up. 🙃 |
Beta Was this translation helpful? Give feedback.
-
|
Please refer to this major change coming to the repo that should address your issues. If it doesn't please resubmit. Thank you for the work! |
Beta Was this translation helpful? Give feedback.
-
|
Voice server currently requires macOS — it uses system audio frameworks that don't have a WSL equivalent yet. WSL2 users can run PAI without voice (just remove the voice curl lines or let them fail gracefully). Native Windows support for voice is on the radar but not yet scheduled. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There was some code adjustment to the server.ts file to get it to work with Windows through WSL:
Here is the edited server.ts:
VoiceServer-TS.md
Also need to install the following:
🪟 3. Windows / WSL Audio Prerequisites
On Windows:
Install FFmpeg and add
ffplay.exeto PATH.Optionally install BurntToast for better notifications:
On WSL (Ubuntu/Debian):
This shared folder ensures Windows can read MP3s generated inside WSL.
Beta Was this translation helpful? Give feedback.
All reactions