Melchior FRANZ

> * Erik Hofman -- Monday 06 February 2006 13:35:
> > The original code was written for/by John Wojnaroski so you might be
> > asking this a the wrong time. Personally I feel it would be a nice
> addition.
> 
> OK, then I'll continue to work on it (as I've done since yesterday).
> I'll make it so that the preferences file decides how many voices there
> are. For each /sim/sound/voice[*]/{text,volume,pitch,speed} there will
> a channel be opened to festival and maintained by the subsystem.
> We could then add aliases for copilot, instructor, etc. Would be nice
> if the b29 copilot reported "gear down" etc., or the bo105 copilot
> gave some navigation hints ("I think we are too far already". :-)
> 
> BTW: the whole thing won't depend on festival. One can easily write
> a few lines of perl to simulate a festival server and use the text
> for different purposes. For example, to let a human or a trained
> monkey read it. And all others can map the text to the screen.log.
> 
> I'll start to commit once I got permission. (The old ATC voice
> thing will lose the /sim/sound/voice property first, which is used
> as an "enabled" flag, and finally die.)
> 

I'm working at getting Festival to compile under Cygwin. They claim that it
does, and, while it's very long-winded, it's looking good so far ...

Vivian



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to