01-30-2017, 08:36 AM | #31 |
Evangelist
Posts: 416
Karma: 765432
Join Date: Apr 2016
Location: Italy
Device: Kindle PW3 5.8.5.0.1
|
|
01-30-2017, 08:49 AM | #32 |
curly᷂͓̫̙᷊̥̮̾ͯͤͭͬͦͨ ʎʌɹnɔ
Posts: 3,008
Karma: 50506927
Join Date: Dec 2010
Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ą₆₀"
Device: K3₃.₄.₃ PW3&4₅.₁₃.₃
|
|
Advert | |
|
01-30-2017, 09:27 AM | #33 |
Addict
Posts: 248
Karma: 892441
Join Date: Jul 2010
Device: K2i
|
@encol: No criticism against this project or you personally - between "what Amazon has chosen to provide on the device" and there being no TTS support at all - its still great that it exists.
Also - many of the shortcomings are more structural issues than your fault. - Open source TTS engines not being up to par with commercial solutions > the "big five" tech giants use big data and machine learning to "understand and improve" their TTS engines - you can't do that with "five people in a garage" any longer... (I think its worthy to think about it from that perspective as well, as "voice assistents" are currently held up as "the modern user interface" - so when user expectations (not mine) go in one direction, and open source projects cant - there is a structural reason for it). - Amazons "dongle" implementation is limited, restrictive, follows their own user experience deliberations and probably isn't "standards oriented", so when a certain popup crashes a process that isn't supposed to run in the first place - thats hardly your fault either. - Leaving the dongle in while the device auto reboots causing a bootloop - is an unforeseen circumstance (in conjunction with the mobileread recovery scripts) and an issue thats probably impossible to solve, because you are weighing the need for a hack to allow people with bricked devices to enter recovery in a way thats low level enough that a screen input is not needed. - And a part of people that would usually wan't to use a TTS engine can't be expected to be able to troubleshoot all this, because they might be visually impaired. - I'm interested in checking out new TTS implementations, when they come along - but mainly from that perspective (how "usable are they" for me and other folks). So thats basically me saying - valiant effort, good job - great for even venturing into this field and creating something that works - but there are limits, that others should know exist - in this implementation, and in others on this device. IVONA on Android is also free (but you have to jump through more and more hoops to get it set up (because of Amazons decision to get voices depublished - because of FBReader resorting to a "more simple UI experience", that doesn't allow you to change the document language on the fly - in newer versions (which is important for TTS purposes) ), and might be a better solution if you are really looking for one, because you need it, rather than, because its cool to play with one. Its cool to play with KSpeak as well. Last edited by notimp; 01-30-2017 at 09:32 AM. |
03-05-2017, 12:30 PM | #34 |
curly᷂͓̫̙᷊̥̮̾ͯͤͭͬͦͨ ʎʌɹnɔ
Posts: 3,008
Karma: 50506927
Join Date: Dec 2010
Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ą₆₀"
Device: K3₃.₄.₃ PW3&4₅.₁₃.₃
|
-m
Reading eSpeak documentation, I found the -m switch which causes eSpeak to interpret some SSML tags when reading an htlm file.
I was interested in the xml:lang tag to have the speech synthetizer switching languages according to the markup. Perhaps integrating eSpeak to Koreader that way could provide multilingual TTS with minimum effort. So, with the help of Omniglot, I created a book to speak "Welcome" in all of the languages supported by eSpeak: "welcome.html" source: Spoiler:
MOBI Book: Spoiler:
When displayed it shows: Spoiler:
When spoken via "espeak -m -f welcome.html -w welcome.wav" it sounds: Spoiler:
...Hoping you can have some fun too. Last edited by PoP; 03-05-2017 at 01:58 PM. Reason: cross linking to KOreader forum |
03-05-2017, 12:54 PM | #35 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Now if you could find a tag to change the voice, the Klingon might sound better spoken in a whiskey-bass voice.
|
Advert | |
|
03-05-2017, 02:06 PM | #36 | |
Evangelist
Posts: 416
Karma: 765432
Join Date: Apr 2016
Location: Italy
Device: Kindle PW3 5.8.5.0.1
|
Quote:
|
|
03-05-2017, 02:22 PM | #37 | |
curly᷂͓̫̙᷊̥̮̾ͯͤͭͬͦͨ ʎʌɹnɔ
Posts: 3,008
Karma: 50506927
Join Date: Dec 2010
Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ą₆₀"
Device: K3₃.₄.₃ PW3&4₅.₁₃.₃
|
Quote:
Well, there is an SSML <voice gender="male" name="Worf"> tag but eSpeak doesn't support it. espeak -v russian+croak is the closest that I could find Code:
espeak [options] ["<words>"]
-f <text file> Text file to speak
--stdin Read text input from stdin instead of a file
If neither -f nor --stdin, then <words> are spoken, or if none then text
is spoken from stdin, each line separately.
-a <integer>
Amplitude, 0 to 200, default is 100
-g <integer>
Word gap. Pause between words, units of 10mS at the default speed
-k <integer>
Indicate capital letters with: 1=sound, 2=the word "capitals",
higher values indicate a pitch increase (try -k20).
-l <integer>
Line length. If not zero (which is the default), consider
lines less than this length as end-of-clause
-p <integer>
Pitch adjustment, 0 to 99, default is 50
-s <integer>
Speed in words per minute, 80 to 450, default is 175
-v <voice name>
Use voice file of this name from espeak-data/voices
-w <wave file name>
Write speech to this WAV file, rather than speaking it directly
-b Input text encoding, 1=UTF8, 2=8 bit, 4=16 bit
-m Interpret SSML markup, and ignore other < > tags
-q Quiet, don't produce any speech (may be useful with -x)
-x Write phoneme mnemonics to stdout
-X Write phonemes mnemonics and translation trace to stdout
-z No final sentence pause at the end of the text
--compile=<voice name>
Compile pronunciation rules and dictionary from the current
directory. <voice name> specifies the language
--ipa Write phonemes to stdout using International Phonetic Alphabet
--ipa=1 Use ties, --ipa=2 Use ZWJ, --ipa=3 Separate with _
--path="<path>"
Specifies the directory containing the espeak-data directory
--pho Write mbrola phoneme data (.pho) to stdout or to the file in --phonout
--phonout="<filename>"
Write phoneme output from -x -X --ipa and --pho to this file
--punct="<characters>"
Speak the names of punctuation characters during speaking. If
=<characters> is omitted, all punctuation is spoken.
--split="<minutes>"
Starts a new WAV file every <minutes>. Used with -w
--stdout Write speech output to stdout
--version Shows version number and date, and location of espeak-data
--voices=<language>
List the available voices for the specified language.
If <language> is omitted, then list all voices.
Code:
To make alternative voices for a language, you can make additional voice files in espeak-data/voices which contains commands to change various voice and pronunciation attributes. See voices.html.
Alternatively there are some preset voice variants which can be applied to any of the language voices, by appending + and a variant name. Their effects are defined by files in espeak-data/voices/!v.
The variants are +m1 +m2 +m3 +m4 +m5 +m6 +m7 for male voices, +f1 +f2 +f3 +f4 +f5 for female voices, and +croak +whisper for other effects.
Last edited by PoP; 03-05-2017 at 02:25 PM. |
|
Tags |
espeak, speech, synthesizer, text to speak, tts |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Request] Porting choose your own adventure games to kindle | #gabriel | Kindle Developer's Corner | 3 | 05-03-2016 02:11 PM |
Porting Anki to Kindle Touch - please comment | koziej | Kindle Developer's Corner | 17 | 01-10-2014 07:39 AM |
Porting Kindle Paperwhite OS to Kindle Keyboard | mrzerga | Kindle Developer's Corner | 5 | 06-30-2013 11:44 AM |
GUI Launcher greyed out when TTS is on and does not come back when TTS is off | jmseight | Kindle Developer's Corner | 4 | 07-28-2012 03:48 AM |
Android porting on my kindle touch? | acajac | Kindle Developer's Corner | 1 | 04-12-2012 09:42 AM |