[crawrj]

Originally Posted by xyzzy

As long as you guys are tinkering with the registry settings for Voice Command, you may want to try making this change...

Try changing HKLM\software\microsoft\voicecommand\speech\Reject ionThreshold

from 45 to 10

This setting determines when Voice Command says "Please Repeat". If the confidence score from the recognizer is below that threshold and above the ignore threshold (10) it will ask for a repeat. It turns out the engine is getting it right plenty of times and we're throwing away a perfectly good recognition because this threshold is too high. Change it to 10 and you might find you get better accuracy.

Another one you might want to set:
HKLM\software\microsoft\voicecommand\speech\Blueto othPTTDelay

this one isn't actually set anywhere by default, but it does have an impact. By default, when initiated via bluetooth, Voice Command will open the bluetooth audio gateway, and then wait for 400 ms before playing the audio indicator. Well, on the jawbone, it seems that keeping the audio channel open a bit longer improves accuracy. Also, this value is apparently too small on some headsets and results in some people not hearing the audio indicator. So you might want to try setting this value to 2000 (the maximum), which will cause VC to open the audio channel, wait for 2 seconds and then play the indicator.

Thanks for the find I will test it out and see how it goes.