Speech Recognition and Text-to-Speech in Android

[Yevgen Borodin]

Hi, all!

We want to make a speech enabled Web Browser.
There's only one problem Android does not have either yet.
We've been fighting with FreeTTS Java speech synthesizer.
Apparently, it's using a number of packages not available in Android's
Java.
The absence of SR and TTS really kills a number of interesting
projects.
And the minimum that we need is a working TTS. Any ideas?
If we could at least get a clue that there will be some kind of TTS
available before the submission deadline, that would give us some
hope.

Thank you,
Eugene.

[sour...@free.fr]

Hi,
it is true that these functionalities miss to carry out the applications but it
will be probably implemented in Android. Nuance (Dragon Speaking editor) is in
the Open Handset Alliance.
http://www.nuance.com/news/pressreleases/2007/20071105_oha.asp
For the moment to make the tests, it would be interesting to do communicate
Android with FreeTTS (which is installed on the PC).
If you have any ideas ...
Phix

Selon Yevgen Borodin <bor...@gmail.com>:

[izamryan]

I was looking at the class index here:

http://code.google.com/android/reference/classes.html

and after searching for "speech" and "recognition" I came across this:

http://code.google.com/android/reference/android/speech/recognition/Recognizer.html

[Yevgen Borodin]

I saw SR APIs. But people say that functionality is disabled.
And I am a lot more concerned about the TTS than about SR.
I suppose, the current solution is to connect to an external TTS and
SR.
But since we are working with an emulator anyway I hope that's ok...

to GOOGLE REPRESENTATIVES:

Please confirm that using external TTS and SR installed on the desktop
would be a legitimate entry for the Android Challenge.

Thank you,
Eugene.

On Dec 23, 7:53 pm, izamryan <izamr...@gmail.com> wrote:
> I was looking at the class index here:
>
> http://code.google.com/android/reference/classes.html
>
> and after searching for "speech" and "recognition" I came across this:
>

> http://code.google.com/android/reference/android/speech/recognition/R...

[Nanard]

I also need TTS for my project.

I'm doing everything I can (access to data , UI) right now.
I just update a TextView and do a Thread.sleep() to simulate a
speech.

I'll have to change only this few code when (if?) Google releases a
TTS emulator somedays...

If this never happend, all my project will be useless !

I hope someone from another company will notice/like my project and
contact me then !

By the way, do you think we can make money with our projects even if
we are not choosen by Google to be the only 10 wining projects ?
Maybe some software editor working on PDA, embeded system, phones,...
could be interested by all of ideas ???

ANDROID TEAM : Will our projects be available to everyone , on Android
web site upon submission ? At least all project descriptions/scrren
shot. So we can see what the other have done :-) ?

[Peli]

Hi Eugene and all people above!

I'm also interested in speech recognition and text-to-speech in
Android!
I had in mind a general approach that would allow to exchange text
input and output between arbitrary Android applications, so that one
could control any Android application by text input, or have any view
read by text-to-speech.

If you want, join us to join our efforts at OpenIntents:
http://code.google.com/p/openintents/
(some ideas regarding this and further links are presented on the idea
page: http://code.google.com/p/openintents/wiki/Ideas )

Our idea is to join efforts on common functionality (like SR and TTS),
but everybody should still pursue their secret ideas for the
competition, so that you can win either with your project or with our
common project.

If you (Eugene, Phix, izamryan, Nanard, ...) are interested in
joining, just let me know, and we'll see how we can best coordinate
our common efforts!

Hope to see you soon,
Peli

[Peli]

Hi Eugene,

I'm not from Google, but I think if we use the general framework of
Intents and IntentReceivers to connect your application to an Android
service that connects to an external TTS, this should give full credit
to your application. Plus, the Android service could be easily
exchanged by a Morse flasher, a Braille reader, or a translator, ...
and your application could work without modification, once a native
TTS or SR is available on Android (which may or may not have been
programmed in Java).

If you are interested in such a possibility, have a look at my other
post below.

Peli
http://code.google.com/p/openintents/