I have tried everything I can think of, to no avail.
Thomas Reid2019-04-30 16:38:01
I have tried everything I can think of, to no avail.
A few weeks ago I had the following problem:
Yes, you posted about the page down problem.
I no longer have the problem with the default setting in Dragon since restoring it this afternoon. The activate command has been working just fine all afternoon. I’m also having no problem with the page up and down command now as well. I will put it down to a glitch in the Dragon profile somewhere along the line.
I need some more advice. Please take a look at my log snippet from this morning. I have a conference call every morning where I was reading some text. I kept getting voicecomputer popping up wanting to restart. Here is a snippet of the log:
Since the two commands are Activate Microphone and Activate VoiceComputer, the speech engine is trying to match everything you say to these two phrases. In other words, when you say NaturallySpeaking, how confident is the speech engine that you said, “activate voice computer”. Logically, it should be only 5% confident. But, the engine will probably report that it’s 80% confident that you said "activate voice computer."
Thanks again Ron,
I have been thinking about the confusion that I’ve been having with this issue. I have used the configure microphone command several times and thought I was using it properly. However, I believe the confusion is that the number that it is producing should be the secondary number.
I was reading the instruction to mean that the number suggested by the configuration command> should be the primary, and that a slightly lower number would be safe for the secondary.This is correct.> In fact, it is the secondary number that actually trips the lookout for a second call for the instruction.> So, if the secondary number is too low, then almost any utterance trips a call to the command> (false positive).I believe that all three statements are correct. But, we’re not on the same page because you see a contradiction and I don’t.I typically set my primary setting to 95% and my secondary to 93%.When I issue a command, it’s typically understood with a confidence level of between 93 and 96%.So my primary command is only understood 60-70% of the time.If the primary command is not recognized.(Let’s say the command is only recognized with a confidence level of 93.2%.)The 93.2% confidence level trips the lookout for a second call for the instruction.I then repeat the command within 3 seconds. (which gives me plenty of time to see that the command is not recognized and to say the command a second time.)If the program understands my second command with a confidence level of 93% or higher (the program typically understands my secondary command 98% of the time) then the program carries out the command.I get very few false positives with these settings.But, if you get a lot of false positives, look at the log file.1) If the program is giving you false positives because it’s misunderstanding random words as a command word, increase the confidence level of the primary command.2) If the program is giving you a false positives because it’s misunderstanding random words as command words twice within 3 seconds of one another (with a confidence level higher than your secondary settings, increase the confidence level of the secondary setting.In the meanwhile, we hope to introduce an update to the microphone feature in the coming months. The update will include a large vocabulary and maybe a short training. Both these features will increase performance of the VC Mic. (The training may come in a later update.)In our own testing, these features don’t seem to make a lot of difference in the accuracy of the Mic.But, we get such good accuracy with the feature, that it’s hard to tell.However, the improvements should help those who aren’t getting the great results that we are.
Once I set my secondary to a much higher level than I had before (as mentioned, to the number suggested during the optimize process), my false positives have gone away. My success using the double command process works extremely well now. It now works exactly as expected.
Great explanation!!! I’m glad that I asked.
here we go again. I was not having any problems after getting the right numbers in the configuration file. The current logs are telling me that the “activate microphone” command is being heard quite consistently at around 94.5%. I have set my values near that number, and well below that number. However, after installing the 2020 version, I’m having problems with just this one command as far as action. Like I said, the program is recognizing the command just fine, but nothing is happening-if the microphone is off in Dragon, it will not restart when I give this command. I was having no problem just before the installation.
Please email me the VC_MicrophoneLog.txt in the C:ProgramDataVoiceTeachMicrophone directory
looks like the culprit was that my Dragon hotkey for turning the microphone on and off was empty.
I just rediscovered why I changed my default hotkey values in Dragon. When I give the> command “press enter”, dictated twice, it turns off my microphone.Yes, you and/or someone else reported this some time back.Does the enter key and numkey+ share the same key on your computer?There’s a ‘Enter two’ (enter <1-20>) command in VoiceComputer, not VoiceComputer lite.Could you use this instead of “press enter”, dictated twice?Or, you can try another hotkey for the Dragon mic. (You have to restart the VC Mic)> However, one of the recognized strings for commands three is "activate microphone"That wouldn’t be the case in the next update…