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

Recommended text or phoneme tokenizer to use #7

Open
francislata opened this issue Nov 3, 2023 · 3 comments
Open

Recommended text or phoneme tokenizer to use #7

francislata opened this issue Nov 3, 2023 · 3 comments

Comments

@francislata
Copy link

Hi @cantabile-kwok, in the paper, there was not any recommended text or phoneme tokenizer to use. Do you have recommendations of what to use?

Thank you.

@cantabile-kwok
Copy link
Member

That is a tricky thing, and I am also thinking about it. In our workflow, we used the Kaldi toolkit and a pre-defined (CMU dict-based) lexicon file to specify each word with its phone sequence. Now this may be too troublesome to use for users not familiar with it. As far as I know, there is a phonemizer g2p tool which, when built upon eSpeak, can generate accurate IPA transcriptions of given sentences. There is also a g2p_en python package which can give the CMU dict phonemes.

These might be easy to use, so you may have a try.

@francislata
Copy link
Author

Thanks for that. I’ve been looking at the Coqui TTS tokenizer class, which will handle phonemization if needed. This takes care of almost everything, including text mormalization. So I’ll give it a try first and go from there. I’ll see if the g2p-en can be integrated too.

@rishikksh20
Copy link

@francislata Have you used Coqui TTS tokenizer for your Unicats, is it working good ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants