-
Notifications
You must be signed in to change notification settings - Fork 92
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
Translation Recognizer #511
Comments
Can confirm this is broken as of yesterday. Looking at the network tab, it looks like there is a loop when trying to switch the websockets protocol. There must have been a server-side change of behavior, because several projects stopped working simultaneously without any changes / updates. |
Yes @eluchsinger, today I analyzed the network tab and saw that it is really in a loop doing a protocol switch on the websocket. Is microsoft aware of this? Is there any way we can open a ticket directly there to know the status? |
@filipe-campos @eluchsinger Thanks for writing this issue up. We are aware of this issue, and merged in a fix last week. The last working version for translation is 1.18.1, and the next release, v1.21 (which includes this fix), is expected mid-April. |
@glharper I understand. Thanks for the update. Shouldn't this be an urgent hotfix though (v1.20.1)? Because a lot of projects are broken now... The downgrade seems to work for me. |
@glharper Thanks for the info. @eluchsinger I agree with you, I believe it should be a hotfix too. |
Speech SDK 1.21 was release. See release notes: https://docs.microsoft.com/azure/cognitive-services/speech-service/releasenotes?tabs=speech-sdk#speech-sdk-1210-april-2022-release |
Apparently the Translation Reconizer is not working anymore, the Azure example itself is not working and also the demo site is not working either.
Azure example:
https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/js/node/translation.js
Site demo:
https://azure.microsoft.com/en-us/services/cognitive-services/speech-translation/#features
Anyone else having problems?
And it doesn't return any error or information, it just doesn't perform the translation.
The text was updated successfully, but these errors were encountered: