11/20/2023 0 Comments Speech to text word 16![]() This affected all my cursor/selection commands, spacing-aware and capitalisation-aware commands, as well as camel case commands and the like. Otherwise the script typed over the selection, partially or wholly. 2 statements for scripts that used the clipboard before/after doing something else, like selection or typing. There are some other changes which messed up my old scripts at first but were easy to fix: Those problems aren't happening in Dragon 16 so far. So I was due for a reinstallation, I think. And my Dragon 15.61 had started refusing to exit. On the bright side, I was able to dismiss the tutorial from a new profile and it didn't nag me, unlike in my Dragon 15.61. I'm getting the impression that it helps to try them in WordPad and come back, but I haven't really figured out the pattern yet. (Dragon 16 also adds a space before every utterance, which is not helpful when you're typing code and it's the start of a line, but that's a trivial problem.) Weirdly, some commands just seem to stop working temporarily for no reason. This happened with Dragon 15.61 too, but only occasionally. With Dragon 16 I have to restart Notepad++ all the time in order for new commands to get recognised. Someone here said that Dragon 16 seems more reluctant to dictate in non-supported applications, and I think I see what they mean. In Dragon 16 the bad vocab item refused to be added in a new profile even before I had imported any commands or vocabulary. But it's here and it seems to have gotten worse. So I was really hoping this problem would be gone in Dragon 16. I would have to create a new user profile in order to add the bad vocab item. The symptoms are quite consistent: if I tried to add them again, it seemed to go fine, but they were listed in the vocabulary without the red plus sign that's supposed to appear on custom vocabulary, and next time I checked they would have disappeared. ![]() In Dragon 15.61 the occasional punctuation vocabulary item sometimes got lost and refused to get added back. And what I mean by unreliable is that sometimes an utterance will fail to be recognised as a command, or only the first word of an utterance seems to get heard, or recognition just becomes really inaccurate. I switched accuracy options from fastest to most accurate very early on, and that helped, but it's still happening. And it also gets tired faster (within the hour?!), and less predictably. But Dragon 16 seems really slow and unreliable at recognition just after starting up. I was hoping for more speed and stability, because Dragon 15.61 used to become slow and unreliable after Windows had been running for many hours, and then I'd have to restart the profile or Dragon or Windows. If you're not on Windows 11 or Office 2021, it's not really worth it. I upgraded from Dragon 15.61 to Dragon 16 a few days ago, and I've got to say, monkey8 was right. In the Alternates panel dialog box, say the number next to the item you want, and then "OK.Solved? Dragon 16 is going badly on Windows 10 To correct a single word, say "correct" followed by the word that you want to correct. To correct the last thing you said, say "correct that." Say "start listening" or click the Microphone button to start the listening mode. Open Speech Recognition by clicking the Start button, clicking All Programs, clicking Accessories, clicking Ease of Access, and then clicking Windows Speech Recognition. ![]() You can also add words that are frequently misheard or not recognized by using the Speech Dictionary. If the word appears more than once, all instances will be highlighted and you can choose the one that you want to correct. You can say "correct that" to correct the last thing you said. There are several ways to correct mistakes made during dictation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |