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

Bug: text_to_speech.ipynb final cell - possible infinite loop? #239

Closed
Veronika271 opened this issue Jan 15, 2025 · 6 comments
Closed

Bug: text_to_speech.ipynb final cell - possible infinite loop? #239

Veronika271 opened this issue Jan 15, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@Veronika271
Copy link

Description

I have been running all of the cells in the text_to_speech.ipynb tutorial sequentially, and the final one has been running for over 25 minutes now without stopping.

Steps to Reproduce

  1. Open up text_to_speech.ipynb.
  2. Run every cell in order.

Expected Results

I expected the final cell to run in 2-3 minutes.

Actual Results

It has been running for over 25 minutes now, and it looks like this is due to a very long loop which might be infinite. I have tried stopping it and restarting it and this did not help.
Here is a screenshot of what I see. The gray text on the bottom looks kind of repetitive, which is why I feel like there might be a long loop involved.
image

Additional Notes

It's possible I am not patient enough, so I will leave this cell running for a few hours and update or remove the issue if it ends up finishing!

@Veronika271 Veronika271 added the bug Something isn't working label Jan 15, 2025
@Veronika271
Copy link
Author

Update: it took 53 minutes and 50 seconds, but it worked!

@satra
Copy link
Collaborator

satra commented Jan 15, 2025

@Veronika271 - did you use the gpu for this? it's a setting in google colab (runtime).

@Veronika271
Copy link
Author

I didn't, but I am trying to rerun the tutorial on GPU right now to see what happens!

@Veronika271
Copy link
Author

It took 2 minutes to run on GPU, but the voice was less accurate.

@satra
Copy link
Collaborator

satra commented Jan 15, 2025

interesting (which means precision may matter and it may be good to set it explicitly). thanks for the update. @fabiocat93 - just a ping in case this rings a bell.

@fabiocat93
Copy link
Collaborator

interesting (which means precision may matter and it may be good to set it explicitly). thanks for the update. @fabiocat93 - just a ping in case this rings a bell.

On the CPU, the model may use FP32 (higher precision but slower), while on the GPU, it might use FP16 (lower precision but faster). This difference could be why the TTS results were lower quality on the GPU

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants