Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 14 of 21 FirstFirst ... 41213141516 ... LastLast
Results 131 to 140 of 208
  1. #131
    Pro-Member
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    384
    Rep Power
    20

    Default

    Quote Originally Posted by Mike Hunt View Post
    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).
    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.
    Attached Files Attached Files

  2.    Advertissements


  3. #132
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    167
    Rep Power
    87

    Default

    Quote Originally Posted by De5i View Post
    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.
    Are you sure this is an Android voice file?
    In info.ini:
    tts_engine="loquendo_7"
    So I see it in my regional selections, but I cannot choose it to test.

    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.

  4. #133
    Pro-Member
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    384
    Rep Power
    20

    Default

    Quote Originally Posted by Mike Hunt View Post
    Are you sure this is an Android voice file?
    In info.ini:

    So I see it in my regional selections, but I cannot choose it to test.

    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.
    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.

  5. #134
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    167
    Rep Power
    87

    Default

    Quote Originally Posted by De5i View Post
    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.
    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.
    Please do. I'm curious about that.

  6. #135
    Member +
    Join Date
    Oct 2012
    Location
    uk
    Posts
    90
    Rep Power
    8

    Default

    Im using the Voice_TTS-nua-eng-Joe-2.zip file but same results with others that Ive tried. Im also getting the phrase "Slow Down" when approaching speedcam even though Im not speeding. Using Svox /Victoria speech engine. As previously mentioned TTS seems to be fine apart from this.
    Are these 2 lines required in sys.txt
    say_camera_distance=1
    say_camera_speed_limit=1

    Also the volume is too quiet over headphones. Volume is fine over Primo through my crash helmet headphone speakers but Nextgen only outputs about half that volume in comparison

  7. #136
    Pro-Member
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    384
    Rep Power
    20

    Default

    Quote Originally Posted by Mike Hunt View Post
    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.
    Please do. I'm curious about that.


    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

  8. #137
    Member +
    Join Date
    Oct 2012
    Location
    uk
    Posts
    90
    Rep Power
    8

    Default

    Doubtful, its exactly the same for me on Android

  9. #138
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    167
    Rep Power
    87

    Default

    Quote Originally Posted by japseye View Post
    Im using the Voice_TTS-nua-eng-Joe-2.zip file but same results with others that Ive tried. Im also getting the phrase "Slow Down" when approaching speedcam even though Im not speeding. Using Svox /Victoria speech engine. As previously mentioned TTS seems to be fine apart from this.
    Are these 2 lines required in sys.txt
    say_camera_distance=1
    say_camera_speed_limit=1

    Also the volume is too quiet over headphones. Volume is fine over Primo through my crash helmet headphone speakers but Nextgen only outputs about half that volume in comparison
    This causes this. Remove that line from sys.txt, and that bug will go away.
    You can try one of these..slightly modified recently and tested yesterday to find that both say on overspeed:
    "The speed limit is %s! Slow down."
    %s in this case being the variable used for speed limit which is correctly vocalized.

    [Only registered and activated users can see links. ]

    If you are still not getting the speed limit variable, there is something that is interfering with the definition of that variable based on context. If it was a different voice file, it could be in one of the *.lua files within the voice file, or it could be a particular skin that is introducing a conflict. I use Pongo which you could try if you want to see if that makes a difference. Other than that, I really don't know.

    Oddly, I had that problem with Primo, and it went away with NextGen.
    Once headphones are plugged in, on most Android systems, volume control is passed to DSP Manager which seems to remember settings on a per-app basis. Make sure all your system volumes are still at max after you plug in the headphones with NextGen running. Other than that, I was never able to solve the issue with Primo.

  10. #139
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    167
    Rep Power
    87

    Default

    Quote Originally Posted by De5i View Post
    [/B]

    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
    Somehow the variable context for "speed limit" is being misinterpreted during navigation to say the unit of measurement "miles".
    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.

  11. #140
    Member +
    Join Date
    Oct 2012
    Location
    uk
    Posts
    90
    Rep Power
    8

    Default

    Thanks Mike.
    I tried using kph instead of mph and it worked but is not much use to me living in UK. It appears that alterations have been made to cater for Europe and once again UK settings dont work correctly. All of the skins that I have tried give problems. For example we drive on the left hand side of the road over here but when approaching a roundabout the skins give a warning "no left turn" which is absurd.

    Is there any way that this version can be fixed to give correct instruction for mph. Im sure that there are many UK users that love this software.

    Bit off topic but any idea why Speed Limit Settings keeps defaulting back to 110% after a restart even though I have set them to 100%

 

 
Page 14 of 21 FirstFirst ... 41213141516 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.