A solution for TTS pronunciation for Go models (Loquendo)

[SpikeyMikey]

[JaguarV12e]

[notones]

Now on UK ROI v850.2781
No problems so far, seemed the easiest fix (for me at least) as i never travel outside of UK

[MARViN2003]

I guess the encoding of the data is different for W&CE and UK&RoI; probably includes the country somehow, but this muchs up the rules.

[Greenglide]

With a Go 520 (went through the pain of the stuttering!) and GB and Ireland map my Loquendo folder does not have a \data folder to put the files from the zip file in - am I missing something.

It has a \bin, \EnglishGb, \EnglishTE and \lib folders.

The \EnglishGb folder contains .lex files but no .rex file. It does have a roadnr.EnglishGb6.7.lex, sms.EnglishGb6.9.lex, EnglishGb6.9.lex and a EnglishGb6.9.phd file.

The daft road numbers have driven me mad for years. Can I use this fix?

[MARViN2003]

Ahh, you have Loquendo 6.9 rather than 7.
I updated mine to 7 when I had the stuttering issue.

You can try it, but I have no idea if it will work. It may be worth looking through the stuttering thread to find the 7.0 files and install them...

[Greenglide]

Upgraded Loquendo to V7 (which doesnt seem any different from 6.9!) and, loh and behold, the files to drop in the \data folder (which now exist) work like a dream!

It really is staggering that TomTom are incapable of understanding the way road numbering in UK (and USA?) works. Does any country actually use the equivalent of "A four thousand six hundred and seventy three" as road numbers?

Truly impressed, thanks MARViN2003 you have my undying gratitude.

Do current production TT units produce this c**p? My 520 will not last forever (although I have just installed a new battery in it go give it another couple of years). Clearly I dont want to purchase a replacement that has the same problems.

Having said that I have a Nokia 5800 with OVI maps and a Nexus One with NDrive installed and dont use the TomTom unit that much these days (much less business mileage) but the TMC traffic data is useful as it does cost.

[MARViN2003]

Glad it works,

The 520 is a good unit, I only updated mine recently because I fried the usb power circuit

Also because you are using the UK & RoI maps, you shouldn't get any of the comma, semicolon and other extra pronunciation problems that we seem to have on the euro maps.

I have a 930 referb from tomtom, which still has the mp3 player and fm transmitter and also a bluetooth remote control.

The newer models do still use Loquendo 7 as far as I know, so will still have the same problems...

[MARViN2003]

Does anyone know where the road numbers and names actually come from?
It would be nice to try and find the diference in the encoding of the UK and Euro maps, then I could work out some new rules for the euro maps that would eliminate the extra pronunciation problems...

I asked Tomtom, but they were unhelpful:

[Greenglide]

Hmm -I assume the road numbers and names are in cname.dat in the map folder with cline.dat and cnode.dat being the actual layout.

All these files are obviously compressed so unless it is a standard compression this will not be easy

What I dont understand is that interface between the TomTom data being read from the map and the Loquendo software must be consistent. If the GB and NI and the Western Europe maps are installed on the same unit the TTS must be able to handle both of them.

Presumably the Western Europe map must be using Loquendo functionality that GB and NI do not. Accented characters, driving on the right, kilometres and general use of foreign languages?

Presumably if it can be made to function correctly with Western Europe maps then this should also work with GB and NI?

[MRCC]

Hi MARViN2003

Thanks for the good work you've been putting in to this.

One problem I noticed though: I just updated the 5 files again and now M621 is pronounced "M six hundred and twenty one" whereas with a previous download (3-7-10) it is read as "M six two one".

The roadnrEnglishGB.rex file was 871bytes but now is only 336bytes.

[layingback]

[Greenglide]

Renaming cphoneme.dat hasnt made an beneficial difference tothe speech (it still pronounces "Fisher Lane" as "Fish Lane" and has a strange rolling "r" on most places with a name ending with "er" - Manchester being one of them).

Presumably the fix for road numbers still works with cphoneme.dat in use?

MARViN2003's files seem to cause it to omit certain road names or the "towards xxx" after the road number. I assume TT is feeding Loquendo with data it cannot make sense of? The map seems to freeze for a few seconds when this happens.

When I get back from my holidays I will have a play!

Earlier in the thread there was a question about how UK road numbers should be pronounced. According to our local highways department A123 as "A one twenty three" and four digit numbers are split into two groups of two so A1058 is "A ten fifty eight" but I think that is a bit picky and there areexceptions when the third digit is a zero!

[MARViN2003]

Before I renamed cphoneme.dat my 930 decided it wouldn't read out any B road numbers for some reason...

[Greenglide]

I have put the line "LogFile" = "/mnt/sdcard/LoquendoTTS/log.txt" in the default7.session file and commented out the "LogFile" = "stderr" line but there is no sign of a log file anywhere!

Have searched the file system in both the internal memory and the SD card - no sign

I put the same entry in the default.session left over from v6.9 but that didnt help.

Meanwhile is TT using TeleAtlas and NavTech SAMPA phonetic alphabet as mentioned in the Loquendo site? If that is fed to Loquendo it may be the reason for the oddities with maps other that GB and Ireland?

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!