Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 6 of 9 FirstFirst ... 45678 ... LastLast
Results 51 to 60 of 84
  1. #51
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    ^^Good point! I didn't even think about that since I *always* remove the "audio" directory for TTS voices since I usually "customize" the "test sound" line.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  2.    Advertissements


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

    Default

    I have changed the testsound line to Soundtest="Cote ST-Andre O." in info.ini. When selecting the TTS voice, iGo says "cote Saint-Andre O" but when navigating, iGo says "cote Saint-Andre Ouest" (Ouest is West in French). My conclusion is that trick will test the TTS pronunciation but the text does not go through the transformation tables. My goal is to transform Rte-329 to Route 329. Unless I am missing something, I can't test using this trick.

  4. #53
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    Interesting... Seems like another difference between WinCE and Android. On WinCE, I used that method to test the actual transformations (and it works). For example, I used it to fix things like the way the TTS engine pronounced "US 1S", which was pronounced as "U South 1 South" instead of "US 1 South"). I guess it's a difference with the way the TTS system is implemented in Android.
    Damn, I'm really striking out with my "tips" here! :-) I guess WinCE and Android are just too different to use the same test "methods".. Specifically, with TTS, WinCE and Android are very different - WinCE uses "add-on" TTS engine like Nuance and Loquendo, whereas Android versions go through the Android TTS "system" (I think).

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  5. #54
    Important User

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

    Default

    Quote Originally Posted by varso View Post
    I have changed the testsound line to Soundtest="Cote ST-Andre O." in info.ini. When selecting the TTS voice, iGo says "cote Saint-Andre O" but when navigating, iGo says "cote Saint-Andre Ouest" (Ouest is West in French). My conclusion is that trick will test the TTS pronunciation but the text does not go through the transformation tables. My goal is to transform Rte-329 to Route 329. Unless I am missing something, I can't test using this trick.
    Explanation
    Spoiler: .

    This post requires you to click the "LIKE this post" button and hit F5 to read this content.
    Last edited by osiris4isis; 7th August 2016 at 21:16.
    "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. #55
    Important User

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

    Default

    Quote Originally Posted by jtrosky View Post
    Interesting... Seems like another difference between WinCE and Android. On WinCE, I used that method to test the actual transformations (and it works). For example, I used it to fix things like the way the TTS engine pronounced "US 1S", which was pronounced as "U South 1 South" instead of "US 1 South"). I guess it's a difference with the way the TTS system is implemented in Android.
    Damn, I'm really striking out with my "tips" here! :-) I guess WinCE and Android are just too different to use the same test "methods".. Specifically, with TTS, WinCE and Android are very different - WinCE uses "add-on" TTS engine like Nuance and Loquendo, whereas Android versions go through the Android TTS "system" (I think).

    Sent from my HP SlateBook 10 x2 PC using Tapatalk
    What I read from your previous posts, you seem to favor (and uses) Loquendo over Nuance on WinCE, right? Loquendo TTS engine is totally different from Nuance (and its successor, Vocalizer*) so I would expect the "test trick" to behave differently. The other thing that is different is that VocalizerEx on android is much newer than Nuance on WinCE so API would of changed/enhanced. As far as using VocalizerEx as part of proggy (like ve1) or going through android, they should be very similar because they are coming from the same provider for same OS that guarantee to work with same proggy.

    * and as memory served me correctly, Vocalizer bought Loquendo at some point (but API might still be different)
    Last edited by osiris4isis; 7th August 2016 at 21:19.
    "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!

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

    Default

    Quote Originally Posted by osiris4isis View Post
    Best way (and correct way) is to find the log API and use it to help debug the problem.
    Do you have any idea about logging the API? I have been learning a lot up to now but I don't even have any idea about where to start looking for logging the API.

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

    Default

    When I was programming, if I wanted to follow the flow of the program, I was putting few print statements in strategic locations. That way, I was able to see variable values as well as confirm that the section of codes were processed or skipped. Is there a lua command that would only show in the log without interfering with iGo?

  9. #58
    Important User

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

    Default

    API means Application Programming Interface, it's a term used by software developer to indicate the document (function/procedure call and interface) of a particular library used. For example, ideally you want the API to VocalizerEx TTS which tells you what are the function/procedure. Unless you work for VocalizerEx (or bought their developer library, if possible), won't happen. Next best thing to do is to look for it in existing codes that uses it and "guess" what it does and what are the parameters passed to the functions. This is why I ask for the posting of your logs so I can try to find it in the codes. It might be that VocalizerEx logging doesn't go to android log file.
    "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!

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

    Default

    I am ready to send you 3 different log files as requested. Sorry for not sending them. I asked you in post #47 if you wanted 3 different routes simulations and you never replied. I assumed you were finding the log files not so useful based on my observations about their contents. Simulation should be good enough as according to my experience, real GPS does not provide additional detail. I will be doing long routes to collect as much TTS data as possible. I will do them in English using your own file. You want them posted here or by a private message.

    Last point, I do not use VocalizerEx. I use Android TTS engine which give me a very natural voice. I tried Pico and the voice is robotic. As I never use TTS except for iGo, I saw no need to install VocalizerEx. In addition, the RTE error is done by iGO, the TTS is just reading what it gets. Plus your tts voices works perfectly with the Android TTS engine.

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

    Default

    You will find the 3 log files as requested. I published them here as they are not close to where I live. This is what I found of Interest while using iGo in English and using Samantha TTS english by osiris4isis

    Route3
    log shows weird symbols for French street names with accents. TTS handles them correctly. This is just ASCII errors in logcat. To be ignored
    St are translated as Street not Saint. I easily fixed it in my French TTS voice.
    O is read as is. Not transformed to Ouest. Fixed in French TTS
    Of course the Rte-329 is read as R T E 3 29 (twenty nine)
    Waypoint is converted to viapoint
    Highway exit numbers such as <^item^lang=FRE^ort= 60 have lang=FRE but are read in English which is ok.
    Aut-15 (should be transformed to Autoroute 15 is transformed to State Route 15) Aut-15 and Rte-15 maybe using same transform table.... Might be a clue

    Route2
    Nothing more than what listed under Route3

    Route1

    same transform error for aut-15, aut-440 and aut-640

    Overall comment, I tried changing the settings "say road names in Native language and Foreign Language with no effect in the pronunciation. Maybe Navteq listed Canada as 100% English. It is so incomprehensible that I have to use French TTS in Quebec and English TTS everywhere else in America. That explains why I work with your TTS and the French one at the same time.

    If you want me to simulate specific routes or issues, just let me know. I will gladly comply.

    [Only registered and activated users can see links. ]

 

 
Page 6 of 9 FirstFirst ... 45678 ... 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.