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

Audio data is being streamed too fast or too slow #420

Closed
shivag12 opened this issue Jul 9, 2017 · 2 comments
Closed

Audio data is being streamed too fast or too slow #420

shivag12 opened this issue Jul 9, 2017 · 2 comments
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@shivag12
Copy link

shivag12 commented Jul 9, 2017

Am facing this issue when recording the audio from Microphone and streaming to the speech service,
I m able to get the text but after few seconds this below error comes up.

{ Error: Audio data is being streamed too fast. Please stream audio data approximately at real time.
at ClientDuplexStream._emitStatusIfDone (/home/pi/GoogleSpeechAPI/node_modules/grpc/src/node/src/client.js:270:19)
at ClientDuplexStream._receiveStatus (/home/pi/GoogleSpeechAPI/node_modules/grpc/src/node/src/client.js:248:8)
at /home/pi/GoogleSpeechAPI/node_modules/grpc/src/node/src/client.js:772:12
code: 11,
metadata: Metadata { _internal_repr: { 'content-disposition': [Array] } } }

@mudivili
Copy link

@shivag12, I am also facing same issue. Were you able to find a resolution?

@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 🚨 This issue needs some love. triage me I really want to be triaged. labels Apr 6, 2020
NimJay pushed a commit that referenced this issue Nov 9, 2022
🤖 I have created a release *beep* *boop*
---


## [4.2.0](googleapis/nodejs-containeranalysis@v4.1.0...v4.2.0) (2022-07-04)


### Features

* support regapic LRO ([1290f13](googleapis/nodejs-containeranalysis@1290f13))


### Bug Fixes

* **deps:** update dependency @google-cloud/grafeas to v4 ([#420](googleapis/nodejs-containeranalysis#420)) ([6e40ebe](googleapis/nodejs-containeranalysis@6e40ebe))
* **issue-417:** adding additional asserts to track flaky error ([#421](googleapis/nodejs-containeranalysis#421)) ([23cd446](googleapis/nodejs-containeranalysis@23cd446))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
telpirion pushed a commit that referenced this issue Nov 9, 2022
* feat!: Update library to use Node 12

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
telpirion pushed a commit that referenced this issue Nov 9, 2022
* feat!: Update library to use Node 12

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
ahrarmonsur pushed a commit that referenced this issue Nov 18, 2022
ahrarmonsur pushed a commit that referenced this issue Nov 18, 2022
NimJay pushed a commit that referenced this issue Nov 18, 2022
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

4 participants