-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Support for StyleTTS2 and OpenVoice TTS Engines #2072
Comments
@JasonLovesDoggo I'll like to work on this one , any suggestions? it'll be my first bigger issue so , a head's up will be great.... |
It shouldn't be too hard to integrate, you really shouldn't need to modify any files besides creating a new file TTS directory, but look at the other TTS engines for how to actually implement one |
@JasonLovesDoggo I've gone throught the openVoice , it involves installing various dependencies and doesn't offer a library , i think it might make installing the bot much more difficult and pretty heavy. |
The bot has become quite heavy due to the integration of certain AI features. However, simplicity is key in this context. If a suitable wrapper or library is found or developed, it could certainly enhance the bot's functionality. If not, we may consider leaving it as is. |
Summary
Add Openvoice V2 and/or StyleTTS2 TTS
Is your feature request related to a problem?
No
Describe the solution you'd like
Hi, I'm excited to request integration with two impressive TTS (Text-to-Speech) engines: StyleTTS2 and OpenVoice. Both engines offer high-quality voices, and incorporating them into your project would be a fantastic addition.
I attempted to integrate them myself, but unfortunately, I found it too challenging. However, I believe OpenVoice V2, in particular, has great potential and would be an excellent choice. It seems more accessible and performs better.
I'd love to hear your thoughts on this request and look forward to your response.
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: