- Status Unconfirmed
- Percent Complete
- Task Type Patches
- Category Infrastructure → Build environment
-
Assigned To
rasher - Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#8589 - Allow to choose Loquendo and ViaVoice TTS
It would be useful to change the configure and voice.pl files in order to allow the user to choose also the Loquendo and ViaVoice TTS
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Loquendo (http://www.loquendo.com) and ViaVoice (http://www.wizzardsoftware.com/) are two text-to-speech engines. They have a great quality, but, unfortunatily, they are not GPL. In order to use them to create sounds (for example the menu messages for blind people) you need the SDK and need an special licence.
'loquendo-text2file' and 'ttsynth_say' commands are referenced in the configure patch. They are to commands that send text to a sound file. Anyone can get ttsynth_say from the ViaVoice SDK. Loquendo-text2file it's a little application that i have done. If somebody need it, i can send him the source file, but rememeber that you need the Loquendo SDK in order to compile and use it.
Another important issue is remember that ViaVoice doesn't work with utf-8. So, you must save the lang file in a compatible format with ViaVoice (ie 8859)
Hi Chelo,
If you're using Windows, I believe that ViaVoice uses SAPI underneath their own front end, so those should work with the current code.
e.g. http://www.wizzardsoftware.com/att_desktop.php
This looks pretty reasonable, although I think we should add charset conversion to voice.pl and introduce a VOICE_CHARSET define or something like that, which will be ignored if empty, but causes voice.pl to convert to the specified charset. I think sapi_voice.vbs might already be doing charset conversion, but I'm not sure.
With Jens Arnold's change yesterday, this should now be possible. I'll look into finally committing this one later today.