Skip to content
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] Language Support ("Hindi") missing in XTTS on local machine. #3655

Open
akshatrocky opened this issue Mar 30, 2024 · 2 comments · Fixed by idiap/coqui-ai-TTS#4
Labels
feature request feature requests for making TTS better.

Comments

@akshatrocky
Copy link

*Title

On XTTS site (i.e https://huggingface.co/coqui/XTTS-v2), Hindi language is already supported and it's working perfect on demo site. But, the problem is when I install XTTS on my local machine, error appears that 'hi' is not supported.

Language hi is not supported. Supported languages are ['en', 'es', 'fr', 'de', 'it', 'pt', 'pl', 'tr', 'ru', 'nl', 'cs', 'ar', 'zh-cn', 'hu', 'ko', 'ja']

Possible solution might be adding 'hi' index in languages. Since afaik, XTTS on local machine import the dataset as on the online demo website. Also, for fine tuning XTTS (used colab notebook from this video - https://www.youtube.com/watch?v=8tpDiiouGxc), Hindi language option isn't available as a option. It would be helpful to add support plus able to fine tune XTTS for that language.

Thanks!

@eginhard
Copy link
Contributor

Thanks for spotting this. I've enabled Hindi in the fine-tuning demo and tokenizer in our fork: https://github.com/idiap/coqui-ai-TTS

@akshatrocky
Copy link
Author

Hi, thanks for the fork repo link, I noticed keyerror='hi' type of errors when I tried to fine tune model, however I've added some 'hi' tags/attributes in some function located in tokenizer.py and now it's works perfectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request feature requests for making TTS better.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants