Forum Discussion
Edge can't use the mic in the Google Translate page
- My guess is that all these Tools use the WebSpeechApi which only works on Google Chrome/Chromium (at least the recognition part) because Google uses it's own cloud servers for the audio transcription. Since the new Edge is basically Chromium it probably thinks that the WebSpeechApi is supported and breaks. The API behaves very strange currently in Edge.
the problem that me and some others are having is with Google.com voice search
it still doesn't work in version 89.0.731.0 (Official build) canary (64-bit)
the top feedback list also refers to google.com
https://techcommunity.microsoft.com/t5/discussions/top-feedback-summary-for-december-8/m-p/1968074
see if you can get it to work on canary
Working fine for me in 89.0.731.0. I've only tried google.com and translate.google.com, but the experience is the same at both sites.
What happens when you try? Are you still seeing the error message I see on Stable?
I keep getting this error. no extension or tracking prevention is applied to it.
it shows me the prompt to allow mic access, then I talk and it shows the heart beat animation as if it's listening to my voice but then after few seconds, I get this
I'm assuming it's different from Google translate voice because that one works fine for me
HotCakeX wrote:I'm assuming it's different from Google translate voice because that one works fine for me
Does it work on the test page? Web Speech API Demonstration
Noel Burgess wrote:
HotCakeX wrote:I'm assuming it's different from Google translate voice because that one works fine for me
Does it work on the test page? Web Speech API Demonstration
yes, it works on there too, even though the performance of that site is bad. i speak hello and then after 3-4 seconds i see the word appear there.
so far, only Google search at Google.com is having problem.
which I don't really care since I use Bing. the problem could even be an intentional block from Google's side. because the evidence shows Web Speech API works, on Google translate and that Web Speech API test site.
I wrote about bugs in the Web Speech implementation here:
Re: Web Speech API support ? - Page 2 - Microsoft Tech Community
Basically Edge is very eager to throw "network" errors where it should throw "no-speech" and it occasionally drops the "onend" event which will probably break 90% of all pages using it.
- Hope a developer sees it or send it from feedback button on Edge, im afraid it might get lost in the forum