Forum Discussion
Edge can't use the mic in the Google Translate page
Edge Canary and Dev don't seem to know how to use a microphone. I tried the following steps both on a workstation connected to a Logitech's Brio webcam's microphone, and a Surface Pro 4 using the built-in microphone.
1- Go to Google's translate page www.translate.google.com
2- Select a language to translate from
3- Click on the microphone icon in box for the language of origin
4- Authorize access to mic if requested then start speaking when prompted
5- Expected result: Edge uses the mic to listen to what I say
6- What's happening: Edge doesn't pick up anything from the mic.
Google Chrome has no difficulty using Brio's microphone nor the Surface Pro 4's. Windows' Voice recorder also has no difficulty using the same mic.
- 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.
56 Replies
The mic works for me when I use Skype on the Canary build.
Not the same as what your doing, but it picks up and uses my webcams mic(Logitech C270) using Windows default drivers for mic & video as there are problems with using the Logitech drivers and running Core Isolation - Memory Integrity, probably Logitech won't update their certificates for it😉
So try using the default drivers for your mic.
Device manager
find driver(Audio inputs outputs)
select update driver
select browse computer
select let me pick
select default "Audio inpoint"Audio Endpoint
Deleted I checked my driver and it is not signed by Logitech but by Microsoft. It uses the Generic USB Audio Device. The driver provider is Microsoft and the driver date is 2019-05-08. My Surface Pro 4 has the same problem using its own microphone.
Try the Skype online(if you have a Skype account): https://web.skype.com/
and use the Echo / Sound Test service call, and see if that works.
