-
Notifications
You must be signed in to change notification settings - Fork 101
wavenet tts not working #211
Comments
Same error, I too I'm working on 2.4.20, seems that the tts.py can't import google tts client libraries
|
Same here... seems google tts module is missing? |
Well at least when trying to install it by hand it says its already installed:
|
forgot to clarify, i'am on the rhasspy docker image. @patrickjane if you are running rhasspy in a docker container too: did you log into this container? perhaps @Romkabouter can help? ;) Edit: Ah I see now, your created a python venv |
@linuxlurak nope I'm on a venv installation. |
I have got the same issue, I'll see if I can fix it |
I had not noticed it, because playing from cache works fine |
Seems like there was a missing dependency. After
Continuing to investigate ... |
Okay, found the issue. I was giving This is the relevant part in profile.json:
|
Good find, so I think the docker should be updated |
I am not using docker, I did the venv installation. |
I logged into the docker image, installed pip, the google-cloud-texttospeech library and then restarted rhasspy but I still have the same error |
Okay so I remember that two weeks ago I already tried to fix this, and installed some google package, but still it didnt work, so I stopped investigating. Maybe theres a second package missing. Lets compare:
|
google-api-core 1.17.0 Pretty the same for my docker image. |
Okay so I just did a complete new install, and for me it was fixed after manually installing
So after the initial installation I had:
In this, |
I am using the hassio addon and have the same problems with wavenet tts. GoogleWaveNetSentenceSpeaker: Falling back to EspeakSentenceSpeaker Is there a solution for the addon too? |
PR is merged, can you retry? I do not know if the docker image is already released however. |
Hello,
I am on a fresh install of 2.4.20 on a fresh install of raspbian buster, and I've just added credentials and configuration for the wavenet tts. However it always falls back to espeak.
This is what I get in the logs:
Not sure what could be wrong here?
The text was updated successfully, but these errors were encountered: