You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A colon seems to end the voice, and a program waits for another command / voice... see example below.. it doesn't allow gpt to say the joke. is there a solution for that ?
[03:13:04] info: Waiting for wake phrase...
[03:13:07] info: Wake phrase detected.
/bin/bash: line 1: mpg123: command not found
[03:13:07] info: Speaking (none): Hello!
[03:13:09] info: Listening...
[03:13:13] info: Recognized: Tell me a joke.
[03:13:16] info: Speaking (none): Sure, here's a classic one for you:
[03:13:19] info: Listening...
[03:13:24] info: Recognized: Talk.
The text was updated successfully, but these errors were encountered:
Sorry, it wasn't a solution. What I've resorted to doing is asking if to refrain from using colons in responses. I do this whenever i restart the program. Not perfect, and i do wish @adrianwyatt comes to the rescue soon.
I originally tried to include this in the config file where it says something along the lines of "I'm a friendly bot... my name is Alex" etc. but didn't work.
A colon seems to end the voice, and a program waits for another command / voice... see example below.. it doesn't allow gpt to say the joke. is there a solution for that ?
[03:13:04] info: Waiting for wake phrase...
[03:13:07] info: Wake phrase detected.
/bin/bash: line 1: mpg123: command not found
[03:13:07] info: Speaking (none): Hello!
[03:13:09] info: Listening...
[03:13:13] info: Recognized: Tell me a joke.
[03:13:16] info: Speaking (none): Sure, here's a classic one for you:
[03:13:19] info: Listening...
[03:13:24] info: Recognized: Talk.
The text was updated successfully, but these errors were encountered: