Printable View
Hello, I had the same problem. With Kasandra TTS Voice file it is OK.Quote:
Originally Posted by vLeeuwen [Only registered and activated users can see links. Click Here To Register...]
File in content/voices/
Thanks Golom,Quote:
Originally Posted by Golom [Only registered and activated users can see links. Click Here To Register...]
You are right, deleting Phoneme solved that problem for me.
:beer:
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.Quote:
Originally Posted by Golom [Only registered and activated users can see links. Click Here To Register...]
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.
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
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.
:mn:
Do not quote previous post. Read carefully:
[Only registered and activated users can see links. Click Here To Register...]
and
[Only registered and activated users can see links. Click Here To Register...]
Hi.
While doing a longer trip after a long time I noticed that when there is a delay on route I get
the announcement that there is a delay " between " location a and b.
But of course the announcement is perfect in Dutch except instead of saying " tussen " it's " between " location a and b and
the rest in Dutch again.
Maybe someone can point me to where these words between and tussen are located to edit ?
I use iGO Nextgen :
Voice_TTS-Pro-Android-Next-Nuance(ve)-Dutch-Xander-kajoe-v.9.181.zip
tts_nua_ve1
System tts : Vocalizer Voices ( payed )
TMC~between %s and %s="tussen %s en %s"
(in Dictionary.lang)
My god rider, just give it a try.
You're not a newbie
I have in content > voice >
Voice_TTS-Pro-Android-Next-Nuance(ve)-Dutch-Xander-kajoe-v.9.181.zip > i18n > dictionary.voice
TMC~between %s and %s="TMC~tussen %s en %s"
instead of your :
TMC~between %s and %s="tussen %s en %s"
So without TMC~ after =
Right place ? Replace that line ?
I have a problem that maybe people here can help me with.
I have an OEM iGo nav system. From what I gather, Primo Nextgen.
The problem is that the Swedish TTS translation files are missing a few phrases. And that means when one of those phrases are going to be spoken, that whole subsystem stops working, and I don't get any more messages spoken. In my case warnings. So driving directions still work, but warning messages stop working.
Now, I've located which messages are missing, which files they are in and so on. But I seem to be failing in creating a new zip-file with these corrections. And I'm hoping maybe someone here can tell me how to create a new zip-file the system will be happy with.
The nav system uses an SD card. I'm using Unix (and/or MacOS). If people tell me I need Windows for this, I can probably dig something up, but it's not something I have ready.
If people want me to share anything, just let me know. And I'm a bit surprised to find such omissions in the language bits of TTS. Do they not have any customers speaking Swedish at all? Else I would have expected others to have reported this a long time ago.
Wrong place to ask, discussed many times. Browse Forum next time. Even a Google search will give you the right topic in the first place :smile:
[Only registered and activated users can see links. Click Here To Register...]
Swedish ... obviously not many users at all from that area.
[Only registered and activated users can see links. Click Here To Register...]
If you use some skin, things can get much more complicated.
I'm tested some apps on Hackintosh and of all of them, only Commander One Pro was able to pack the archive back without changing the created and modified date. Don't forget to unhide all files and remove macOS stuff before packing.Quote:
Originally Posted by sillbit [Only registered and activated users can see links. Click Here To Register...]
EDIT: For comparing and editing files, I suggest the multi-platform application Beyond Compare.