Flite TTS: Difference between revisions
(Created page with "{{Stub}} for very long, FlightGear has been able to let an external festival instance speak text written to /sim/sound/voices/pilot etc. I have just pushed some code to let t...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
{{See also|Howto:Customizing Flite TTS Voices}} | |||
for very long, FlightGear has been able to let an external festival instance speak text written to /sim/sound/voices/pilot etc. I have just pushed some code to let the already working internal TTS synthesier (flite+hts_engine) create the audio for you. Those of you who already have -DENABLE_FLITE set while running cmake will only have to set the property --prop:bool:/sim/sound/voices/enabled=true on startup. The old voice manager will try to connect to the external festival server and will eventually fail if you havn't started one. In that case, fg will fall back to the internal flite synthesizer. The voices are configured in preferences.xml, line 316ff. You can set <festival> to false to avoid the connect to the festival server (and the error messages on the console).<ref>{{cite web | for very long, FlightGear has been able to let an external festival instance speak text written to /sim/sound/voices/pilot etc. I have just pushed some code to let the already working internal TTS synthesier (flite+hts_engine) create the audio for you. Those of you who already have -DENABLE_FLITE set while running cmake will only have to set the property --prop:bool:/sim/sound/voices/enabled=true on startup. The old voice manager will try to connect to the external festival server and will eventually fail if you havn't started one. In that case, fg will fall back to the internal flite synthesizer. The voices are configured in preferences.xml, line 316ff. You can set <festival> to false to avoid the connect to the festival server (and the error messages on the console).<ref>{{cite web | ||
| Line 9: | Line 12: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
== Related == | |||
{{Appendix}} | |||
Latest revision as of 19:29, 31 October 2017
| This article is a stub. You can help the wiki by expanding it. |
for very long, FlightGear has been able to let an external festival instance speak text written to /sim/sound/voices/pilot etc. I have just pushed some code to let the already working internal TTS synthesier (flite+hts_engine) create the audio for you. Those of you who already have -DENABLE_FLITE set while running cmake will only have to set the property --prop:bool:/sim/sound/voices/enabled=true on startup. The old voice manager will try to connect to the external festival server and will eventually fail if you havn't started one. In that case, fg will fall back to the internal flite synthesizer. The voices are configured in preferences.xml, line 316ff. You can set <festival> to false to avoid the connect to the festival server (and the error messages on the console).[1]
Related
References
|