Likes: 
What voice file are you using? Attach it and I'll take a look. Mine, in English, seems to work as expected for the overspeed warning (always says the speed limit).Originally Posted by japseye
EDIT: In thinking more about this, the alert that you are getting is sort of typical of the default alert in just about every voice file..in info.ini, --at least this part is: You are over the speed limit:not dictionary.voice. The more specific alert with the speed limit, comes from dictionary.voice (which always over-rides info.ini). So it is possible that your dictionary.voice file does not have the proper phrases at all, or something is causing a conflict. If you post your file, I can take a look at it, or try one of the (English?, other language?) voice files I have already posted previously to see if that works.
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 274
Thread: TTS Nextgen discussion
Hybrid View
-
26th September 2015, 11:12 AM #1Master
- Join Date
- May 2014
- Location
- Europe
- Posts
- 159
- Rep Power
- 103
Last edited by Mike Hunt; 26th September 2015 at 02:34 PM.
-
26th September 2015, 11:17 AM #2Master
- Join Date
- Mar 2013
- Location
- Blath
- Posts
- 285
- Rep Power
- 71
I have the same issue it does not say the speed value, it says You are over the speed limit, the speed limit is miles" attached is the voice file i am using. Originally Posted by Mike Hunt
-
26th September 2015, 01:37 PM #3Master
- Join Date
- May 2014
- Location
- Europe
- Posts
- 159
- Rep Power
- 103
Are you sure this is an Android voice file? Originally Posted by De5i
In info.ini:
So I see it in my regional selections, but I cannot choose it to test.tts_engine="loquendo_7"
In looking over your dictionary.voice file, there is a lot of stuff in there that may no longer be applicable in NextGen. Many skin commands/additions.
Much of the diMka still works, totally not sure about the others. Specifically for NextGen, that file is more than twice as big as it needs to be. There could be some entries that are cancelling each other out. I could edit it, but then I could not test it. So I suggest you try the posted dictionary.voice sample I posted for 'translation' earlier in a copy of your voice file, and then see if the overspeed alert works as it should. If it does, you can add back in whatever you want from your original file that will not conflict.
-
26th September 2015, 01:44 PM #4Master
- Join Date
- Mar 2013
- Location
- Blath
- Posts
- 285
- Rep Power
- 71
The voice file I am using is on WinCE with Loquendo_7 TTS engine that is why you are not able to select it. Are you able to test this on WinCE? In the meantime I will try the posted dictionary.voice to see if this cures the issue and let you know. Originally Posted by Mike Hunt
-
26th September 2015, 02:26 PM #5Master
- Join Date
- May 2014
- Location
- Europe
- Posts
- 159
- Rep Power
- 103
Not really. Nothing that I have will be able to use Loquendo voice files. Sorry. Not even those designated for Android. Somehow, whatever modifications were used to make the older Loquendo voices compatible with Primo and further, will not work for me in a 'pure' Nuance situation. Originally Posted by De5i
Please do. I'm curious about that.
-
26th September 2015, 04:04 PM #6Master
- Join Date
- Mar 2013
- Location
- Blath
- Posts
- 285
- Rep Power
- 71
Originally Posted by Mike Hunt
Hi Mike,
I tried the dictionary.voice and it still will not say the speed limit value, it says the limit "The speed limit is miles, slow down". I have tried this with Loquendo and nuance TTS voices and both give me the same result. So its not the voice file at fault here. I can hear the speed limit value being spoken in the Test TTS menu but not in normal navigation mode.
This could point to the something in WinCE app not able to say the speed limit
-
27th September 2015, 06:27 AM #7Master
- Join Date
- May 2014
- Location
- Europe
- Posts
- 159
- Rep Power
- 103
Somehow the variable context for "speed limit" is being misinterpreted during navigation to say the unit of measurement "miles". Originally Posted by De5i
Could be like described above..some conflict, or could be as simple as a flaw in unit designation. I use 'kilometers' as opposed to 'miles'. In the UK (which is the language file for English with the original distribution), I know it can go either way as far as roads go. It would be interesting to find if you eliminated 'miles' and switched to 'kilometers' if the problem went away. At least that would narrow it down to the language file to examine.
EDIT: PS. Tested on my WinCE device (which I rarely use), same voice file, same skin, etc..all set up identically as possible to Android, and everything works, so it's definitely not a version thing.Last edited by Mike Hunt; 27th September 2015 at 11:58 AM.
Reply With Quote
Bookmarks