Opie-reader Learns Speaking

[TimW]

I think it may be to do with the fact I'm building for Collie, or to do with it picking up some of my local configuration because it seems to be confused about whether or not it is building for OSS or ALSA. It defines something which is clearly supposed to be for an ALSA build but fails in building the OSS interface. I had the same thing when I compiled it by hand and had to fiddle with some #defines in the header files which ./configure hadn't set right.

[TimW]

I've tried passing a sentence at a time to flite and it doesn't work very well. If you listen to the way that flite says a paragraph, the first few words have a different emphasis to give an audible cue that there is a new paragraph. Having this cue applied to every sentence sounds terrible.

BTW, I managed to compile flite for OZ by manually editing the flite-1.2-release/config/config file to replace ALSA by LINUX (which enables OSS rather than ALSA). There is a setting in the bb file which tells config to do this but it doesn't work properly for me. I can now prepare an ipk for opie which will use either call the library direct, or exec flite to do the dirty work (ie the same as people have been testing on the SharpROM). There is a feature freeze in the opie CVS ATM but I can send an ipk to anyone who wants to try it. Unfortunately the flite ipks are too big for me to do this so you need to be able to build them yourselves. Also, there is some doubt (in my mind) about how to invoke flite on the ipaq vs the zaurus under OZ so initially I'll probably only send out one of each, so let me know which device you are using. Once it is confirmed as working I'll send out some more.

[phunkhy]

I would like to port Opie-Reader 0.7i to pdaXrom to benefit from the flite support. Who can give me any hint how to do that. I would like to have a tarball which contents can compile. I
simply don't find the sources in the opie CVS.

A nice flite ipk source I found:
http://www.unpleasant.net/chris/zaurus/pda....2_armv5tel.ipk
(if you have troubles with flite, like 'can't open /dev/dsp' then just do 'killall esd')

cheers

[TimW]

I would like to port Opie-Reader 0.7i to pdaXrom to benefit from the flite support. Who can give me any hint how to do that. I would like to have a tarball which contents can compile. I
simply don't find the sources in the opie CVS.

A nice flite ipk source I found:
http://www.unpleasant.net/chris/zaurus/pda....2_armv5tel.ipk
(if you have troubles with flite, like 'can't open /dev/dsp' then just do 'killall esd')

cheers
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

[a href=\"http://handhelds.org/cgi-bin/cvsweb.cgi/opie/noncore/apps/opie-reader/]The opie CVS source is here.[/url] To compile for X11 make sure that USEQPE is undefined and put all the shared stuff (like icons etc) into a directory referenced by the environment variable READERDIR (look at the source - search for READERDIR - to see the sub-directories used).

[ken]

TimW:

The flite homepage is here:

http://www.speech.cs.cmu.edu/flite/

It includes the source, etc

If it's festival you're interested in, it's here:

http://fife.speech.cs.cmu.edu/festival/

[malik]

for those who didnt lost their interest in tts systems on the zaurus.
i was suprised that the below setup worked

1) an older arm port of qemu + linux binary of the german tts system txt2pho
2) an arm port of mbrola
3) mplayer to play the generated wav files

its hard to compare the results for german and english speech, but i would
say that the mbrola system is better than flite but not as good as
the ibm plugin for opera.

for a text file consisting of one paragraph with around 4 lines (a 80)
step 1) took around 40 sec and step 2) around 12 sec. the generated wav file
was around 16 sec.

conclusion: the above setup doesnt seem to be really usable on the zaurus.

malik