A solution for TTS pronunciation for Go models (Loquendo)

[dhn]

Courtesy of a supermoderator at tomtomforums in the States is a solution for the poor pronounciation of Loquendo computer voices.

See here

Reference in the link is made for US or NA maps and US voices but I suspect alternation of the equivalent EU voices would work as well. Mods here can probably help you with which files to deal with.
_________________
David

[SpikeyMikey]

Thanks.

I've renamed the file cphoneme.dat in the map folder as suggested and first impressions are good.

We've now got a High Street as opposed to a High Strit

Time will tell how much of a difference it will make, but I'm impressed.
_________________
Mike
TT GO6000 (Europe); iPhone and iPad Pro with iOS TT GO & MyDrive + CamerAlert

[AliOnHols]

Thanks for the link David and to MVL too.
_________________
Garmin Nuvi 2599
Android with CamerAlert, OsmAnd+, Waze & TT Europe.
TomTom GO 730, GO 930, GO 940 & Rider2.
SatMap Active 10 & 20.

[dhn]

Mvl has stated that he'll be adding more information to the thread later tonight (here in the Eastern time zone in NA) so you may want to check back for more stuff.......but you don't need to stay up to the wee hours in the UK, guys!
_________________
David

[Andy_P]

[geddit]

This thread seemed a wonderful idea, particularly the...

"Highway numbers were pronounced as "one hundred and twenty-four" instead of "one two four". The above link also describes what needs to be done to correct this one too."

Unfortunately, on my UK GO630 I cannot find any of the stated files in the Loquendo folder. Is there a fundamental difference between UK and US Navcore versions? Or have I missed the obvious.

Geddit

[mikealder]

[JaguarV12e]

On my 730 off the Loquendo directory there is a file called EnglishGbTT.rex, and it has rules for manipulating spoken strings.

I have spent a while playing with it, but it is not as simple as it looks.

adding a line like:
"(^|[ \t]+)A[ \-]*([0-9][0-9]?)([0-9][0-9])[^0-9]?" = "\1 Eh \2 \3 "
changes "A One Thousand One Hundred and Ninety Eight"
to "A Eleven Ninety Eight Semicolon" (or a trailing "comma" if the road has a secondary name).

I am sure that this can be fixed, but the difficulty is that I have found no reference to the syntax that the file is operating on, and only have the examples in the file for guidance.

I have deduced that the problem is that because the "A" in the original string is pronounced "Eh", there must be some (invisible) control character that is putting the TTS in a mode where it spells out each letter (or punctuation mark) and I don't know which contorol character puts TTS back into normal mode to finish the string.
_________________
Tomtom Go 1005
Tomtom Go 730T

[Mally1957]

[dhn]

Unless and until TT corrects the inherent problems with TTS, then yes, a rename for every new map would be in order.
_________________
David

[loriannod]

[JaguarV12e]

The problem is not in the string manipulation, it is that I don't know the contents of the string that is being manipulated (the control characters are not spoken), and I cant use brute force to get it to say the right thing without more knowledge of the TTS syntax.

I can suppress the comma or semicolon, but then (because the TTS is apparently in the wrong mode), any following text is spelled out. For example: A1198, Old North Road is pronounced "Eh Eleven Ninely Eight Comma Old North Road" if I suppress the comma in the string, it is then pronounced "Eh Eleven Ninety Eight Oh Ell Dee North Road". If I just knew the control character to force it back into normal speech mode, I think the rest is easy.
_________________
Tomtom Go 1005
Tomtom Go 730T

[dhn]

I don't know whether it'll help, but take a scroll through this thread from a US based forum.
_________________
David

[JaguarV12e]

Back to the original "fix" of this thread...

Don't try it if you intend to travel to France (or maybe any other foreign country). The standard pronunciation of French names by UK Tomtom is a bit weird, but without cphoneme.dat, it is positively comical, and a large proportion of french words become totally unintelligible.
_________________
Tomtom Go 1005
Tomtom Go 730T

[what-are-the-chances]

Hi, was looking at this thread and on checking my current Loquendo folder i could not (as already reported) find the relevant file(s)
\LoquendoTTS\data\roadnrEnglishUS.lex
However on checking my original complete back up for my GO520 (which i haven't looked at for a long time) i noticed that the equivalent UK file was in there, 'roadnr.EnglishGb6.7.lex' as well as 3 other lex files.
'roadnrAUS.EnglishGb6.7.lex', 'EnglishGb6.9.lex'and 'sms.EnglishGb6.9.lex'. They are all located in \loquendoTTS\EnglishGb\

The reason that they are no longer part of my TTS structure (and maybe others) is that during the infamous 'stuttering' period one of the fixes was to change to Loquendo v7 Kate and then Navcore 8.2xx. This fixed the stuttering for me, but these extra files were not part of the 'Loqeundo v7 Kate' that i installed. This implies (to me anyway) that it is not necessarily a US/UK device difference because these files were once part of our set up.

I don't really know if this info will be of any use in making further progress with this issue but i thought i would share it just in case.

Cheers
_________________
Tom Tom Go 520 - Map UK ROI 815.2003 Navcore_8.203.9717.go40 - ( Loquendo TTS7 )

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!