Registering and logging in removes this ad.
Registering and logging in removes this ad.
Dragon recognizing but not executing commands involving keystrokes
Submitted by Per Haglund on Mon, 05/07/2007 - 09:11.
I'm a fairly new user of Dragon and can't seem to find help for this problem that I'm having.
the Dragon incident number is 1152632
with version 8, I was experiencing problems with navigation commands, for example "press left_arrow", "press end key". sometimes they would work, most of the times they would not. every time they would be highlighted with a blue border, indicating to me that they were being recognized as commands. After some trial and error, I thought that the keyboard might be the problem. By switching from a wireless keyboard to a USB keyboard I did no longer have the problem.it seemed as if Dragon was turning off numlock and navigating using the equivalent keys on the numeric keypad, i.e. the key 4 representing left arrow, and then turning numlock back on again.
today I upgraded to version 9, and unfortunately the problem is back again. This time it seems that commands in general are being problematic. For example, sometimes I say close window three or four times before the window is actually closed. As before, each time the command is recognized with a blue border.
this also affects my vocola macros from time to time
I will be very grateful for any help or advice, thank you
I had DNS 9 until
I had DNS 9 until yesterday(updated to 9.5 yesterday). I had the same problem. But I never tested it out by changing my keyboard. I did not get to work in DNS9.5 long enough to see whether it still has this problem.
I worked around this in DNS9.0 for my most frequently used commands by using vocola macros for them. But having to write vocola macros for commands that are natively supported by DNS is something that I would like to avoid. I would be interested in knowing how others workaround this or fix this.
creating new macros is not
creating new macros is not always work either, for example I created a new macro to kill the window by pressing ALT +f4. It works more often than the Dragon command to close a window, but not always.
Is your sound quality good
Is your sound quality good enough? This can also sometimes prevent commands from being recognised,
Quintijn
Quintijn wrote: Is your
Is your sound quality good enough? This can also sometimes prevent commands from being recognised,
Quintijn
I believe so. The spoken text is correctly recognized and displayed on the yellow box. It is just that the appropriate command is not executed or so it seems.
-Vayup
Exactly, sometimes it can
Exactly, sometimes it can take me three or four attempts before I managed to close the window, although each attempt produces the yellow box with a blue border.
perflubron, FYI, I am
perflubron,
FYI, I am having the same problems as you. They started after installing V9.5, so I rolled back to V9.1 -- still no joy. If I remember correctly there was also MS OS update at about the same timeframe and this may be the culprit. In addition to the problems with "press keystroke" commands I also have problems with "select (next|previous)1..10 words" commands, as well. Like you, I have to issue them twice (or more) to have them execute.
Maybe someone will offer a solution or at least more clues.
-Coop
perflubron wrote: I'm a
I'm a fairly new user of Dragon and can't seem to find help for this problem that I'm having.
the Dragon incident number is 1152632
with version 8, I was experiencing problems with navigation commands, for example "press left_arrow", "press end key". sometimes they would work, most of the times they would not. every time they would be highlighted with a blue border, indicating to me that they were being recognized as commands. After some trial and error, I thought that the keyboard might be the problem. By switching from a wireless keyboard to a USB keyboard I did no longer have the problem.it seemed as if Dragon was turning off numlock and navigating using the equivalent keys on the numeric keypad, i.e. the key 4 representing left arrow, and then turning numlock back on again.
Although this might be a problem with your wireless connection, which I suspect is a USB connected wireless radio transceiver, it has nothing to do with your keyboard itself. Keyboard and keypress controls are all handled by COMMAND.COM (yes, Windows still uses MS DOS). One of the built-in functions of COMMAND.COM is what is called "CON" which stands for CONsole and which monitors and controls the keyboard and the monitor. These are all part of the CONsole function and is initiated by the BIOS and COMMAND.COM at boot time. Therefore, the wireless keyboard itself has no impact on DNS and keystrokes. You could totally disconnect your keyboard altogether and DNS would continue to work with regard to voice commands for keystrokes and other CONsole functions.
However, as I said, it could be a USB problem or a wireless connection problem (i.e., conflict).
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS
"As far as the laws of mathematics refer to reality, it is not certain. As far as they are certain, they do not refer to reality." -- Albert Einstein
Thanks for your feedback so
Thanks for your feedback so far. Perhaps I should clarify my setup at the moment. I'm no longer using the wireless keyboard, but a USB keyboard instead. When I had Dragon version 8 installed on my computer, with the USB keyboard, there were no problems.
As of yesterday I'm using Dragon version nine. I have problems with commands to close windows and press keys (probably others which I don't use).
I have NatSpeak and vocola installed, my macros work apart from the ones which press keys which sometimes also fail (for example a macro which presses the up arrow a certain number of times).
I just installed Dragon 9.5,
I just installed Dragon 9.5, and so far it seems that the commands are working better. I will let you know how I get on.
perflubron wrote: I just
I just installed Dragon 9.5, and so far it seems that the commands are working better. I will let you know how I get on.
It executes the commands more frequently, but there are still situations when it takes several attempts before the command is executed.
For the moment I've rolled
For the moment I've rolled back to version 8...
perflubron, I think I found
perflubron,
I think I found a solution to this problem (still testing). It works on my system, at least. The solution is to kill the process "ctfmon.exe" from within the Task Manager. Now, I don't have to repeat commands multiple times in order to have them executed. By the way, I am now using V9.5, as well.
Apparently ctfmon.exe causes several problems with DNS. Do a search for "ctfmon" and you will see a few. Nuance is supposed to have a Technote to permanently disable "ctfmon.exe", but I haven't found it, yet.
Give it a try -- your mileage may vary,
-Coop
Coop, Try Dragon TechNote
Coop,
Try Dragon TechNote 3244:
http://knowledgebase.nuance.com/view.asp?tnID=3244
Graham
www.itspeaking.co.uk
Thank you Graham, I knew
Thank you Graham,
I knew there must have been a Technote -- I just hadn't found it, yet.
-Coop
Thanks! I killed the process
Thanks! I killed the process this morning, and so far so good. All commands are being executed when recognized. Assuming that it continues to work today I'll be back in version 9.5 tomorrow. I am a bit surprised that the support staff at Nuance failed to pick this one up but I will let them know about the resolution.