-
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
[Warning] stft with return_complex=False is deprecated. #2639
Comments
Hi @Alienpups, Yeah, it is a thing. To fix it, we need to change our STFT class to use
by
A PR would be welcome :). |
To fix this warning, do I just need to make the changes you mentioned in torch_transforms.py? Did I understand that correctly? And what exactly does PR mean? :) So I replace these three lines... with the following? ... |
Yes, you also need to use "return_complex=True" on the torch.stft function call. Sorry, PR means pull request. If you like you can do these changes and then send a pull request and turn a 🐸 TTS contributor :). |
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. |
I have the same problem, and fix by change edit file python3.10/site-packages/torch/functional.py
and insert this before:
|
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. |
…coqui-ai#2639 Resolve "UserWarning: The use of `x.T` on tensors of dimension other than 2 to reverse their shape is deprecated" by using `x.mT` instead of `x.T`
Describe the bug
If I start to train my model I always get this warning message. Is it just me or is this a thing?
To Reproduce
I run this command: C:\TTS-Training>python train_vits.py --continue_path "vits_louise-voice-April-21-2023_05+38PM-0000000".
Training starts but I always get warned about some sft error.
Expected behavior
No response
Logs
No response
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: