<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d9519466\x26blogName\x3dthe+spkydog+koop\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dTAN\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://spkydog.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://spkydog.blogspot.com/\x26vt\x3d-4534400202552370894', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Thursday, April 27, 2006

Comparison of Dragon Naturally Speaking and Microsoft

I just came across this recently published comparison of Dragon Naturally Speaking 8 and the dictation engine Microsoft ships with Office 2003. This is one of the most indepth comparisions of these products I've seen, and if you are about to spend a significant amount of effort training and using one of these products you'll want to read through this and understand the tradeoffs.

The main take away here seems to be DNS8 offers better accuracy than Microsoft, but also requires a LOT more CPU. The author also points out that both products do not seem to perform any better/worse on dual core machines. This sort of suggests that if you've already bought Office and are running on a low end or older PC, you might want to just use Microsoft's engine. On the other hand if your PC has ample MIPs available and you have $$ burning holes in your pockets, go and buy a copy of DNS8.

The author's findings do gel with my own personal experiences in the recent past, when my right arm was in a cast for 6 weeks. I started out with the Microsoft dictation engine and after a couple of weeks I switched over to DNS. My main motivation for switching to DNS was not recognition accuracy, but the fact that they also offered a speech interface to the over all windows desktop, which let me use the computer with minimal need to try using the mouse with my left hand. Once I got DNS trained and running, I felt it offered more accurate dictation as well, though I didn't try to objectively quantify performance as this article does.

Another thing to consider is that with Windows Vista reportedly supporting speech as a seamless platform feature vs. an afterthought, its quite likely purchasing DNS at this point could be a waste of $$. I would expect the speech engine(s) in Vista as well as how they are integrated into the desktop and applications will be significantly better than what we've seen in the past.

Read the article.

1 Comments:

At 10:23 AM, Blogger The Team said...

Hi Skydog,

I ran across this post, and couldn't help but make a small comment.

The rumored accuracy benefits with Dragon are entirely urban mythology. I've been a SR user for almost 10 years, have been through the littany of recognition engines, from L&H to IBM to Dragon to a variety of 2nd tier apps.

MSR is entirely accurate, and is so from it's initial use. It's easier, more straightforward and the folks at Microsoft are working a lot harder than one might expect to make speech recognition truly integrated into Vista so that anyone can use it, without a noticable learning curve.

As it is now, the v6.1 recognizer that ships with Office 2003 is as incredibly accurate as anything I've ever used, and I expect 99% accuracy after three training sessions. (Try that with Dragon).

I think we're all in for a pleasant surprise and rewarding use of SR with Vista, no doubt.

Just my take.

 

Post a Comment

<< Home