bigjake620
Resolved by Perry_S!
Can someone help me with getting my speech recognition to work in Windows 10 on my new PC? It works fine on an older windows 8 PC that I had been using.
I added the microphone control to the project to make sure that it hears the microphone. That works.
In the speech recognition configure menu, when I speak the levels tab on the side goes up and down. So the microphone seems to be working. I'm using an external microphone.
There isn't a line readout in the speech recognition control in the upper right corner as there is on my windows 8 version. So I don'tbelieve the module is connecting to the speech recognition part of microsoft. No confidence number or anything. This is what my project looks like:
When I open microsoft word, I'm able to get the dictation working. So I believe the speech recognition part of microsoft works, but it doesn't appear to connect to ez-robot.
Any help would be appreciated. I've been struggling with this for a few days.
Related Hardware (view all EZB hardware)
mine is same as perry.
I can reproduce the issue by changing this from ON to OFF. It should be ON
Yes, I have the switch "Allow apps to access your microphone" turned on. My build is the same as Perry_S.
Unfortunately did not fix the issue on this machine. Mine was "ON". I turned it off then, back to on. No change.
below are more setting to put in on position.
Yeah - good find nomad. I also found this... https://maxedtech.com/fix-microphone-not-working-in-windows-10-1803/
mine destop appvieuwer says off.
OK....when i looked where nomad pointed...i had ARC open but was not showing up there, but the Speech runtime exe was showing in use. I turned off the "on" to "off" then back to on. The Runtime no longer showed it was in use and would not come back online. So i shut down ARC and rebooted the computer. On reboot a windows update was applied. I restarted ARC and revisited the microphone privacy settings and I had ARC now listed....and IT WORKS in ARC!
So was it the windows update on reboot, or killing the speech runtime and rebooting that did the fix?! Someone will have to confirm which one did it.