-
Notifications
You must be signed in to change notification settings - Fork 668
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
Speech To Text - Error: write after end exception #202
Comments
hi @Nhor, did you update the |
(Note: both the username and password are random characters generated by bluemix - see https://github.com/watson-developer-cloud/node-sdk#getting-the-service-credentials for instructions on how to get them.) |
Yes, I've generated my Watson Speech To Text service credentials and I'm getting the very first chunk of the response, but there goes a cascade of errors. Here's the
|
Hum, that doesn't sound good.. can you email me the sample audio file you're using? [github username]@us.ibm.com |
Oh, also, please try creating a reference to the recognizeStream and listening for other events to see if anything else stands out. There's an example of this at https://github.com/watson-developer-cloud/node-sdk/blob/master/examples/speech_to_text.v1.js |
I've tried several audio files. So my conclusion is that it seems like the service is working perfectly fine with short phrases but fails to recognize bigger files, throwing |
Got the file, reproduced the bug, it looks like the connection is closing with a 1006 error/status code. I'll track down the root cause and get a fix out, hopefully within a day or two. |
Great, thanks!
|
This should be fixed in v1.2.0 - by default, the STT services stops processing after the first sentence/pause, and there's a There may still be some issues to be address when it is overridden and set to false, but this should be a better fit for most usage. |
Code from the docs:
throws
Error: write after end
exception. Here's my full stacktrace:The text was updated successfully, but these errors were encountered: