-
Notifications
You must be signed in to change notification settings - Fork 800
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 request] Text to Speach #315
Labels
enhancement
New feature or request
Comments
Thank you, given the interest I could add the support this week & do a release. Which architecture are you interested in priority? |
I want to use this model: microsoft/speecht5_tts. |
3 tasks
3 tasks
I want to use this model:bark |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name of the feature
In general, the feature you want added should be supported by HuggingFace's transformers library:
Model: SpeechT5_TTS (Text-to-Speech)
The model is available here on HuggingFace's platform.
Reason for request
Why is it important that we add this feature? What is your intended use case? Remember, we are more likely to add support for models/pipelines/tasks that are popular (e.g., many downloads), or contain functionality that does not exist (e.g., new input type).
Usefulness: The SpeechT5_TTS model is designed to convert text into spoken audio. This model could serve multiple purposes across different sectors, including but not limited to education, automation, and accessibility.
Popularity: As a Microsoft model, it is backed by significant research and development, making it one of the more robust and versatile options available for text-to-speech.
New Functionality: Though text-to-speech is not a new technology, the advanced capabilities of this model could offer more natural and clear speech, which is especially valuable in applications where voice clarity and natural intonation are important.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: