Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.
Using Bluetooth Headset for Speech Recognition with Windows Mobile: Or Not
Posted on 4-Feb-2006 08:57 by M Freitas. | Tags Filed under: Blog.



You tried some of the registry hacks floating around to use Bluetooth headsets with Pocket PCs and it didn't work well? Over at the Windows Mobile Team Blog, Mike Calligaro explains why Voice Command doesn't work over Bluetooth (BTh) headsets:

"The short story is that the current version of Voice Command relies on microphones that sample at 16 kHz, but BTh headsets only do 8kHz.".

But the real explanation comes down in the blog post. The whole thing comes down to assumptions made by developers when planning software that will take a long time to be written. Decisions have to be made, and sometimes they branch our to the wrong path.

Apparently "the Voice Command team. [They] set out to make the best voice recognition software they could. And, their original analysis said that they could do much better recognition if they designed their database around the assumption that audio would be sampled at 16 kHz instead of 8.

At this point in history, BTh's future was murky. Although it had strong backers, it wasn't doing very well. There were people who promised that it would align the planets, create spiritual harmony, and bring about world peace. There were others who felt that it was a flash in the pan that wouldn't go anywhere. And there were a million more opinions that covered pretty much everything in between. Publicly, Microsoft was pretty cold on BTh at the start, though a number of people in the company were strong proponents.

So the Voice Command team had a tough decision to make. Should they assume BTh would continue to flounder and write a better recognizer that relied on built in microphones (which can sample at 16 kHz)? Or should they assume BTh would take off and everyone would want to do Voice Command over BTh headsets?

They decided that BTh would succeed, but that it was going to take a while to do it. So they chose to go with the better recognizer first. Then BTh took off more quickly than they expected
.

There are much more on the post, worth reading it. It does sound as a mea culpa, which is good - but there is no guarantees this kind of decision or assumption won't happen in the future. But every long project needs decisions taken sooner than later so it's understandable.







comments powered by Disqus




Trending now »

Hot discussions in our forums right now:

Gareth Morgan is a genius
Created by Satch, last reply by dejadeadnz on 8-Dec-2016 23:08 (75 replies)
Pages... 3 4 5


NZ Prime Minister John Key Resigns
Created by ajobbins, last reply by elpenguino on 8-Dec-2016 23:43 (214 replies)
Pages... 13 14 15


The President Of The USA - Who do you think?
Created by TimA, last reply by DarthKermit on 8-Dec-2016 16:22 (909 replies)
Pages... 59 60 61


Dishwasher not Working Properly
Created by tdgeek, last reply by mdav056 on 5-Dec-2016 20:18 (28 replies)
Pages... 2


Wilson's Car Park - When Free is not free
Created by nzkiwiman, last reply by debo on 8-Dec-2016 23:01 (48 replies)
Pages... 2 3 4


Spark wireless broadband and home /lan access: CGNAT limitations
Created by yokkem, last reply by BarTender on 8-Dec-2016 15:57 (19 replies)
Pages... 2


Spark not planning to deploy native IPv6 at all. Ever.
Created by Erayd, last reply by sbiddle on 7-Dec-2016 20:57 (19 replies)
Pages... 2


JB Hifi Cost & GST Sale - 7th Dec
Created by Finch, last reply by Kopkiwi on 7-Dec-2016 15:11 (16 replies)
Pages... 2