-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Piper: Crash after any TTS call #3379
Comments
This is especially likely to happen when playing longer messages. This is currently preventing me (and others) from switching TTS engines to Piper (this does not happen with my marytts based mimic3 server). |
For me, it happens on any message. This issue is new in this update, before working as expected. |
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. |
This seem the same error described here rhasspy/wyoming-piper#8 Piper is crashing when writing the resulting audio wav file, so the instruction to open it to continue is failing. Wild guess, try to increase the parameter |
I tried increasing the number of processes to 2, does not fix the issue however. Piper only seems to work for shorter texts. As soon as the input gets a little longer I get this:
This is a different exception though. Running on a Raspberry Pi 5 8GB |
Issue resolved for me. Piper 1.5.0, HA: 2024.3.0. |
Did you manage to fix this? I have the same issue with the same hardware - I changed PSU+cable and its fine now. |
Never tried again unfortunately @ArifJSyed |
Describe the issue you are experiencing
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Piper
What is the version of the add-on?
1.4.0
Steps to reproduce the issue
System Health information
Anything in the Supervisor logs that might be useful for us?
The text was updated successfully, but these errors were encountered: