-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
xttsv2 model sometimes(almost 10%)produce extra noise.[Bug] #3598
Comments
training data default length is about 15 seconds |
Is my training reference audio too long?(lower than 5 minutes will be better) |
Most often occurs in FR language than others. You synthesize 10 samples of a "text" for a given "voice", 2-3 out of those 10 samples contain the "text" + "some other blabbering" |
same with german. For german, i think i sometimes could hear sentences like (just some guessing here) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You might also look our discussion channels. |
keep watching |
i think something that confirms my guess. it should not pronounce punctuation marks in my opinion. |
I also have a problem with noise after punctuations and in long sentences it is common for him to say the 'ponto' for the period in Portuguese Does anyone know if it is possible to reduce this by finetunning the model? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You might also look our discussion channels. |
Describe the bug
For example,If it generates a 30-second audio, for the first 15 seconds it generates normal audio, and for the last 15 seconds it generates noise
To Reproduce
tts_to_file(text=text,
language=lang_code,
speaker_wav=speaker_wav,
speed=speed,
file_path=temp_file
,split_sentences=split_sentences)
Expected behavior
No response
Logs
No response
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: