-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Using another vocoder #864
Comments
Yes, you can use a different vocoder, I know for a fact that the encoder can be taught to audio of a different sample rate, but I am not sure about the other models |
I also understand that the speaker's encoder should not be affected by this. I'm interested in using a synthesizer and vocoder with different sampel rates. |
In theory it should work |
It is possible to use a different sample rate for the vocoder. The vocoder hparams must be chosen carefully to be compatible with the synthesizer. There is some discussion here: mozilla/TTS#520 (comment) . If you use our defaults for the synthesizer hparams, the mel spectrograms will not contain any frequency content above fmax=7600 Hz. You may wish to change this. |
Thanks for the great job! My question is, can I use another vocoder for waveform synthesis, and if so, what features can it have? (For example: should it have the same sample rate as the entire pipeline?)
The text was updated successfully, but these errors were encountered: