No, Dragon NaturallySpeaking did not suddenly get all its speech-to-text recognition correct for the last month – it’s time for some catch-up. Or “some ketchup,” depending on the quality of your microphone. February’s blunders:
What I actually said to my computer: A couple of FYI’s
How my voice software translated it: A couple of FY eyes
What I actually said to my computer: Thank God.
How my voice software translated it: Think God.
What I actually said to my computer: …and then I ran.
How my voice software translated it: …and then Iran.
The day that Dragon NaturallySpeaking made me a real Debbie-Downer:
What I actually said to my computer: Let’s dance!
How my voice software translated it: Less dance!
And one more:
What I actually said to my computer: Castaic Lake
How my voice software translated it: To stay at lake
A fine February indeed.
I’m really not as crude as my voice software thinks I am. What I actually said to my computer in an e-mail to a friend: The woman I had been wooing… but what Dragon NaturallySpeaking typed: The woman I had been doing…
What I actually said to my computer: I do ramble. But how Dragon, my voice software, translated it: I do Rambo. That’s just way too much information.
And one more, also from this morning. What I actually said: denims and wools; but what Dragon heard and typed was The Nims and wolves.
I’m not even sure who, or what, the Nims are, do you?
Trying to write down directions, what I actually said to my computer via Dragon NaturallySpeaking: 264 Lane street. But how Dragon wrote it: 26 four-lane street…
I think Dragon was trying to get me lost.
What I actually said to my computer: “…foreign voices.” but what Dragon NaturallySpeaking wrote: “…for invoices.”
What I actually said to my computer while creating an article about B12 supplementation: “colorectal cancer risks.” But what my voice recognition software typed: “co-director cancel risks.” Definitely a surprise side effect of too much B12.
The iPhone’s voice recognition is pretty good, but not flawless. Take this example from one of my friends. What she said to her phone: “When should I be at your place?” but her iPhone typed, “When should I be at your penis?”
Particularly awkward since she didn’t catch the error before hitting send.
Unfortunately, I did not catch this voice recognition error before hitting “send” on the email. What I actually said to my computer: I hope you are well, Chasta. But how Dragon, my voice software, spelled that: “I hope you are well, chested.”
Easily the most inappropriate voice recognition software blunder so far this year! Responding to an e-mail from a client, what I actually said to my computer: Thanks for your thorough response! But how my Dragon software translated it: Thanks for your poor response! And no, I did not catch the error – not until the confused client replied, asking for clarification.
My only salvation was the fact that my client has a good sense of humor and assumed I was making some kind of joke.
This type of error is an impossible thing for voice software to do as well as a human. If I’d not spoken clearly enough, even a human might hear the same thing: “poor” instead of “thorough.” The difference: a human can understand the context of social norms and recognize that they must have misunderstood because surely a business associate would not openly blurt out an accusation like that.
But not Dragon NaturallySpeaking. Poor Dragon.
A good candidate for our predictive text/AutoCorrect category, this one from the Facebook post of a friend:
“I’m seriously not that bad of a speller, but when I typed melancholy I really thought it would figure out that I meant MELANCHOLY and not “melon holy”…. Uh… when have you ever heard someone say, ‘You know, you seem a bit melon holy today.’… Stupidy stupid.”
I never heard of such a thing, but apparently Dragon NaturallySpeaking has. What I actually said: “When the plans firm up…” But how Dragon translated it: “When the plants sperm up.” And that was in an email to a business associate. So glad I caught that before hitting “send.”
Dragon NaturallySpeaking excels not only at voice recognition, but at voice recognition errors. Here’s 2 funny ones from this week. What I actually said: “They’ve got a sense of humor.” But how my Dragon translated it: “They got us into humor.”
How dare they!
And, boy, did it go off base on this next one. What I actually said: A Shakespearean technique. How the voice software translated it: “Each experience acne.”
Must have been a young cast, is all I can say.
I know regular subscribers understand, but, for the rest of you and for the record, these posts are the inaccurate transliterations of my voice software, not my actual words. That said, here’s a doozy:
What I actually said to my computer: Jubal Sackett book (a famous novel by Louis l’Amour), but how my voice software translated it: Jew ball sack at book.
To say the least, Dragon NaturallySpeaking (DNS) is not well versed in the novels of Louis l’Amour. And it is definitely capable of being politically incorrect, and frequently stumbles when trying to understand names. Fortunately, I caught this voice recognition software error before hitting “send” on the email.
Here are three items you can find in most health food stores – herbs that are popular with people on particularly healthy diets. Unfortunately, Dragon didn’t have a clue how to handle these.
For example, what I actually said to my computer is “Astragalus,” but my voice software translated it: “as stragglers.”
Another Dragon NaturallySpeaking fail that occurred as I was vocally typing out a shopping list for a friend: What I actually said to my computer: “Get Stevia and…” but how my voice software translated it: “Get Steffi at hand.”
And one final voice recognition software error with health food: What I actually said to my computer is “Ashwaganda.” But how my voice software translated it: “Ashwood ganja.”
Well, many people do call ganja an herb. 😉
Dragon NaturallySpeaking often has trouble with names – personal or brand names. Starbucks menu items are no exception:
What I actually said to my computer: Frappuccino.
How my voice software translated it: Fred Pacino.
A friend of mine recently attempted to get her Apple iPhone’s Siri to understand a common, simple word: barista. No luck. How Siri’s voice recognition translated it: Paris stuff. A friend of hers tried it herself, and Siri failed again: bar restock.
Clearly, Siri hates coffee.
You know that old adage “Feed a cold, starve a fever.” Or is it “Feed a fever, starve a cold”?
According to Dragon NaturallySpeaking, it’s neither. What it typed when I said the former: Feet are cold, star receiver.
Honest, I was talking about the long-snouted creature that eats ants. Clearly, Dragon NaturallySpeaking didn’t understand:
What I actually said to my computer: ant eater.
How my voice software translated it: aunt eater.
I tried once more, and got one more fail: and eat her.
Two recent voice recognition errors that I wish I’d caught before hitting send:
What I actually said to my computer: dinners and galas
How my voice software translated it: dinners and gay laws
And one more:
What I actually said to my computer: Yay, thanks
How my voice software translated it: gay, thanks
Watch out, people – protect your laps!:
What I actually said to my computer: I can film the lap
How my voice software translated it: I can feel the lap