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

    Default

    Do not add the "debug_tts_manager=1" line in the debug section. Nextgen will not generate the logcat.log.

    Isiris4isis is right. The exact text sent to the TTS engine is different than what iGo displays (French voice but same ending in English) 'Prenez la première À* gauche, R T E 329 . '

    There are spaces between the letters. That cuts down a lot of testing. I will retry the suggestions posted in #11 to 19.

  2.    Advertissements


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

    Default

    It may not matter on Android anyway, but the "debug_tts_manager=1" line goes under the [tts] section in sys.txt, not the [debug] section.

    It sounds like you are getting all of the details you need anyway, so you probably won't benefit from it even if it does work, but I just wanted to post that clarification.

    Hope you get your speech issues fixed up now though! The logs helped me fix a few TTS-related issues too (same issue - wasn't sure how the maps were reporting certain things).

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

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

    Default

    I have already fixed a few issues like some local streets end with a O(Ouest) instead of the W(West) and many streets start with ST(Saint) and Ste(Sainte) and were transformed to street. These were easy to correct however, I am still fighting the Rte-329 mystery. I do not understand why and where the Rte-329 is transformed into R T E 329. I am not sure if there is already some sort of transformation happening and I can't locate the code or it is stored as R T E but displayed as Rte-.

    I am not giving up. It's kind of fun and I learn a lot while testing.

    If someone have ideas where to look, please share.

  5. #44
    Important User

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

    Default

    Something to try
    Spoiler: .

    This post requires you to click the "LIKE this post" button and hit F5 to read this content.
    Last edited by osiris4isis; 5th August 2016 at 12:58.
    "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. #45
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    @Jtrosky
    Forget what I said about the debug_tts_manager=1 line. I noticed I was getting too tired and going too quickly testing many things at the same time in order to reduce the number of launching and testing cycles. I was getting sloppy and noticed I did a mistake on the sys.txt. The line was there all along in the TTS block.

    I now work more systematically by writing down what was tried. I tried all possible strait text replacements and none worked. I now concluded I have to deal with a more complex transformation. I will not test for a few days. I am now learning LUA patterns so I will understand what the lines in the transform tables are doing. Once I feel more comfortable, I will have a look at the config_transforms.lua line as posted in #44.

    @Osiris4isis
    Hex Workshop shows 202052205420452033323920202E20270A. So it is real spaces. The only difference between the "R T E 329 ." line and the other TTS lines is that there is 2 spaces after the 9 while all the other lines have only one. I suspect the Rte-329 has been processed by one of the transform files as some of the lines/code add an extra space at the end of the transformation. I doubt the extra space was part of street name in the map. Too bad we can't verify if the hyphen is stored in the map name. If yes, it means the transform table dropped the hyphen which would confirm it is not a strait text replacement (like R T E='Route'). It would involve a transformation parsing the street name and stripping unnecessary text.
    Last edited by varso; 5th August 2016 at 13:54.

  7. #46
    Important User

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

    Default

    Unless you can traced where the debug code are outputted, you don't really know if there is any "post processing" done to the actual roadname taken from map engine. Do this: truncate log file so that it's empty then run proggy to get log data and see if roadname are outputted. Do this 3 times and post those log files. I might be able to help track down those logs.
    "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. #47
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    I did a car ride this morning and without guidance, the logfile does not have any street names. I think the only way to see street names with logcat_level=7 is what the app is sending to the TTS engine which is already processed by the transform tables at that point. I tried logcat_level=1 and logcat_oslevel=7 in the sys.txt. It created about 5 lines into the logcat file. Do you know what the "values for logcat_level do?

    Do you still want me to do 3 different route simulations with many road changes or would you prefer that we test different values for logcat_level=7 until we get iGo to log street names in the logfile first?

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

    Default

    Just another way to get a logcat generated maybe easier if you are familiar with ADB. Just need to type adb.exe logcat|find "navngo" and launch igo. You will see the lines building up in the Command windows as you go and stops when you exit iGo.

    It gives you exactly the same info than the logcat generated by logcat_level=7. The only difference is that the ADB command gives you a header such as TTSSpeakerImpl: at the beginning of each lines while the logcat.txt does not.

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

    Default

    By the way, I found an easy way to test TTS "phrases" when trying to correct some stuff on my WinCE device. Instead of trying to plan and simulate routes that hit the streets you want, just put the text that you want to test into the TTS Voice "test" phrase (in the voice file .ini file). That way, you can test the TTS "conversions" just by selecting the TTS voice in iGo... Makes it a lot quicker and easier to test TTS changes.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  11. #50
    Important User

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

    Default

    Remember that the "test" phrase in .ini fille will only works if it's not taking the one in the audio directory which some voice file contained. So for TTS, remove audio directory.
    "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!

 

 
Page 5 of 9 FirstFirst ... 34567 ... 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.