You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When training a model on Piper VITS, some eSpeak-NG functions do not work correctly. Specifically, numbers 10 and above are pronounced as separate digits (e.g., "10" is read as "one zero" instead of "ten").
Interestingly, when testing a similar model VITS by Coqui with the same dataset, this issue does not occur.
Expected Behavior:
Numbers should be pronounced correctly rather than as separate digits.
Steps to Reproduce:
Train a model on Piper VITS using eSpeak-NG.
Try synthesizing numbers 10 and above.
Notice that instead of the expected pronunciation, numbers are read as separate digits.
Possible Causes:
Issues with text tokenization before being fed into the model.
Problems with eSpeak-NG integration in Piper VITS.
Missing number processing rules in the current configuration.
Question:
How can this issue be resolved? Are there any ways to explicitly configure eSpeak-NG in Piper VITS to ensure correct number pronunciation?
The text was updated successfully, but these errors were encountered:
When training a model on Piper VITS, some eSpeak-NG functions do not work correctly. Specifically, numbers 10 and above are pronounced as separate digits (e.g., "10" is read as "one zero" instead of "ten").
Interestingly, when testing a similar model VITS by Coqui with the same dataset, this issue does not occur.
Expected Behavior:
Numbers should be pronounced correctly rather than as separate digits.
Steps to Reproduce:
Possible Causes:
Issues with text tokenization before being fed into the model.
Problems with eSpeak-NG integration in Piper VITS.
Missing number processing rules in the current configuration.
Question:
How can this issue be resolved? Are there any ways to explicitly configure eSpeak-NG in Piper VITS to ensure correct number pronunciation?
The text was updated successfully, but these errors were encountered: