Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 8 of 13 FirstFirst ... 678910 ... LastLast
Results 71 to 80 of 130
  1. #71
    Junior Member
    Join Date
    Sep 2019
    Location
    Spain
    Posts
    2
    Rep Power
    0

    Default

    Hi! I've found a mistake in line 333.

    File >>> config_database.lua in Spanish_universal_unisex_andTTS-Boki_Srb_v.1.zip

    Path >>> Spanish_universal_unisex_andTTS-Boki_Srb_v.1\config\

    L"Prepárese para coxer el ferry, dentro de %dist3",

    "coxer" should be "coger".

    Thanks.
    Last edited by Trismagia; 10th October 2019 at 04:43 PM.

  2.    Advertissements


  3. #72
    iGO Enthusiast Universal unisex TTS and engines v.1.x
    Universal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.x
    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    52
    Posts
    6,397
    Rep Power
    4260

    Default

    Possible.
    It is not possible to know all the languages or translate them. Original files were used. So:
    Quote Originally Posted by Boki_Srb View Post
    ...NOTE:
    Languages that have an engine and have no voice can be made by translating English-US_universal_unisex_andTTS-Boki_Srb_v.1.zip
    From this ZIP file translate next sub files:
    dictionary.voice
    config_database.lua (section: patterns and poi)
    config_numbers.lua (section: distances.patterns and ordinals)
    and send me the translated files on PM
    ...
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  4. #73
    Junior Member
    Join Date
    Dec 2018
    Location
    FRANCE
    Posts
    4
    Rep Power
    0

    Default

    Hello everybody,

    I am facing a strange issue trying to get TTS voices working on both Igo Primo and NextGen on my Android 6 device.
    I installed VocalizerEx2 TTS engine, and language pack. When I run a trial it works normally.
    In Igo/content/voice I installed the "French_universal_unisex_and TTS-Boki_Srb_v.1.1.zip" mentionned in post 1.
    When I go in Igo to parameters I can select French universal unisex android TTS, and I get the sample according to th voice selected in Vocalizer engine.

    But when it comes to navigation, most of the time it remains quite, no guidance, it speaks may be one time over 10.

    I tryed to replace the "French_universal_unisex_and TTS-Boki_Srb_v.1.1.zip" in the Igo/content/voice file by "French-Can_universal_unisex_andTTS-Boki_Srb_v.1.0.zip" and I get the instructions normally.

    Can anybody have a logical explanation to this? I would say this is related to corrupted file, but other should have met the same issue and I didn't see anything about it. Does anyone have the french TTS file working?

    Thanks

    I come back with my problem, since it seems I was not complete enough.

    The Igo Primo is Igo Israel version 9.6.29.636868.

    The Igo Nextgen is Igo World 9.18.27.736653.

    None of them are skinned but remain in original version.

    The maps are Here 2019Q2.

    All is located in the internal memory.


    I tried on different devices (Android 6 and Android 9 smartphones, and Android 8 tablet, except Primo on the Android 8), and I got always the same issue, so it doesn't seem related to the used device.

    Just to summarize, as explained previously, the drawings work normally, with natural voices, the instructions come normally, I have an issue with the TTS voices to get the name of streets anounced.
    The TTS engine is installed and works normally, but with the French universal unisex TTS .zip file installed in Igo/content/voice, I can select it as voice in teh Igo parameters, I get the trial announcement , but the instructions are missing when it comes to navigation (I get may be about 1 of 10). If I replace this file with the French canadian TTS file I get the instructions back.

    But I observe an other problem : in some cases, the street name is not correct : I get strange words in the middle of the street name. For example, instead of "Rue de la Montat" it will say something like "Rue vilavila de la Montat".
    I read on the forum this could be related to the phoneme file (I had this issue on an other device running Igo 8.3 on WinCE, and deleting phoneme files solved the problem, thanks), but in this case the phoneme files are not installed.
    I tried with an older map (Here 2018Q3), but same issue with the same street names.

    I spent hours and hours to search answers on the forum before asking for help, but didn't find what I need.

    Any idea?

  5. #74
    Master
    Join Date
    Jan 2016
    Location
    Germany
    Posts
    452
    Rep Power
    654

    Default

    Maybe you try it: Post 18

    [Only registered and activated users can see links. ]

  6. #75
    Master
    Join Date
    Mar 2013
    Location
    France
    Posts
    179
    Rep Power
    85

    Default

    Or try here
    Code:
    Please Login or Register to see the links

    CODE tags for external links, dear colleague...should i remind you of the rules?

  7. #76
    Junior Member
    Join Date
    Dec 2018
    Location
    FRANCE
    Posts
    4
    Rep Power
    0

    Default

    Thanks for your help.

    I tried the files from Phildu91 and I endly could get all the instructions without the strange word I sometimes had with the french canadian TTS file. I tested all his versions, the "French_universal_unisex_andTTS-Phildu91_v.1.6.zip" sounds to me to be the best one for NextGen, but is not accepted by Primo : I can see it in the language parameters, select it, get the trial, but when I want to confirm it the program exits...So I choosed for Primo the "Voice_TTS-Android_++_FR_by_Phildu91.zip".

    All af this need to be tested more deeply but it seems to work not to bad...Thanks to eveybody, particularly to Phildu91.

    Just an other question : how to do if I want to change the way it says some instructions? I read about the "dictionary.voice" file inside the TTS zip, but I it mainly concerns display and warning, I didn't see the guidance instructions..but may be I'm tired with all this tests and I didn't look good.

  8. #77
    iGO Enthusiast Universal unisex TTS and engines v.1.x
    Universal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.x
    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    52
    Posts
    6,397
    Rep Power
    4260

    Default

    You are asking questions in wrong topic
    In addition, a good part of your questions have nothing to do with the language, which is a plain text file. Mostly, it is up to engine related
    Also, browse
    [Only registered and activated users can see links. ]
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  9. #78
    Master
    Join Date
    Mar 2013
    Location
    France
    Posts
    179
    Rep Power
    85

    Default

    @ pascalgps:
    you have to edit config_database.lua into voice file
    and make desired changes

  10. #79
    iGO Enthusiast Universal unisex TTS and engines v.1.x
    Universal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.xUniversal unisex TTS and engines v.1.x
    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    52
    Posts
    6,397
    Rep Power
    4260

    Default 15.10. Corrected Spanish TTS

    Updated Unisex_TTS.zip in OP
    15.10.2019. Corrected Spanish language (Spanish_universal_unisex_andTTS-Boki_Srb_v.1.1.zip), tnx @Trismagia
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  11. #80
    Junior Member
    Join Date
    Mar 2017
    Location
    Canada
    Posts
    3
    Rep Power
    0

    Default

    Boki_Srb I think there is a bug in the English US file.In the cases where the road (usually a highway) has the name a number or for highways exits which are also Numbers the software said the number followed by something like "backslash equal one slash" or something like this (more info on the other thread). I do not have phoenemes, and the problem is not related with the map, happens with both HERE and TT. I did try everything which came to my mind, and finally tried to use an old Primo TTS voice I had around (Ivona Kendra). Guess what, it does not have the problem !. Reads only the numbers without the backslash. So for sure the problem is in the voice file. However this file has other problems, sometimes just reads " after 1.1" (without km after) but it's random and reads 3rd as 3"road" (Your file is correct in this case. I do not have experience with these file, maybe somebody can take a look ? I attached the old file which does not have the problem.Thanks.
    Spoiler: attached
    [Only registered and activated users can see links. ]



    Possible
    But I can't know where the bugs are, nor do I create standard files. If someone has the will and the knowledge, he is welcome
    Last edited by adit; 22nd October 2019 at 11:01 PM.

 

 

Tags for this Thread

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
  •