Likes: 
Reply With QuoteHi,I have the vocalizer tts version 1.0.2.3t and Android 8.0.
Is there a new and better version than that and which languages supports?
Thanks.
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 261 to 266 of 266
Thread: TTS Nextgen discussion
-
17th September 2019, 03:04 PM #261Junior Member
- Join Date
- Dec 2009
- Location
- Europe
- Posts
- 6
- Rep Power
- 0
Hello, I had the same problem. With Kasandra TTS Voice file it is OK.
Originally Posted by vLeeuwen
File in content/voices/
Thanks Golom, Originally Posted by Golom
You are right, deleting Phoneme solved that problem for me.
Last edited by Pukker; 19th September 2019 at 09:59 AM.
-
20th October 2019, 08:25 PM #262Member
- Join Date
- Sep 2013
- Location
- globe
- Age
- 42
- Posts
- 10
- Rep Power
- 0
-
21st October 2019, 01:15 PM #263Master
- Join Date
- Mar 2013
- Location
- France
- Posts
- 176
- Rep Power
- 64
-
22nd October 2019, 12:40 AM #264Junior Member
- Join Date
- Mar 2017
- Location
- Canada
- Posts
- 3
- Rep Power
- 0
Anybody solved this problem ? I am using NextGen with the unisex TTS (english), Google engine. I do not have phonemes (Android). Most street names are OK but on highways (Canada) I can also hear "equal, backslash" followed by correct highway number, for highways which have a number not a name (most highways around here). Any modified voice file which fixes this ? I searched but did not find any. Thanks. Originally Posted by Golom
PS - For example one street : Dundas St W 5 is pronounced "Highway 5 slash equal one backslash". This is consistent for any highway which has a number.
There is any way to eliminate that slash equal part ?
There is any way to read the highway name , not number if it has both like in this case ? I vaguely remember some hack long before about this on Primo.... Not sure it is possible on NG.
I'm using latest Canada maps, tried both Here and TA, is the same, and the standard unisex English US voice, with standard Google TTS vocalizer .
I did more investigation about this. First, because I am in Canada but the language is Eng US it consider me as being in a foreign country so the settings for sound are the one for foreign country not local (no idea how can I set that my locale is Canada not US ?).
Changing the sound settings for "Say Road Names in Foreign Language area" from numbers only to "Numbers and Names" make the software now to only say the direction when reaching the road which has both name and number ( I tried manoevures only also an it's the same). However other highways which have ONLY a number like 401 or any highway exit which is a number have the same problem so the software says the number followed by slash equal one backslash. So the problem is still there.
Any help is appreciated.Last edited by adit; 22nd October 2019 at 06:22 PM.
-
25th October 2019, 11:59 PM #265Senior Member
- Join Date
- Apr 2014
- Location
- Taihape
- Posts
- 120
- Rep Power
- 46
Are you using an American voice file? If not you could try one.
Voices for different parts of the world have different routines for interpreting numbered roads e.g. A Uk english voice will not read US road numbers correctly.
This has nothing to do with the android voice you use.
Sent from my SM-A310Y using Tapatalk
-
28th October 2019, 04:20 PM #266Junior Member
- Join Date
- Mar 2017
- Location
- Canada
- Posts
- 3
- Rep Power
- 0
Yes, US voice, with US Engine (tried a few from Google TTS, Cereproc, vocalizer, all same problem. I posted on another thread a voice file (older) which does not have this problem.I do not have phonemes.From what I see something got broken between older Primo voices in editing to these unisex ones.
Do not quote previous post. Read carefully:
[Only registered and activated users can see links. ]
and
[Only registered and activated users can see links. ]Last edited by Boki_Srb; 28th October 2019 at 06:08 PM. Reason: removed unnecessary quote
Advertissements
Posting Permissions
Bookmarks