Thread: Audio Problem

Try at least one street in the hundred range (ie: 105th) The changes are what I had posted earlier. In config_transforms.lua, comment out L"^%d+", which allow correct logic to be used

Code:

Please Login or Register to see the links

I never deleted any existing routines ( just commented them out between --[[ ... ]] ) The benefit of this kludge is that you don't have to manually add all entries (1st,2nd,3rd,4th...100th...) in dictionary.voice I hope I didn't break anything. For example, would it announce house address of "23 Applewood Dr" or "Route 66 Pkw" correctly? I also got a fix for "N Ave" not announcing "North Avenue"

BTW, there are lots of TTSPro features (under diMkaWAaP133 skin) that your voice file didn't activates (ie: Read Out Route Summary) which make testing easier.

Didn't have time to play with C310/C320 yet. Still got to look for a SD card (less than 4GB) to test with.

Good stuff! Nice working getting that fixed up!

What's interesting (to me, anyway), is that the Nuance voice files in WinCE are completely different (they don't even have the "roadnumber_typ_patterns" function in the config_transforms.lua file (I wanted to check to see how mine were setup in WinCE). I would have thought that the voice .lua files would have been the same since I thought that LUA is a "language" used within iGo. If so, I wonder why the .lua files are so different between WinCE and Android - I would have thought that LUA was LUA - regardless of the OS. Obviously not though! :-)

EDIT: I'm sorry - it *does* have the "roadnumber_typ_patters" function - I just missed it the first time. Interestingly, the first line is NOT commented out in WInCE. May be worth comparing the config_transforms.lua file between WinCE and Android - maybe there is another difference that causes it to work properly in CE (without commenting out that first line).

EDIT2: Actually, *some* of the WinCE Nuance voice files have that function and some don't. It seems like the TTSPro Nuance voice files have the function and the non-TTSPro Nuance voice files do not. For example, the Samantha voice does not have that function at all. But the Ira voice file does have it (but that line is NOT commented out). Come to think of it, when I tested this issue on WinCE, I tested with Samantha - not Ira. Let me test with Ira to see what happens on WinCE.

Sent from my HP SlateBook 10 x2 PC using Tapatalk

I believe Nav N Go (maker of iGO/Primo/NextGen) uses a subset of LUA. My original mod was to change dictionary.voice file for an old voice running on MyWay. Then I checked Primo with the Joe Cool voice file (probably from Mike Hunt) had the LUA routines and after playing around with it, the "digit check" need to be remove in order for the routine not to intercept and change the output. The commenting out was my fix I like to use Samantha because it has TTSPro functionalities, so I'm porting the fix over to it. Who ever originally created the function format_road_number, was thinking to handle highway with naming of <digits> or <alpha><digits> or <alpha><alpha><digits>. US highways have format of <alpha><digits> like "I-75" (so having it not pronounced "Aye" 75 th is correct) or "US 101" (pronounced "U S one hundred one") However, I don't recall any highway having just <digits>, only streets. So commenting it out should be correct.