Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 9 FirstFirst 12345 ... LastLast
Results 21 to 30 of 84
  1. #21
    Member +
    Join Date
    Mar 2016
    Location
    Alaska
    Posts
    42
    Rep Power
    2

    Default

    Quote Originally Posted by varso View Post
    I did not know the text as in RTE is uppercase/lowercase sensitive...

    ...I just learned from the previous post that brackets are for optional text. The [0-9] is this for only 1 digit or any numerical?
    Everything is case sensitive but the
    (?i)
    means be case insensitive (doesn't work for non Latin characters)

    Brackets mean any *one* of the included characters. So [0-9] means any *one* digit.

    The + I suggested, means one or more of the previous. So effectively any number of digits.

    The ? means 0 or 1 of the previous (as in it may or may not exist).

    Just Google regular expressions. There are slight differences between implementations but it's very common.

  2.    Advertissements


  3. #22
    Important User

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

    Default

    Answer
    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 23:47.
    "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. #23
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    Tried all of your suggestions and still no success.
    Food for thought, I always try 2 diff TTS files, Samantha from OI4 and a french one too. I test the french because it has a much more complete data set in the dictionaries and the transform table. I have noticed that the English voice says R-T-E-3-2-9 and the french one says R-T-E-threehundredtwentynine. I do not know if this is a clue but the 3-2-9 is transformed in the French version. I have seen the code to do that transformation somewhere. I will look in which block that transformation is done. It might help finding out if RTE is handled as a road name or something else. I will come back on this.

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

    Default

    I reread your post #18. Not sure what you want. The road name per say can be seen by the screen capture I already published in post #13. I get the same syntax as the screen capture when I do a street search with RTE-. I can do a screen capture of the detailed turn by turn screens. It will show RTE-329. I can record the voices. I cannot think of another logfile.

  6. #25
    Important User

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

    Default

    Quote Originally Posted by varso View Post
    I reread your post #18. Not sure what you want. The road name per say can be seen by the screen capture I already published in post #13. I get the same syntax as the screen capture when I do a street search with RTE-. I can do a screen capture of the detailed turn by turn screens. It will show RTE-329. I can record the voices. I cannot think of another logfile.
    Do not mistaken what is shown on screen is what was passed from map engine. The only way to be sure is to output the data to logfile (or debug it via TTS voice) Vocalizer (formally Nuance) voice engine can be told how to pronounced the text passed to it. Like I said in post #18, if you're hearing "R" "T" "E", it means either voice engine is told to pronounced each letters (instead of it as a word) or the data was "R T E" or "R.T.E." And since the "match" function is exact, you might want to try it with "R T E" or "R.T.E." instead of "RTE" Give that a try and see if help.
    "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. #26
    Senior Member
    Join Date
    Dec 2010
    Location
    NA
    Posts
    127
    Rep Power
    7

    Default

    I get what you are saying about what you see is not necessarily what the map engine sees. The only logfile I am aware of is the crash report when the app crashes. I looked quickly in the iGo folder and did not see any logfiles generated by the system. I looked quickly into the igo menus and did not see any switches to generate some. If you know any ways to generate some, you'll have to "educate" me

    As for the R T E and the R.T.E. suggestions, I included both syntax in the config_transform_tables and the dictionary.voice and simulation still said RTE.

    Yesterday, I asked for help in a French forum and someone suggested that instead of fixing iGo, he suggested that I instruct the TTS engine to modify RTE to Route. He said his TTS was reading RTE but after modifying the TTS engine RTE was then read as Route. He suspected it should not be any different on Nextgen. As you can see, he did not say clearly he did this test with iGo. He might just have use a ebook reader with a text file with RTE in it. but anyway, I think it has potential. What do you think of that?

    Personally, not the most elegant fix... ask one app to fix another app behavior but it would solve the problem. If you can't get into a house through the front door, try the back door....

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

    Default

    I am not very familiar with the Android versions of Primo/NextGen, but in the WinCE versions, you can use the "log_1="\SD Memory\nng\debug.log::5" line under the "[debug]" heading in sys.txt to get detailed log information. Obviously, you need to replace the "\SD Memory\nng" part of the path with the correct path for your device.

    There is also a "debug_tts_manager=1" item under the "[tts]" section in sys.txt to get even more detailed TTS-related info in the logs - again, at least in WinCE.

    I have used the lines to help figure out how map text is being seen by the TTS engine in the past.

    This one more line that also gives more detailed TTS-related info, but it escapes me right now. However, between the two sys.txt lines above, you should be able to get what you need (assuming they work the same in Android).

    Hope that helps. Please let me know whether or not this works in Android when you find out.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

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

    Default

    Tried "debug_tts_manager=1" item under the "[tts]" but did not see a log file inside iGo_Basar folder. If the command worked, where would the logfile be generated in your WinCe version? Meanwhile, I will read more about the sys.txt content.

    Thanks for your suggestion.

    edit: tried the line always_say_road_names=1 and 2 and 3 with zero difference in road names pronunciations. I suspect debug_tts_manager=1 & always_say_road_names=1 are ignored by NextGen
    Last edited by varso; 3rd August 2016 at 15:35.

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

    Default

    Sorry - I should have clarified - the "debug_tts_manager" line is only useful when you also have the "log_1" line. The "debug_tts_manager" option simply adds more detailed TTS info to the log file specified with the "log_1" option.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

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

    Default

    Something else I just thought of. Since it's Android, which already has a system log, Primo/Nextgen might just log things directly in the Android log. To view the Android log, open a terminal app and type "logcat" (live log). "logcat -d" will "dump" the entire log to the screen and exit. Might be worth it to check there as well....

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

 

 
Page 3 of 9 FirstFirst 12345 ... 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.