News for hackers. Stuff that matters.
Re:40+ voice searches thrown at Google on Jelly Bean by switch007 on Tuesday July 03, 2012 @07:35AM (#4193584)
I assume that's over wifi? I'd like to see its performance over 3G.
Re:40+ voice searches thrown at Google on Jelly Bean by mise on Tuesday July 03, 2012 @08:11AM (#4193680)
On a related note, does the voice get intrepreted on the device, or on Google servers?
Re:40+ voice searches thrown at Google on Jelly Bean by Inversechi on Tuesday July 03, 2012 @08:24AM (#4193721)
From what I've read It's all done on the device.

"One of the biggest issues with Siri is that it requires access to Apple’s servers in order to work. In Jelly Bean, however, Google will provide full offline voice dictation to users. Granted, that’s not a full Siri competitor, but the fact that the search company has been able to take it offline in a mobile setting is very important."

http://www.eweek.com/c/a/Mobile-and-Wireless/Android-41-Jell...

Re:40+ voice searches thrown at Google on Jelly Bean by ConstantineXVI on Tuesday July 03, 2012 @08:20AM (#4193711)
As of JB, it can do both. Though I believe the offline mode is only used as a backup if the network's acting up.
Re:40+ voice searches thrown at Google on Jelly Bean by Tyrannosaurs on Tuesday July 03, 2012 @12:19PM (#4194740)
I wonder whether the offline performance is comparable?

If it was then surely you'd do all the voice parsing locally so I'm guessing that it's not. Unless anyone can think of another reason you'd push it through the servers?

Re:40+ voice searches thrown at Google on Jelly Bean by ConstantineXVI on Tuesday July 03, 2012 @01:27PM (#4195130)
Two factors:

- online should have more training data and can be improved much more easily. Don't see that advantage going away.

- power efficiency and/or speed. Sending 5s of audio across the net can be less strain on the device (esp. older ones) versus parsing the audio locally.

Re:40+ voice searches thrown at Google on Jelly Bean by apendleton on Tuesday July 03, 2012 @12:24PM (#4194771)
Pure speculation, here, but some of the transcription looked like it relied on pretty heavy statistical inference stuff (like knowing that "Worcester" comes before "Mass" but "Wooster" comes before "College," even though they're both pronounced the same). I would be really surprised if the client-side recognition was that smart, so I'd guess that they do it server-side if they can.