Skip to content
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 api limits and not showing the transcript that I have spoke on command prompt #405

Closed
GH-rajasekharReddy opened this issue Jun 19, 2017 · 3 comments
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@GH-rajasekharReddy
Copy link

I am new to nodejs and testing speech sample in real-time with sox on windows 10 platform.
Though I am able to run "node recognize.js listen" command successfully but it is throwing below output,

E:\nodejs_voicer\nodejs-docs-samples\speech>node recognize.js listen
Recording with sample rate 16000...
Listening, press Ctrl+C to stop.
Recording 5548 bytes
End Recording: 37.970ms

End recording is showing different time duration for multiple test runs but 5548 bytes of recording is constant.

What are the actual limits for streamingMicRecognition call? I have checked the documentation for streamingRecognition, it is available with approximate values as ~1min etc. refer streamingRecognition & audio-limits

  1. I am not able to view the text which I spoke from the command prompt. Anything needs to be tweaked or doing something wrong?
  2. What is this 5548 limit to audio speech api?
  3. Why recording is ending ~26ms even when I am on talk?

Please guide me on above queries.
If this is not the right place for this discussion, suggest me where can I log my concerns? Appreciate your time on this.

@ARTI7
Copy link

ARTI7 commented Sep 27, 2017

i m getting the same error with sox on windows 7.

please guide me.

@AkaiBF
Copy link

AkaiBF commented May 11, 2018

Same error also with sox on Windows 10.

@fhinkel
Copy link
Contributor

fhinkel commented Nov 8, 2018

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

@fhinkel fhinkel closed this as completed Nov 8, 2018
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
NimJay pushed a commit that referenced this issue Nov 10, 2022
NimJay pushed a commit that referenced this issue Nov 10, 2022
NimJay pushed a commit that referenced this issue Nov 11, 2022
🤖 I have created a release \*beep\* \*boop\* 
---
### [2.1.4](https://www.github.com/googleapis/nodejs-kms/compare/v2.1.3...v2.1.4) (2020-11-25)


### Bug Fixes

* **browser:** check for fetch on window ([#404](https://www.github.com/googleapis/nodejs-kms/issues/404)) ([96a90e3](https://www.github.com/googleapis/nodejs-kms/commit/96a90e3bea1c8b7e8e2d57cc1eb6204ed326b915))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please).
ace-n pushed a commit that referenced this issue Nov 11, 2022
🤖 I have created a release \*beep\* \*boop\* 
---
### [2.1.4](https://www.github.com/googleapis/nodejs-kms/compare/v2.1.3...v2.1.4) (2020-11-25)


### Bug Fixes

* **browser:** check for fetch on window ([#404](https://www.github.com/googleapis/nodejs-kms/issues/404)) ([96a90e3](https://www.github.com/googleapis/nodejs-kms/commit/96a90e3bea1c8b7e8e2d57cc1eb6204ed326b915))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Development

No branches or pull requests

6 participants