google-cloud-node icon indicating copy to clipboard operation
google-cloud-node copied to clipboard

streamingRecognize on speech v2 does not work

Open sofisl opened this issue 7 months ago • 4 comments

Please make sure you have searched for information in the following guides.

  • [x] Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
  • [x] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
  • [x] Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
  • [x] Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
  • [x] Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
  • [x] Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
  • [x] Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples
  • [x] Check the API's issue tracker: https://cloud.google.com/support/docs/issue-trackers

A screenshot that you have tested with "Try this API".

N/A

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://buganizer.corp.google.com/issues/408977549

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

Not sure yet but there is a workaround, we need to investigate

A clear and concise description of what the bug is, and what you expected to happen.

Should work with the public method, not the internal method

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

Seems like it has been broken for a while given stack overflow workaround https://stackoverflow.com/questions/76722471/how-to-setup-streamingrecognize-google-cloud-speech-to-text-v2-in-node-js

sofisl avatar Apr 29 '25 20:04 sofisl

it does not work whatever you do. we are having problems migrating to v2 because of this.

uzbeki avatar May 09 '25 06:05 uzbeki

@sofisl I would like to request an update - I am a CE at GCP and have multiple clients asking me about this bug.

Why are we using a pseudoprivate _streamingRecognize? Do we have guidance on which should be used and why?

Additionally, I am at a loss for how to leverage chirp 2 from this method. It demands that I leverage a global recognizer but I cannot leverage a global recognizer for chirp2 - I can only leverage a regional one. I have code and examples ready to share if necessary.

manbeardave avatar Jun 02 '25 22:06 manbeardave

We shouldn't be using it, we should be using the top-level streamingRecognize, but it's broken right now so the workaround is to use the private method.

sofisl avatar Jun 05 '25 22:06 sofisl

See https://github.com/googleapis/google-cloud-node/issues/3952#issuecomment-1440325529 for streaming implementation.

chirp and chirp2 are not supported in global, only in us-central1, europe-west4, asia-southeast1. chirp3 is in us only.

orgads avatar Oct 01 '25 07:10 orgads