On Firefox 4 Day, Chrome 11 Hits Beta With The Ability To Talk To Your Computer
techcrunch.com
techcrunch.com
Does anyone know of Mozilla or Microsoft having any intention of switching to a more continuous release cycle?
(I believe Google uses http://code.google.com/p/omaha/ to push their updates out - quite a fascinating piece of software.)
I understand the security implications of A. However, B would be an acceptable alternative since the user initiates it. I'm imaging a vocal interface that requires minimal user keyboard interaction.
I found an attribute called "continue", but it doesn't seem to do anything special when added to the input element.
It's the way it should be, just imagine the vulnerabilities having js enabled microphones would have.
Does anyone actually use Voice Control on an iPhone, or any other speech recognition tech? I've never seen it used in real life except in IVR systems.
Back on topic, didn't Google roll something about Voice Command customization out a while ago? I'd been using it when I can so it would "learn", but I guess that's pointless if it doesn't. It does seem to have gotten better for me since the start, but I don't know if that's personalization or just Google improving it. I mostly use it for searching or dialing, so I can't speak for its accuracy at longer commands like texting, however.
I didn't know you could use it for alarms. That's brilliant and would be great for one-off alarms.
I also use it for short text messages if I don't have a second hand free or can type it out for whatever reason. It works reasonably well, but I've been letting it adapt to my voice pattern so maybe it works better for me than others.
1) is it me, or does it take two clicks to go from the plugin icon to actually accepting voice input?
2) android's voice search has both visual and audible cues to indicate to the user that it's actually picking up your speech, finished, and is now thinking about it. that'd be excellent.
2. This is a bug in Chrome due to the extension rendering in a popup bubble and the usual speech indicator also being in a popup bubble, but it won't render as only one popup bubble at a time can be displayed.
Is this still making requests to Google's servers to do the transcription? Personally I think I'll take the resource-hungry plugin over a web API.
Well, on a computer. On a phone, cloud voice input is fantastic.
The latter is how voice recognition works on Android, and why it only works when you have an active internet connection. It seems a little weird to me to build an html5 standard that requires server side computation. How is a non-profit open source browser going to fund the massive server load needed, not to mention the R&D needed to develop a voice-to-text translator? Google’s stuff is proprietary.
I have had a Nexus One for over a year now, and all the speech recognition does is annoy me if I accidentally hit the microphone icon and have to cancel it.
To be fair, I am not a native speaker of English, maybe it works better for native speakers.
I downloaded Firefox 4 and I liked it but after a couple of minutes I didn't resist not going back to Chrome.