-
Notifications
You must be signed in to change notification settings - Fork 230
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
Stuck on "Say something" #62
Comments
Can you please leave issues only in English or in both languages. Did you try the STT from the GUI first? Le 10 nov. 2016 1:00 PM, "5ika" notifications@github.com a écrit :
|
Also there is a dedicated section in our doc with some stuff to do on a rpi Le 10 nov. 2016 1:06 PM, "Nicolas Marcq" nico.marcq@gmail.com a écrit :
|
I'm sorry, I updated my message with english language. Yes, I tried STT from the GUI and there is no response. |
Really weird, if the trigger is detected, the STT should work exactly the same way. What is you OS version? The last Raspbian Jessie? It's the only one we have tested so far. |
I'm on Raspbian Jessie. Fresh install with the last official image. |
The network is well configured? Are you behind a proxy server? The RPI has a full access to the internet? |
The RPI has all access to the network. I ping network without problem. No proxy, DNS okay. |
Ok, I need to perform some test, maybe it is due to our last changes. I'll be back to you in a couple minutes. |
So, I've just tested the last on my laptop (In a VM on Ubuntu 16.04) and it works with the last stable release (master branch). I've not tested in my Rpi, I cannot do it before tomorrow. I can only recommend to try with another microphone from now. I'll perform a full install tomorrow to confirm that issue. |
Ok, thank you for your time. |
I'll test with my own microphone tomorow on a fresh install of Raspbian Jessie. I keep this issue open until I can confirm it is not a Kalliope problem. Anyway, the automated install is fully functional on Ubuntu 16.04. So if you want to test kalliope and play with it by creating your brain you can install the project in a VM and then copy your brains when the Rpi is fixed. |
So I've tested on my own RPi with a fresh install. Hope this help. I'll add this into the Rpi doc. If you can confirm that is ok from your side too. |
Still the same... I moved the sensibility to the top. |
Hi, I had the same kind of problem : it doesn't understand "kalioppe" when waiting for "Say something" on start. I tried in the gui, microphone / tts / stt works fine there.
Ps: I'm French, so maybe I don't enunciate "kalioppe" correctly. |
Look at the demo of kalliope in French to know how to pronounce it. Le 20 nov. 2016 3:36 PM, "Skunnyk" notifications@github.com a écrit :
|
And by the way. "Say something" appears when the hotword has been detected. Le 20 nov. 2016 3:40 PM, "Nicolas Marcq" nico.marcq@gmail.com a écrit :
|
Oh, yes, "say something" appears after the hotword has been detected … and my problem was the hotword detection. Sorry :) |
@5ika ping. |
I think I can close this. It seems to be attached to the used microphone. |
Merci beaucoup pour ce projet ! Ça fait longtemps que je cherchais un équivalent.
French
J'ai suivi toutes les instructions pour l'installation (dev) sur une raspberry pi.
J'ai cependant un souci : l'application reste bloqué sur "Say something" et ne semble pas reconnaître ce que je dis.
Pourtant, j'arrive bien a récupéré le son par mon micro avec
rec
puis à l'écouter avecplay
.Comme le mode debug n'indique rien de plus, je ne sais pas trop comment résoudre cela.
Auriez-vous une piste ?
English
I followed the instructions for the installation on a raspberry pi.
But i have an issue : the application gets stuck on "Say something" and it does not seem to recognize what i am saying.
However, I can recover a sound with
rec
thenplay
.Debug mode indicates nothing more and I don't know how to resolve this.
Can you help me ?
The text was updated successfully, but these errors were encountered: