Something is seriously wrong with the training side in the toolkit and I don't think I would be alone

 

Are you mixing up the WSRToolkit (developed by us) with WSR developed by Microsoft? The WSRToolkit is just a tool. If there are flaws beyond our control we should not be blamed for them. I would start with looking at your microphone as no microphone used at a long distance will be as good as a good noise canceling close talk microphone. You said on the forum, “after wasting a lot of money on more expensive units over the years.” You don’t say what these more expensive units are? We could not find any record of purchases from us other than the WSRToolkit? There may be more expensive microphones that are not good for speech recognition.

 

would I? I don't really understand the ratios of the sound setup too well, but nothing has worked above about 60% accuracy unless in dead silence.

 

We read your post. I can guarantee the problem is partly the microphone and also the audio subsystem of Vista and Windows 7. We don’t recommend any long distance from mouth microphone and especially not a Labtec.  If you pull out one of your expensive close talk microphones and set the Input volume to 20% and the Input SNR to 12 (as a starting point) you will see good results.

 

Marty Markoe, eMicrophones, Inc.

This forum and our eMicrophones forum use the exact same software and reside on the same server. We've never heard of the forum software timing out. I'll leave this running while I go have dinner and then post. It is now 6:35 PM GMT -5

 

Also, I learned long ago when using Dragon to dictate to text fields in Internet Forums that it was dangerous to dictate directly. Too often, words dictated were interpreted as commands that took one out of the text window and when click back all text would be gone. For many years we've dictated into the Dragon Dictation Box and now with WSR we have a macro called OpenDictationBox.WSRMac that let's us dictate to Word Pad and transfer text to an Internet Forum text field.

 

Marty

 

PS. Finished dinner and posted this at 7:19.

 

1. The audio subsystem problems with Windows Vista and 7 are well documented. Our Tune Microphone feature will override Windows. Number 3 in the Readme section:

 

Have you followed the above?

 

2. How did you add your own text for training? What was in the text?

 

3. What do you mean the type of microphone has to be reset? Are you running the Setup my microphone utility?

 

4. If you believe WSRToolkit is the culprit with your reduced accuracy, simply uninstall it. Of course you used the Manage Profiles feature to backup your speech profile before playing with new features?

 

Marty Markoe

 

If you are referring to Bluetooth, you are incorrect. Bluetooth samples audio at 4 kHz except for the VXI Xpressway which has been reworked to sample audio around 9-10 kilohertz and thus be close enough to Dragon NaturallySpeaking's requirement of 11 kHz. WSR samples audio at 16 kHz and basically there's no Bluetooth that will work well with WSR because of the difference in sampling rates.

 

By the way, antihadron whose post you were responding to is the programmer who wrote the code for the WSRToolkit. He understands audio quite well as you can imagine. 

 

Marty

 

antihadron wrote:

"I've found that WSR is more sensitive to microphone quality than is DNS. I've tried to use cheapo headsets.  WSR picks up every bit of background noise while using them.   Also had problems completing training. "

 

It sounds to me like everyone is on the same page. One of the programming requirements for the WSRToolkit Version 2 was for the Tune Microphone function which works great.

 

Marty