I'm assuming we can swap out the backend? I ask because with Tizen IVI we use festival and sphinx (both open source speech rec & tts engines) as well as a commercial offering from Nuance to demo speech rec and tts in our platform vs using a cloud service like Google (not to mention I've never looked at the terms and conditions (license) that goes with using the Google API but I'm sure there's one if you use it commercially in a product).
Thanks, Adam From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Hu, Ningxin Sent: Monday, December 23, 2013 12:57 AM To: Gao, Chun; crosswalk-dev@lists.crosswalk-project.org Subject: Re: [Crosswalk-dev] Intent to Implement: Allow speech recognition API using the default microphone One more comment to Speech Recognition Backend: Google speech recognition service backend implementation (needing API key) only applies to desktop version (Windows, Linux and Mac) as [1]. However Android implementation [2] depends on Android Speech API [3]. It means if the device supports speech recognition functionality, Crosswalk will work fine. Thanks, -ningxin [1]: https://github.com/crosswalk-project/chromium-crosswalk/blob/master/content/browser/speech/google_streaming_remote_engine.h [2]: https://github.com/crosswalk-project/chromium-crosswalk/blob/master/content/browser/speech/speech_recognizer_impl_android.h [3]: http://developer.android.com/reference/android/speech/package-summary.html From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Hu, Ningxin Sent: Monday, December 23, 2013 10:42 AM To: Gao, Chun; crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: Re: [Crosswalk-dev] Intent to Implement: Allow speech recognition API using the default microphone LGTM. Thanks. Additional information: The W3C Speech API spec (including speech recognition and synthesis): https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html To use Google Speech Recognition Service as backend (current implementation in content layer), need to provide API key as documented at: http://www.chromium.org/developers/how-tos/api-keys -ningxin From: Gao, Chun Sent: Monday, December 23, 2013 10:16 AM To: crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Cc: Hu, Ningxin Subject: Intent to Implement: Allow speech recognition API using the default microphone Summary: This implementation makes Crosswalk allow speech recognition API using the default microphone automatically. Speech recognition API has been implemented at content layer by Chromium upstream, but it could not work on Crosswalk, that's because the class which accept/reject using microphone has not been implemented for Crosswalk yet. Affected component: W3C API Related feature: XWALK-728< https://crosswalk-project.org/jira/browse/XWALK-728> Target Release: Crosswalk 4 Implementation details: Implement the class XWalkSpeechRecognitionManagerDelegate for Crosswalk, it's derives from the class SpeechRecognitionManagerDelegate which defined in content/public/browser/speech_recognition_manager_delegate.h. And allow the Speech Recognition API to use the default microphone in corresponding member function of the class. Thanks, Gao Chun
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
