-
Notifications
You must be signed in to change notification settings - Fork 603
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
Surprising errors in production code using v2 of @google-cloud/speech #5609
Comments
Hey @sorokinvj, which file types are affected? |
Hey @danielbankhead, we are using real-time transcriptions.
Though our setup involved Currently we rolled back to v1 with this code and everything went back to normal:
on the frontend we are using basic new MediaRecorder api to send the data:
|
@danielbankhead We have the same use case and issue, it is very difficult for us to move to v1. Any update about it? It is considered critical to our system. |
WEBM OPUS should be supported:
I will see what’s going on. |
@danielbankhead |
Also experiencing this issue, also with WebM and seems to have broken a few days ago. |
Also experiencing this issue |
Update: the service team is aware of this issue; I should have another update soon. |
Any updates? |
A fix is rolling out and should be available shortly |
@danielbankhead any news on the fix? is it available all ready? do you know the release version I should be looking for? |
The issue is on the service side; no update required on the client side. The rollback should be rolled out by now, however I'm waiting for the service team to confirm. |
The fix should be widely available now. |
I can confirm that the problem is fixed. I sent an audio/webm file to the google-cloud-speech v2 recognize functionality and it worked (didn't told me that file format was invalid) |
Hey guys, our system today started to produce surprisingly many errors, our PROD server is affected and all our users.
We did not change any implementation and I hope that recent update of Google Chrome also did not touch audio interfaces.
We are using MediaRecorder API and up until today all users were happy and get their streams recognized successfully.
Here is our main service:
The text was updated successfully, but these errors were encountered: