I have used Windows 11's included dictation feature (Win + H) for several months now in order to complete my work as a medical transcriptionist more efficiently. To be clear, I don't mean the dictation tool included with Microsoft Word; I mean the Microsoft Voice Typing tool specifically designed for and included with Windows 11, as per this article.
The program is usually great, recognising obscure and complicated medical terminology fairly well, with only a few words requiring input manually. Combined with Microsoft Word's autocorrect feature, I rarely have to make edits to what I have dictated before sending it off for review.
The one thing I do regularly have to edit is punctuation - specifically, commas. Commas have been giving me grief for over a month now, and I have had to resort to using an AutoHotkey shortcut to pause dictation, insert a comma, and then reopen dictation for me when I press RightCtrl on my keyboard in order to minimise the impact on my workflow. However, as dictation tends to "buffer" (slightly greyed out text that is erased if you type anything before it has finished processing) for a second or two after you have stopped talking, this still means a two second break in my dictation flow every single time that I need to insert a comma in my work.
"Period" works fine. "New line" moves the cursor to a new line. Even "semicolon" or "open brackets" work like a charm. However, comma fails to work more than 25% of the time.
I have tried speaking clearly and enunciating to the finest degree. I have tried pausing for a second, saying "comma" loud and clear, then continuing. I have tried yelling as loudly as possible. Nothing prompts the program to recognise a comma. Most infuriating of all, sometimes I'll say "comma", and wait... and as expected, nothing happens. Realising that the program has not registered a comma, I will say "comma" again, and only then will the program whir to life... and insert ",,". TWO COMMAS.
For such a sophisticated, advanced, and presumably machine-learning-driven program, Windows dictation is laughably hopeless at inserting perhaps the second most common punctuation mark in existence. How this has not been noticed and patched by now is completely beyond me, as it grinds workflow to a halt in what should otherwise be a smooth and simple process.
Any advice related to this issue, or words of comfort from anyone who has experienced the same, would be greatly appreciated.