Closed LexiconCode closed 6 years ago
I don't think I've experienced this. What version of DNS are you using?
I have experienced it with DNS 13, 14 and 15. The frequency seems to become much more pronounced in 14 and 15. I'll make a video of it next time and post as a example.
I've never experienced this myself. Does this happen with different programs?
That would my next question. If it happens with a specific program or programs. I actually don't use free dictation in many programs. When I need to do dictation rather than code, I tend to mostly dictate into notepad and then copy/paste.
Actually, now that I think about it... I have had problems with dictation stopping working in Outlook 365. But I have so many other problems with Outlook that I figured it was Outlook's fault.
It can happen with any program even those that aren't supported by dragonfly or caster. That makes me think it's a bug related to DNS. The only thing I have Not tested is whether or not it's a side effect of using NatLink causing a bug within DNS.
Closing this issue but others can feel free to post the find they have a issue similar to this as described.
This is most likely a bug within Dragon NaturallySpeaking itself but I want to understand if other people are experiencing it.
The description of the problem can be described as freely dictating within an application all the sudden Dragon NaturallySpeaking doesn't recognize free dictation. However it does recognize global commands within the same application.
So if you have application
A and B
When dictating in application
A
DNS suddenly stops recognizing dictation"please say that again"
BringingB
application in the foreground and dictate everything works as expected. If you quickly switch back to ApplicationA
Free dictation is still unrecognized. In the event that you stay in applicationB
long enough a number of minutes and switch back toA
the issue may resolve itself. If you try to wait it out an applicationA
may or may not resolve.