Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Windows10 problem. Cannot run node recognize.js listen #255

Closed
GTamara opened this issue Dec 10, 2018 · 10 comments
Closed

Windows10 problem. Cannot run node recognize.js listen #255

GTamara opened this issue Dec 10, 2018 · 10 comments
Assignees
Labels
api: speech Issues related to the googleapis/nodejs-speech API. priority: p2 Moderately-important priority. Fix may not be included in next release. 🚨 This issue needs some love. status: blocked Resolving the issue is dependent on other work. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@GTamara
Copy link

GTamara commented Dec 10, 2018

Hello
I am trying to launch nodejs-speech/samples by using node recognize.js listen
but it is not working. The error message is the following:

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

Error: spawn rec ENOENT
    at _errnoException (util.js:1024:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
    at onErrorNT (internal/child_process.js:372:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:678:11)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

I am using Windows10, I set $env:GOOGLE_APPLICATION_CREDENTIALS="D:\projects\current\speech\speech-recognition-1eec10025372.json".

Also I added sox folder to $path.

When I try another command:

node recognize.js sync ./resources/audio.raw -e LINEAR16 -r 16000

It works fine.
What is wrong? Let me know, please.

Best regards.

@JustinBeckwith JustinBeckwith added triage me I really want to be triaged. 🚨 This issue needs some love. labels Dec 11, 2018
@JustinBeckwith JustinBeckwith added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Dec 23, 2018
@JustinBeckwith
Copy link
Contributor

👋 @googleapis/ml-apis

@JustinBeckwith JustinBeckwith removed 🚨 This issue needs some love. triage me I really want to be triaged. labels Dec 23, 2018
@nnegrey
Copy link
Contributor

nnegrey commented Dec 27, 2018

Hi, do you have sox installed on your machine?

Related Issue:
GoogleCloudPlatform/nodejs-docs-samples#397

@nnegrey nnegrey self-assigned this Dec 27, 2018
@jkwlui jkwlui added the needs more info This issue needs more information from the customer to proceed. label Jan 15, 2019
@jzhao8
Copy link

jzhao8 commented Mar 25, 2019

Does not work, Sox 14.4.2 and 14.4.1 both tried and, yes they were added to PATH.

@JustinBeckwith JustinBeckwith removed the needs more info This issue needs more information from the customer to proceed. label Mar 25, 2019
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Jun 8, 2019
@sduskis
Copy link

sduskis commented Jun 13, 2019

@ajaaym can you please have someone take a look at this?

@ajaaym
Copy link

ajaaym commented Jun 13, 2019

@sduskis ack, will have someone to start on this soon.

@beccasaurus beccasaurus removed their assignment Jun 13, 2019
@laljikanjareeya
Copy link
Contributor

please go through this issue and change the index.js of node-record-lpcm16 as suggested here.

@bcoe
Copy link
Contributor

bcoe commented Jun 25, 2019

@GTamara just following up, did @laljikanjareeya's recommendation do the trick for you?

@StillOnMyWay
Copy link

StillOnMyWay commented Jul 8, 2019

Also following up, any movements toward a longer term fix? The link which was posted worked btw.

please go through this issue and change the index.js of node-record-lpcm16 as suggested here.

@laljikanjareeya
Copy link
Contributor

issue in node-record-lpcm16 and PR for this issue is already in node-record-lpcm16 repository, once they release the new version we will upgrade it.

@bcoe bcoe added the status: blocked Resolving the issue is dependent on other work. label Jul 8, 2019
@bcoe
Copy link
Contributor

bcoe commented Jul 8, 2019

currently blocked by gillesdemey/node-record-lpcm16#46

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api: speech Issues related to the googleapis/nodejs-speech API. priority: p2 Moderately-important priority. Fix may not be included in next release. 🚨 This issue needs some love. status: blocked Resolving the issue is dependent on other work. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests