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

    Default

    Many thanks for your help. Sorry if I have missed your offer before and you are right, I would rather be independent about generating my own logcat so I can play with it. I find it quite fascinating actually. . Actually, I was just doing some experiments with ADB to see if I can grab more data from iGo. So far, same data but labelled differently.

    Here you will find the Osiris4isis TTS file

    Looking forward to your logcat

    [Only registered and activated users can see links. ]

  2.    Advertissements


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

    Default

    I want to tell you I fixed all the errors I found to date with few changes in the the transform_tables of the Fr-Can TTS from Zervdim. I think I will send Zervdim the corrections as the Fr-Can file is specifically designed for the French section of Canada. I am reluctant at this point playing with the US file (many americans travel to the French Canada section as it gives them the European feeling without the airfares). I am afraid it may break other things in the US. It will be a future project if Zervdim accepts my proposed changed for the Fr-Can file otherwise no point spending time on a project I can't share.

    @osiris4isis
    Unfortunately, the same corrections did not seem to "hold" in your TTS. I am willing to redo the same fixes now that I understand more what I am doing. I might have made wrong assumptions or plugged the code into the wrong sections.

    This is the fixed Fr-Can TTSpro from Zervdim

    [Only registered and activated users can see links. ] My changes are:added lines 105, 124, 356, 401 into the config_transform_tables.lua file

    Thank you for your help. You both have been very generous with your time. I consider my request for help completed however, if osiris4isis wants to incorporate the corrections into his TTS file, I am willing to give it a try.

    As for the logcat issue, do you want to push it forward with a new thread or you prefer to wait for someone having a need for it be the champion?
    Last edited by varso; 9th August 2016 at 15:29.

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

    Default

    So you fixed the "RTE" issue as well? If so, that's great news! If fixed, are you saying that you were able to fix it in the Zervdim voice, but the same fix doesn't work with the osiris4isis voice file?

    Regardless, here is why I see in my WinCE debug.log file regarding this issue (sorry it took so long, had to install Canada map and refresh my memory on how to set a start point! :-) ):

    Also, when I now see is that the first set of information is what iGo reads from the map file and the second set of information is what iGo sends to the TTS engine (not what the TTS engine converts it to) - important difference....

    First, I couldn't get iGo to even say "R T E" at all - it was saying the road name instead, which was a result of my sys.txt settings. Originally, I had these lines under [tts] in my sys.txt and iGo said the road name instead of the route number (not sure exactly which line it was, but it was one of these 3 lines):

    Code:
    Please Login or Register to see the links
    Here is the TTS portion of the log file with those settings:

    Code:
    Please Login or Register to see the links

    Then, when I commented out those 3 sys.txt lines, here were the results:

    Code:
    Please Login or Register to see the links
    Interestingly, the only difference between a Nuance voice (Samantha) and a Loquendo voice (Dave) is that the Loquendo voice said "R T East 329" instead of "R T E 329". :-) Obviously, I can fix that in my Loquendo .lex file (or maybe even in the voice file itself), but... Just an FYI.

    I hope that helps. Although it sounds like you found the real issue before I got a chance to post this anyway. It seems that, for whatever reason, iGo is changing "RTE" to "R T E" before sending it off to the TTS engine. I suspect that is what is causing you grief. I think this is an easy fix in Loquendo (by adding "R T E" = "Route" to the .lex file), but not sure off hand how I would need to fix in Nuance....

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

    Default

    Whoa, what you find is very interesting. Your reply is very long. You might have missed my edit. I listed the corrections I made into Zervdim TTS file. Not sure these fixes will work on osiris4isis file as logic is not the same. For instance, I had to fix the St =Street to St=Saint and Ste=Sainte in osiris4isis but not on Zervdim but most important, Rte- was replaced by R T E in Osiris4isis but stayed as Rte- in Zervdim. It means it was transformed in osiris4isis but we were not able to pinpoint where the transformation occurred because of poor logcat. I did not have to deal with a transformation within the Zervdim.

    Would you mind sending the logcat if you still have them. I want to analyse them for educational purposes.


    After I solved the TTS problems, I removed all references to logcat into sys.txt and decided to run adb.exe logcat|find "navngo" to see if the level of detail would be different. To my surprise, I got exactly the same info. It was like the only line working in sys.txt was logcat_file="/sdcard/iGo_Basar/debug/logcat.log". The rest was irrelevant. Hopefully Android/NextGen has other commands to trigger detailed logging.

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

    Default

    actually it is the opposite or you got your name reversed..., The Loquendo transformed the Rte-329 to R T East 329 so the RTE="Route" would not work because it is not a match. In Nuance, no transformation therefore a match. That's why the fix will work in your Nuance file. It's just for the sake of arguing..... I am in a very good mood as it is over.... I was feeling so sorry for you guys being dragged into this mess for 8 pages over a week. I appreciated you all tagged along.

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

    Default

    Quote Originally Posted by varso View Post
    actually it is the opposite or you got your name reversed..., The Loquendo transformed the Rte-329 to R T East 329 so the RTE="Route" would not work because it is not a match. In Nuance, no transformation therefore a match. That's why the fix will work in your Nuance file. It's just for the sake of arguing..... I am in a very good mood as it is over.... I was feeling so sorry for you guys being dragged into this mess for 8 pages over a week. I appreciated you all tagged along.
    Actually, let me clarify - the log files looked *exactly* the same with both the Nuance and Loquendo TTS engines/voices. Again, the log file only shows what iGo sees in the map files and what iGo sends to the TTS engine - it doesn't really show how the TTS engine "interprets" the information (what the TTS engine *actually* says).

    The difference is that the Nuance TTS engine actually said "R T E 3 29" whereas the Loquendo TTS engine actually said "R T East 329" - even though the iGo log file shows that "R T E 3 29" was sent to the TTS engine in both cases. So in order to make Loquendo actually say "Route 3 29", I could add an "R T E" = "Route" line to the Loqeundo TTS engine "EnglishUS.lex" file, so that Loquendo would actually say "Route" when it sees "R T E" instead of saying "R T East". At least that's my theory. I'll have to test that just because I'm curious. But that is how I "fixed" other issues similar to that. I may also be able to fix it by modifying the dictionary.voice file in the voice file itself as well. However, I've found that I've had more luck fixing this issues directly in the .lex file (for Loquendo TTS voices) - even when the same entry in the voice "dictionary.voice" file didn't fix it.

    I hope that makes sense. :-)

    And by the way, do NOT feel sorry for "dragging" us into this. Personally, I enjoy this kind of stuff! I like learning how this all works myself, just as you're finding that you kind of enjoy it!

    Let me create new, clean log files for you and then I'll post them (the original log files have a lot of other "crap" in them that you don't need (me going through the menus trying to figure out how to manually set start point, changing settings, etc.... But I will create new, clean log files and post them shortly.


    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  8. #77
    Important User

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

    Default

    Quote Originally Posted by varso View Post
    Rte- was replaced by R T E in Osiris4isis but stayed as Rte- in Zervdim. It means it was transformed in osiris4isis but we were not able to pinpoint where the transformation occurred because of poor logcat. I did not have to deal with a transformation within the Zervdim.
    You might want to compare what I mentioned in post #44 between my voice file and zervdim.
    "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!

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

    Default

    Hi oriris4isis,
    I do intend to compare both voice-TTS files and see where the transformation occurred. My job will be easier if I look at jtrosky's logcat files. Just to see exactly what is stored in the variables is a big help. Many variables have very similar names but I do not know their exact purpose. An example I have in mind (maybe not real in our case) would be the variables road and Street. I am very busy for the next 2 days. I will definitely do a follow up.

    @jtrosky
    I have been told at the beginning that I could fix my problem by bypassing iGo and fixing the pronunciation with the VocalizerEx engine. The user told me he fixed few problems that way in the past. It works but you must admit it is not the best solution... fixing one program by patching another one.

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

    Default

    @varso - here is a .zip file that contains two separate logs - one when the US English Nuance TTS Samantha voice is selected and one when the US English Loquendo TTS Dave voice is selected. These voice files originally came from @zervdim, but I believe that I may have modified them slightly... Actually, when troubleshooting some issues with differences between the Loquendo and Nuance TTS voices, I ended up making the voice files contents exactly the same for both Nuance and Loquendo TTS voices (except for the contents of the info.ini file). This way I had consistency between Loquendo and Nuance TTS voices (in terms of TTS Pro phrases, etc).

    Hope this helps. Please let me know if there is *anything* else I can do to help. This was a great thread - lots of great info for others, especially those just learning the ins-and-outs of the TTS engines/voice files.

    Oh - one more thing, you might want to take things a step further and start looking into Lua files themselves. Use the JiGOLua tool to decrypt the encrypted Lua files. Of particular importance for the voice stuff are the Lua files in data.zip, under "media_libs\voice_guidance". If you decrypt all of those file with JiGOLua, you can really start getting into the details of exactly how iGo handles voice stuff - VERY interesting and informative stuff! I love how iGo hardcodes VERY little into the executable binary itself... Makes it very "hacker friendly". :-)

    Let me know if you can't find JiGOLua.

    I've attached the WinCE log files here.

    [Only registered and activated users can see links. ]

    Sent from my HP SlateBook 10 x2 PC using Tapatalk
    Last edited by jtrosky; 10th August 2016 at 16:04.

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

    Default

    Thank you for the data. I will take a break for few days as I neglected other jobs around the house. I should analyze it this the week-end.

 

 
Page 8 of 9 FirstFirst ... 6789 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.