When Windows 7 was release it has voice recognition in it. My initial thoughts on the voice recognition was that it was good, but the user interface was for crap. Now, when I did that review, it was on a beta version of Windows 7; it was a release candidate— I recall thinking, this is so bad, they’re going to have to update this to make it usable… but when Windows 7 was released officially, Microsoft had done absolutely nothing to it to improve the GUI.
I have always said that the voice recognition of Microsoft was good, but the GUI is the biggest problem with it. It’s like trying climb a range of boulders with a skateboard; it’s clumsy at best.
So, when I downloaded the RC version of Windows 8, one of the first things I wanted to see was the GUI of the voice recognition. And what a disappointment it is. Microsoft has done NOTHING to it to make it more user friendly.
But I need to explain…
Microsoft‘s voice recognition isn’t compatible in all applications, but as long as you are using their voice recognition with their applications, yeah, you’re okay, but outside that— your screwed. The caveat to that is if the application is aware and it’s using the voice recognition schema that Microsoft requires.
And while I understand the concept that while voice recognition should or could be something where an user can completely control their PC with it; that’s not my concept. I don’t want my PC to do everything via voice— and truthfully, it’s just not possible. So I’d like to focus on the voice recognition and usability of the function in my applications, the ones I’d like to use it in; and this is where Microsoft continues to fail. I need it to work in everything, not just Microsoft products and not just the applications with this little piece in it.
The Microsoft boys have this ability to make it work like that, but they chose not to; they say no, make it work the way I’d like it to work— that model doesn’t work, and it’s not going to work for a long time. And it’s funny, because there’s some people that are going to argue that it’s not Microsoft‘s fault that their voice recognition doesn’t work in the specific applications; it’s the authors fault for not putting this piece in their software.
Bah, crap and balderdash! I call BS on that one because other voice recognition applications like Nuance Dragon NaturallySpeaking does this without blinking. And I only mention Dragon NaturallySpeaking because they’ve got the right idea on user interfaces for voice recognition.
Voice recognition should work, when you want it to work— that’s it… that’s all there is to it. Where Microsoft if fighting the rest of the world on how they think voice recognition should work and how it should be integrated with the operating system; the true answer is, it should work everywhere.
With the distribution of Windows 8 RC; two things— I’ve got a strong aversion towards the Metro GUI; I believe it’s obtuse beyond anything Microsoft could’ve offered. I’m sure it’s okay for a tablet PC, but not for the desktop. The second, the GUI for the voice recognition on the RC version, it should have offered a direct link to the Microsoft voice recognition data center; to use the same voice recognition as the Windows Mobile 7 phones [if they wanted to standardize across the board].
Again, the recognition of the Microsoft engine has never been in question; it’s a pretty good engine— not as good as Dragon NaturallySpeaking, but good. But to strike a contrast, Dragon NaturallySpeaking is a newly paved road for voice recognition while Microsoft is still traveling the ‘Oregon Trail’ with theirs.
Larry Henry Jr.