forked from coqui-ai/TTS
-
Notifications
You must be signed in to change notification settings - Fork 101
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
[Bug] HF transformers update breaks XTTS streaming #31
Labels
Comments
4 tasks
eginhard
added a commit
that referenced
this issue
May 28, 2024
transformers>=4.41 break XTTS streaming, see #31
Merged
|
@pseudotensor Cool, thanks! Do you want to send a PR? |
eginhard
added a commit
that referenced
this issue
Jun 16, 2024
….41.1 Fixes #31. The handling of special tokens in `transformers` was changed in huggingface/transformers#30624 and huggingface/transformers#30746. This updates the XTTS streaming code accordingly.
This was referenced Jun 16, 2024
eginhard
added a commit
that referenced
this issue
Jun 16, 2024
….41.1 Fixes #31. The handling of special tokens in `transformers` was changed in huggingface/transformers#30624 and huggingface/transformers#30746. This updates the XTTS streaming code accordingly.
eginhard
added a commit
that referenced
this issue
Jun 17, 2024
….41.1 Fixes #31. The handling of special tokens in `transformers` was changed in huggingface/transformers#30624 and huggingface/transformers#30746. This updates the XTTS streaming code accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
huggingface/transformers#30624 broke the XTTS streaming code (https://github.com/idiap/coqui-ai-TTS/blob/df088e99dfda8976c47235626d3afb7d7d70fea2/TTS/tts/layers/xtts/stream_generator.py) as reported in huggingface/transformers#31040. The streaming code needs to be updated accordingly.
To Reproduce
https://coqui-tts.readthedocs.io/en/latest/models/xtts.html#streaming-manually
Expected behavior
No response
Logs
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: