I'm having an issue with starting Bing to listen right after EZ Builder starts. I cant start it listening by clicking the Start Recording button or starting it from an EZ Script with the start listening command.
The only way I can get the control to start recording is to go into it's settings page and click on the Save button. Then when I exit back to the front of the control everything is working right. The control will continue to work correctly until I restart EZ Builder. Then I need to do the above all over again.
Any ideas what may be going on here? I turned my Windows Defender off but nothing changed. I have no other antivirus running.
I'v attached a Youtube vid of what is happening.
Thanks!
Asked
— Edited
- on first start of ARC it comes up that theres no api key
- open settings key is there
- click save and everything works fine until ARC is shutdown and restarted
Check to make sure the api keys are set again as nick777 mentioned. I think the update that DJ pushed removed the keys due to them now being stored differently. This will happen on the cognitive recognition stuff and on API.AI also. Once this is done it should fix the issue for you for good. I noticed that they stopped working on Spock after the update to these plugins but haven't looked into it yet.
Let me know if nick777's suggestions work out for you. I think that they will.
Interesting though, I did delete the control at one time before this issue started up and reinstalled it. I remember seeing my key already inserted on the new control. After hearing your explanation I'm sure this caused it.
So, when you say "set the key" do you mean delete the old one and reenter the new and save?
Thanks again!
I cleared the Key box in the control. Shut down ARC and rebooted windows 10. I then went back in the Bing control and reentered my key and saved.
Everything was working again until I restarted ARC. Same issue as before, Cant start the Bing control until I go into settings and click on save. *confused*
I went back in and clicked Save again bit the issue stays.
Here's what I tried:
Deleated the ARC Voice Rec control
Deleated the Bing control and reinstalled it.
Started a new project with only the Bing control installed.
Compleatly uninstalled ARC and then reinstalled the latest version.
Started a new project on a new computer with only the Bing control installed.
Each time in the above stepts I deleated the KEY in the control and reset it. I then exited the project and then restarted the project (several times).
Only thing left is to some how uninstall the Bing plugin from ARC and reinstall it. How do I do that? I noticed that I always have the Bing plugin in the Add To project section even after I reinstalled ARC.
Help please. Any other ideas? Anyone else stillhaving this issue? *confused*
click the gear on the bing speech plugin
click OK on the window that opens up
see if you can use the plugin.
This is what I have to do to use it. I am curious if you are having the same issue.
When I first start ARC, the Start Recording button on the plugin control is unresponsive. I then click on the Gear Icon and after the settings page opens I click on Save. After this action has been done the control works great. However the next time I start ARC after it's been shut down for the day, I have to again click on the Gear Icon, then after the settings page opens, I again have to click on Save to get it to record again. This continuously happens each time I start a new session by opening ARC for the first time.
Alan
Thanks again.
I too have seen this, I'm late to this so I may have missed something.
Question, do you have to login to Microsoft's API site for this API to work? I've noticed if am not logged into that site I get a transport and login failed in the bing speech window of ezb. After I login it works fine. Am I doing something wrong?
Thanks,
You shouldn't have to login to Microsofts API site for these to work. The API key is kind your login.
DJ has published updates to these plugins. I won't have time to check them out until tonight or tomorrow. I assume that these updates were to address this issue. If nobody else checks them out before I can, I will post an update letting people know if the issue is resolved.
And of course thanks to Dj for the updates!