Speech sample with 'listen' command stops node after results returned

[stuarttayler]

When I run the speech sample with the 'listen' command, the transcribed text is returned but then the node process stops and returns be to the command line. I'm not getting any error messages, it just returns the text and stops.

I assumed it should carry on listening and return more results rather than quitting, or is this the expected behaviour? If so is there a way to continually listen?

I am running the sample on a mac with node 6.9.4. I'm using the service json file to authorise.

[jmdobry]

I am seeing the same issue.

I assumed it should carry on listening and return more results rather than quitting

That is what it used to do. I suspect this may be related to upgrading the version of node-record-lpcm16 used by the sample.

Can you try downgrading node-record-lpcm16 to 0.1.4 and see how that works for you?

[stuarttayler]

Thanks, I'll give that a try and let you know

[stuarttayler]

Hey @jmdobry that didn't work, but just looking at package on NPM and it says: "The library will automatically attempt to stop when it encounters silence, if not you can stop the recording manually." which I guess explains it... Not sure if earlier versions did this too.

[jmdobry]

Looks like there's a silence threshold setting, I'll try tweaking that in the sample.

[iam-peekay]

Hi @jmdobry For me, it's throwing an error saying:
"listener" argument must be a function

[jmdobry]

Hmm, I just tried the sample again, and I was unable to reproduce any issue. It worked fine for me. I'm on Node.js 6.9.1 and Mac OS X.

It continued to listen, even after pauses. Note that I tried this in a rather quiet environment.

[victorfliks]

Hi @jmdobry i try the speech sync, and the other command and work fine,
but if i use listen command it always return :

Listening, press Ctrl+C to stop.
events.js:160
throw er; // Unhandled 'error' event
^

Error: spawn rec ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3

my node version are 6.10.0
and i'm running on windows machine
I'm using the service json file to authorise.

[metalaureate]

@victorfliks +1 same error

[immartian]

same problem here.
The listening will stop after several hits, without error messages.

I sense there's a time limitation after checking an old post https://groups.google.com/a/chromium.org/forum/#!topic/chromium-html5/s2XhT-Y5qAc
it's quite out-of-date information, I can't imagine this limitation still there.

[JoYeonJeong]

Did you solve this problem???

[fhinkel]

If the issue still persists, please file it here. Thank you.