-
Notifications
You must be signed in to change notification settings - Fork 57
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
Cannot import name 'ParlerEngine' from 'RealtimeTTS' #17
Comments
Need to look into that. |
sry I have a meeting to go to real quick |
Ok, np. Found the issue: I focused on conda installation and forget to upgrade the main requirements without conda, where RealtimeTTS giot outdated. I updated the requirements file, with this it should work now. If you don't want to reinstall you can start the virtual environment and execute |
I successfully booted up after the installation, but there's a few errors.
And when I try to switch speech engine, this happens:
|
Also when I tried speaking to it, something stranged popped up.
|
Will look into that tomorrow. We will solve all that. |
The system engine error very much looks like a bug. I didn't use that engine for a while, probably I changed something and messed it up. |
Alright, I'll try 👍 |
Actually upgrading realtimestt seems to solve all the issues, it's responding normally now, it's just awefully slow because I have a GTX 1560 super. |
Also I saw that there's something called wakeword, and I suppose that wakes the assitant up? What am I suppose to say in order to let it wake up? |
Standard wakeword is "Jarvis", currently hardcoded, I really need to change that. You can open Linguflex/lingu/modules/listen/logic.py manually and edit line 413 to change the wake word. With pvporcupine as wakeword backend you can choose a wakeword from this list: alexa, americano, blueberry, bumblebee, computer, grapefruits, grasshopper, hey google, hey siri, jarvis, ok google, picovoice, porcupine, terminator. |
Seems like an issue with TextToSpeech, might be an import issue or wrong requirements?
Full log below.
The text was updated successfully, but these errors were encountered: