As good as SpeechStart+â„¢ is, it really doesn't hold a candle to the VC microphone. The reason for this is simply because SpeechStart+â„¢ contains too much bloat. Since we separate out the VC microphone and don't require any training, it's simpler and easier to use.
Note that the VC microphone has the same capability to turn the microphone on and off as SpeechStart+â„¢.
The InTags and My InTags features in VoiceComputer are more comprehensive than those in SpeechStart+â„¢. For example, VoiceComputer's Chrome extension is capable of numbering links in Google Chrome, whereas SpeechStart+â„¢ can't. SpeechStart+â„¢ can only number the "menubar" in Google Chrome.
VoiceComputer's InTags allows you to manipulate and select emails in the Outlook inbox, whereas SpeechStart+â„¢ does not have this capability. Note that we separate the InTags features from the VC microphone to avoid the kinds of issues and complications that can arise from using SpeechStart+â„¢. Also, trying to use both the VC microphone and SpeechStart+â„¢ will create conflicts. Use one or the other, but once you get used to the VC microphone you'll find that it works much better. Never use both.
Lastly, you will run into a number of conflicts when attempting to use KnowBrainer and VoiceComputer together. For example, if you launch KnowBrainer, which automatically launches Dragon, and then you launch VoiceComputer, the KnowBrainer commands will take precedence. In this case, VoiceComputer's InTags and My InTags will not work. You will get KnowBrainer's "DISPLAY numbers", which are generally not very efficient. On the other hand, if you launch VoiceComputer, which also launches Dragon in the same way as KnowBrainer does, then the VoiceComputer commands will take precedence over the KnowBrainer commands.
Trying to mix-and-match KnowBrainer and VoiceComputer is ill advised simply because you will create more problems than you'll solve. In short, use one or the other, but not both simultaneously. If you simply must use both, which we do not recommend, then launch VoiceComputer first and then open KnowBrainer. Still, the best approach is using one or the other, but not both simultaneously.Chucker2017-09-07 07:56:52
Thank you for the feedback. We have never tested the multiple monitor settings in VoiceComputer relative to a monitor set up in "portrait" display mode.
Unfortunately, we are not in a position to test this at the present time, but I'm not surprised that this can be a problem. We'll try to do our best to take a look at it, but setting a monitor up in "portrait" mode is unusual relative to the average user who is using VoiceComputer with multiple monitors.We've never given that much thought because no one ever asked or noted a problem with such in the past.
As regards "place window upper left | right | lower left | lower right", we eliminated these some time ago as being, for the most part, impractical. "Place window screen left or right" is not a command. I would ask you what it is that you're trying to do via that command? If you're trying to place a window on any specific monitor, the command would be "place window on monitor | screen #" where #= the number of the monitor to which you want to move the window (place the window).Chucker2017-09-09 07:13:32