Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 9 123 ... LastLast
Results 1 to 10 of 84
  1. #1
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default Need help with TTS road name

    I am using the latest Nextgen Skin Basarsoft by osiris4isis which does not come with TTS voices. I have added TTS voices and they are are recognized and working nicely with iGo. My issue is that the TTS voice says Turn right on R-T-E 777 instead of saying turn right on ROUTE 777.

    I have checked in the config_transform_tables.lua file and I can see the lines:
    {1, L"RTE", L"ROUTE"},
    {1, L"RTES", L"ROUTES"},

    I also added in the dictionary.voice file the line:
    Rte, %s.="Route, %s."
    I also tried
    Rte="Route"

    Still says R-T-E

    Any suggestions?

    Your help is much appreciated...

  2.    Advertissements


  3. #2
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    What TTS voice package you use?
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  4. #3
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    I am a bit baffled. I downloaded so many different tts packages aver the years for so many different versions of Igo that I cannot specifically name the package. I just have the zip files and they work....The TTS zip files I am referring to are called Voice_TTS-android-fra-can-lua.zip and Voice_TTS-android-eng-us-lua.zip. I have been working mostly with the french one as it had the RTE lines in the transform table as indicated in post #1 but both ones do not work.

    Just to help you identify the package, I am pasting the info.ini of the eng-us file

    [ I N F O ]
    L C I D = 0 x 0 4 0 9
    a s k _ r e c a l u l a t e = " O f f r o u t e ! R e c a l c u l a t e ? "
    b r a n d = " P i o n e e r "
    c m l a n g k e y = " V o i c e _ E n g l i s h - u s "
    f l a g = " f l a g _ u s a . b m p "
    f l a g _ i c o n = " c o u n t r y f l a g _ u s a "
    g p s _ d i s c o n n e c t = " G P S d i s c o n n e c t e d . "
    g p s _ s i g n a l _ l o s t = " G P S s i g n a l l o s t . "
    l a n g _ e x t e n t i o n _ f l a g = " "
    l a n g u a g e k e y = " e n g l i s h U S "
    l a n g u a g e n a m e = " E n g l i s h ( U S ) "
    l u a _ e n g i n e _ v e r s i o n = " 1 _ 0 "
    l u a v o i c e = 1
    n a m e = " ( T T S v 4 ) v 6 1 3 3 1 4 "
    o f f r o u t e = " O f f r o u t e ! "
    o v e r s p e e d = " Y o u a r e o v e r t h e s p e e d l i m i t . "
    p h o n e m e _ l a n g = " E N U "
    r e c a l u l a t e = " R o u t e r e c a l c u l a t i o n . "
    s e x = " "
    s v n r e v i s i o n = " 6 1 3 3 1 4 "
    t e s t s o u n d = " H a v e a n i c e t r i p , d r i v e c a r e f u l l y . "
    t i m e s t a m p = " 1 4 4 8 0 0 7 9 1 9 "
    t i m e s t a m p _ r e a d a b l e = " 2 0 1 5 _ 1 1 _ 2 0 _ _ 0 9 _ 2 5 _ 1 9 "
    t m c s u p = 1
    t r a f f i c _ j a m = " T r a f f i c j a m a h e a d . "
    t t s _ d e s t n a m e s = 1
    t t s _ e n g i n e = " a n d r o i d "
    t t s _ e t a = " Y o u w i l l a r r i v e a t y o u r d e s t i n a t i o n a t % I : % M % p "
    t t s _ l a n g n a m e = " e n g - U S A "
    t t s _ r a t e = 1 0 0
    t t s _ v o i c e n a m e = " N / A "
    t t s v o i c e = 1
    u n i t s s u p _ k m m = 1
    u n i t s s u p _ m l f = 1
    u n i t s s u p _ m l y = 1
    v o i c e I D = " 3 6 3 4 "
    v o i c e k e y = " T T S _ a n d r o i d _ e n g _ u s _ l u a "

    and I am including the french can zip file for your benefit.
    Attached Files Attached Files

  5. #4
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    I'm using the US voice that I've created for VocalizerEx and I don't have problem with RTE being pronounced "route" You might want to give that a try [Only registered and activated users can see links. ]
    Last edited by osiris4isis; 1st August 2016 at 05:03.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  6. #5
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    As suggested, I have loaded your file called "Voice_TTS-nua-eng-us-f1-lua-dri40-vssq5f22.zip" and Samantha says Rte, not Route. I have tried Audrey in French with the same result. Maybe in Europe, your "Routes" are labelled Route not Rte in the Navteq maps. That would explain why you never hear Rte. On my iGo screen, the top line displays Rte-100, not Route-100. What about you?

    In my previous installation (Primo), I managed to fix the issue by adding the lines Rte="Route" and Aut="Autoroute" in the dictionary.voice file. Somehow now, under Nextgen, it doesn't do the trick. I see now that the data.zip, config_transform_tables.lua, dictionary.voice, global.cfg, sys.txt or UX files can control to some extend the way TTS works. It's becoming difficult to find a solution when I do not know which file has priority over the next ones and why there are so many different places to control TTS.
    Last edited by varso; 1st August 2016 at 19:33.

  7. #6
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    With US map, I hear "route" and not "RTE" (like Route 66, a famous US highway). Some streets where I live has two names: the main name and its old name which can be a "route". I never hear RTE. I'll bet the map engine is returning a different name; maybe "rte-100" instead of "rte100" and it gets processed differently. Which map are you using?
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  8. #7
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    I am using the latest North America maps from Navteq. The streets are labelled as Rte-111. I think you may have something here. I will try using Rte-="Route" to see if it works.

  9. #8
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    If you are curious about this, would you please set a simulation from starting point (Canada, Quebec, Lachute, Route Principale, 1065) ending point (Canada, Quebec, Lachute, Rte-329, 45) and you will see that Samantha will say Rte. It's a 15 seconds simulation....

    I have tried the Rte-="Route" and it did not work.

  10. #9
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    Unfortunately, I do not have enough space on my phone to have Canada map to test. I would love to see this happen because I'm curious about the solution as well. Meanwhile, you can try this
    Spoiler: .

    This post requires you to click the "LIKE this post" button and hit F5 to read this content.
    Last edited by osiris4isis; 2nd August 2016 at 02:27.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  11. #10
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    I tried your suggestion and it did not work. I did find a street with RTE for a search. Starting point (California, Upland, College commerce way, 550) ending point California, Upland, W arrow Rte, 1915). The problem is, on my phone, TTS just says turn left on next street. It does not name the road so I cannot test the Rte to Route translation.

    I noticed something, If you do a search for a street called RTE in the States, the search results are almost always named Route with a few exceptions having Rte somewhere in their names. In Canada, you see search results with Route and many RTE too. Maybe this is unique to Canada. Obviously, Navteq does not have a standardized naming convention for street abbreviations.... RTE searches are translated to Route by iGo in USA and RTE stays as RTE in Canada.
    Last edited by varso; 2nd August 2016 at 14:24.

 

 
Page 1 of 9 123 ... LastLast

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