TTS voices

Started by Menion, July 07, 2013, 14:44:19

0 Members and 1 Guest are viewing this topic.

Menion

Ah I'm checking what I did in code and indeed, all defined containers needs to have at least one item, sorry. So for numbers, I'll improve this to next version.
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download
  •  

Menion

Answer to problem mentioned by ta-ka here: http://forum.locusmap.eu/index.php?topic=4467.msg35838#msg35838 - missing notification for 1 hour, 0 minutes

Issue was in TTS file, where were no configuration for '0' minutes. Please check modified EN or CZ file what I mean (extra '0' parameter in TIMES_T1 container.

I should today publish one quick special version right here on forum, so if you modify these TTS files, I'll include them into version. Same with Crowdin, thanks!
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download
  •  

ta-ka

#92
@menion thanks for the fix of 0 minutes issue.

updated ja.tts : "numbers_N1" is empty now.
fixed en.tts : 's' after mile was missing at "%N1 mile per hour, 2, Inf"

EDIT:
crowdin done. (except Locus GIS, sorry for that)
  •  

gynta

#93
damn
that means, my file also need a fix...
brb :)

edit
done (tts and crowdin)
thx ta-ka!

Menion

- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download
  •  

ta-ka

The warning popup message reported in post #89 still appears in version 3.7.1.4.
Haven't it fixed yet?  Or, is there anything wrong in ja.tts at google drive?
Could you please have a check?


  •  

ta-ka

About Training, I've noticed that Locus pronounces annoying 'comma' between variables if Japanese voice is selected. Could you please improve this?
  •  

balloni55

QuoteI've noticed that Locus pronounces annoying 'comma' between variables
i noticed the same if i use Samsung TTS :-[, if i use google TTS it work for me :)
Locus Map Classic 3.62.1 AFA
Locus Map 4.11.1.1 Gold AFA
LMP User ID 7ee4dad32
LM4 User ID e06d572d4
  •  

ta-ka

Quote from: menion on April 07, 2015, 13:30:55
@ta-ka, problem with comma should be a problem. It's weird that TTS reads it, weird. Google TTS or Czech Ivona TTS reads it correctly - just as a small break. Hmm ...

Is the adding 'comma' hard coded in the program source? If so, how about to take it out to ??.tts/crowdin text as a parameter.

"short_pause": ","
"short_pause" can be 'comma' or 'white space' or any other appropriate character depending on Language and TTS engine.

Btw, reading balloni and your post, I confirmed Japanese Google TTS doesn't speak comma, too.  However KDDI N2TTS speaks comma...
  •  

gynta

#99
Quote from: menion on April 07, 2015, 20:58:01
@ta-ka: adding "separator" to tts is not something I want. Main reason why TTS file was created, is to be able to define some special texts that will TTS engine read correctly. Because some TTS engines reads this correctly, some not, I'll try to think and find some general solution.
Seems it is a long known global problem: https://code.google.com/p/ankidroid/issues/detail?id=907 and some other pages
Hmm as I think about it, I'll try to next version add a dot instead of comma.

Quote from: ta-ka on April 07, 2015, 18:34:27
However KDDI N2TTS speaks comma...
Think "KDDI N2TTS" only known in asia? Isn't it?
So can't check this TTS-engine.

After some tests with "IVONA" "Samsung" "SVOX" and "Google":

SamsungTT german "Hallo , Peter" read a "comma"
SamsungTT german "Hallo, Peter" ignores the "comma"
SamsungTT english "Hello , Peter" ignores the "comma"
SamsungTT english "Hello, Peter" ignores the "comma"

Only the combination "Hello-space-comma-space-Peter" with german Samsung brings a problem.
All other TTS-engines and combinations ignores the "comma"

@Menion is there any "%X-space-comma-space-word" combination inside Locus TTS?
should be "%X-coma-space-word".

ta-ka

#100
I post here about the discussion of comma and tts.

Quote from: menion on April 07, 2015, 20:58:01I'll try to think and find some general solution.
Hmm as I think about it, I'll try to next version add a dot instead of comma.
I'm afraid but "dot" won't be a general solution. I confirmed it is literally pronounced by N2TTS as shown in a video below.
https://www.dropbox.com/s/a99451wtokegpz0/20150408_tts_comma_period.mp4?dl=0

Quote from: menion on April 07, 2015, 20:58:01Main reason why TTS file was created, is to be able to define some special texts that will TTS engine read correctly.
Because some TTS engines reads this correctly, some not,
To read, or not to read, that is the question. 8)
Since "," and "." are not punctuations but special symbols in Japanese, it makes a sense that N2TTS pronounce it literally. On the other hand, it is known that "," and "." are punctuations in a lot of languages in the world. So, it also makes a sense that Japanese Google TTS doesn't pronounce it but put a pause for convenience. Which is correct?  It is difficult to say.

Japanese punctuations are "、" and "。" which correspond "," and "." respectively. When we read Japanese text, we put a short pause at "、" and a longer pause at "。". (We learn it at primary school ;)) Please note that both Google TTS and KDDI N2TTS put a pause on "、" and "。" and don't pronounce them. It is correct behaviour.

Quote from: menion on April 07, 2015, 20:58:01adding "separator" to tts is not something I want.
Then how about to introduce punctuations entry in tts file and put it between variables? (period is for further compatibility.)
"comma": ","
"period": "."
In fact, I usually translate "," to "、" in ja.tts and crowdin.

Quote from: gynta on April 07, 2015, 23:06:25
Think "KDDI N2TTS" only known in asia? Isn't it?
So can't check this TTS-engine.
@gynta Thanks for trying to test even Japanese TTS :). I think it is Japanese language specific TTS. Is it possible to open google play with this url?
https://play.google.com/store/apps/details?id=jp.kddilabs.n2tts
If it's not successful, you may try apk downloader.
  •  

Menion

Very nice explanation, thank you!

Then check TTS files, added:

        "special_comma": ", ",
        "special_period": ". "

hope it helps
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download
  •  

ta-ka

#102
Thank you for quick answer and decision as always!

And, please fix empty "numbers_N1" issue (post #89) as well. ;)

EDIT:
updated ja.tts
  •  

ta-ka

I've confirmed that the warning message "incorrectly initialized action %N1" still appears in 3.7.1.6 and in this case the voice system of Locus falls back to crowdin text base. I'm sure that empty "numbers_N1" in tts file cause the issue and it's possible to reproduce it by using attached en.tts.

Now, I would like to ask again whether empty "numbers_N1" is a valid format or not. If valid, please fix the issue to properly load tts file. (for both tts file integrated in Locus and placed at data/tts folder.) If invalid, I'll re-modify ja.tts at google drive with non-empty "numbers_N1".

  •  

Menion

Ah I had a check for valid amount of items in number_X folder on two places, not just on one. Sorry, fixed, thanks.
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download
  •