Dragon Dictate 2.0 for the Mac

I have been a bit harsh on MacSpeech in the past, but since then they have been bought by Nuance (makers of the excellent Dragon NaturallySpeaking dictation software for Windows). If there is anyone who can finally release a decent dictation application for the Mac, it’s them. And recently they released the rebranded Dragon Dictate 2.0. Looking forward to finally not having to launch Windows in Parallels Desktop every time I want to dictate something, this of course filled me with much joy and hope. But judging by¬†MacSpeech’s own forums this version has caused a lot of problems for many people, first and foremost because of a bug which crashes the application when you launch it! After making absolutely sure that I can indeed get my money back within the first 30 days if the application is not working properly and am therefore in no way running the risk of giving even more money to MacSpeech for a faulty product, I bought and installed it. The aforementioned bug was easily avoided by leaving the start-up mode to “Idle – Microphone off”.

Here are the results of the first test:

She sells seashells by the seashore.

Impressive. How about this one:

How much would be debuted chuck chuck if a woodchuck could chuck wood
How much would with a booby-trapped truck if it would chop the truck would
How much would really would truck truck even good truck woodchuck would

The first one was pretty close, the rest not so much, but in all fairness it’s a very tough phrase. And all in all the accuracy is outstanding. Even better than Dragon NaturallySpeaking 10, which is only natural considering it is using the same underlying engine as Dragon NaturallySpeaking 11. The editing commands are at first confusing for someone who is used to Dragon NaturallySpeaking (when I started this post I was actually planning on doing a fair bit of complaining about them), but by now I’m pretty happy about them. There are occasional crashes and bugs, like sometimes leaving out the last character when dictating single words or punctuation (which, in the latter case, leads to a whole lot of nothing). But when Nuance fixes those I think we finally, at long last, have a good dictation solution for the Mac.

What is wrong with MacSpeech?

The tale of a software with potential, near-monopoly status and a lot of upset users.

MacSpeech Dictate is the only usable dictation software for the Mac. I’ve been using it since the beginning of January, and the speech recognition is pretty good most of the time. Especially considering I’m not a native speaker and have a tendency to slur. But the software has its problems. There’s a very limited set of text editing commands, and the only ones I can get to work on a regular basis are the ones for selecting words and replacing/deleting them, and moving the insertion point (but only between words). The built-in notepad is the fastest place to dictate into, but sometimes it types the words backwards, or inserts the same text repeatedly in the wrong place. And if you use it long enough it will eventually crash, leaving your carefully dictated text in binary afterlife. Dictating into Firefox leads to sudden and unexpected line breaks and spaces, same thing with Xcode, Pages from iWork is better but the only applications completely free of such frustrating appearance of unwanted whitespace are Mail and TextEdit. In TextEdit, however, moving around and selecting text is excruciatingly slow. You end up spending almost as much time waiting as dictating. Occasionally, Dictate will select all or parts of the text and remove it. The only way to teach the software new words is to write them into a text file, save it, and then open it with the Vocabulary Training command. And then hope that this time, it will work. My first user profile stopped working after two months so I had to create a new one and start from scratch. Sometimes Dictate just stops responding or starts misinterpreting everything I say, which a restart may or may not fix. It will only on rare occasions recognize the word “cell”, and never recognizes “app”. Which is inconvenient for someone who only writes about iPhone programming. And it never learns from its mistakes. There’s more, but I think I’ve made my point.

So with me and many other users experiencing serious problems with version 1.3 of a software we had paid $200 for, what do you think MacSpeech did? I will get to that, but first let me speculate about why they did it.

Read More