Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 271

Hybrid View

  1. #1
    Master
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    287
    Rep Power
    68

    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. #2
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    169
    Rep Power
    100

    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. #3
    Master
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    287
    Rep Power
    68

    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. #4
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    169
    Rep Power
    100

    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. #5
    Master
    Join Date
    Mar 2013
    Location
    Blath
    Posts
    287
    Rep Power
    68

    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

  7. #6
    Master Mike Hunt's Avatar
    Join Date
    May 2014
    Location
    Europe
    Posts
    169
    Rep Power
    100

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

 

 

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
  •