Home PageFacebookRSS News Feed
PocketGPS
Web
SatNav,GPS,Navigation
SurfShark VPN
Pocket GPS World - SatNavs | GPS | Speed Cameras: Forums

Pocket GPS World :: View topic - A solution for TTS pronunciation for Go models (Loquendo)
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in for private messagesLog in for private messages   Log inLog in 

A solution for TTS pronunciation for Go models (Loquendo)
Goto page 1, 2, 3 ... 15, 16, 17  Next
 
Post new topic   Reply to topic    Pocket GPS World Forum Index -> TomTom Portable Navigation Devices
View previous topic :: View next topic  
Author Message
dhn
Frequent Visitor


Joined: Oct 08, 2007
Posts: 2544
Location: Toronto CANADA

PostPosted: Mon Mar 15, 2010 6:44 pm    Post subject: A solution for TTS pronunciation for Go models (Loquendo) Reply with quote

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
Back to top
View user's profile Send private message
SpikeyMikey
Lifetime Member


Joined: Mar 21, 2006
Posts: 852
Location: Hertfordshire. Forever blowing bubbles

PostPosted: Mon Mar 15, 2010 7:20 pm    Post subject: Reply with quote

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 Smile

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
Back to top
View user's profile Send private message
AliOnHols
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Oct 15, 2008
Posts: 1933

PostPosted: Mon Mar 15, 2010 8:08 pm    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
dhn
Frequent Visitor


Joined: Oct 08, 2007
Posts: 2544
Location: Toronto CANADA

PostPosted: Mon Mar 15, 2010 9:19 pm    Post subject: Reply with quote

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! Wink
_________________
David
Back to top
View user's profile Send private message
Andy_P
Pocket GPS Moderator
Pocket GPS Moderator


Joined: Jun 04, 2005
Posts: 19991
Location: West and Southwest London

PostPosted: Mon Mar 15, 2010 10:51 pm    Post subject: Reply with quote

Quote:
To fix TTS, go to your map folder (usually "North America" or "Usa_Canada_and_Mexico") and look for the file cphoneme.dat. Rename this file cphoneme.old.

After that most of your TTS will be fine. If there are any words that are still mispronounced, you can fix them by using notepad to edit the following files:
- \LoquendoTTS\data\roadnrEnglishUS.lex (all models except the GO 720/920)
- \LoquendoTTS\EnglishUs\roadnr.EnglishUs6.8.lex (for the GO 720/920)


It looks like the equivalent file for the UK models is - \LoquendoTTS\data\SMSEnglishGb.lex (as it's the only .lex file on the machine).
But that seems only to deal with abbreviations likely to be found when reading out SMS text messages, nothing about road names etc.
Back to top
View user's profile Send private message
geddit
Occasional Visitor


Joined: Oct 05, 2007
Posts: 47

PostPosted: Fri Mar 19, 2010 7:32 pm    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
mikealder
Pocket GPS Moderator
Pocket GPS Moderator


Joined: Jan 14, 2005
Posts: 19638
Location: Blackpool , Lancs

PostPosted: Fri Mar 19, 2010 7:54 pm    Post subject: Reply with quote

geddit wrote:
Or have I missed the obvious.

Quite possibly, the file you need to re-name is in the Western_Europe map folder and is called:

cphoneme.dat

Which you rename to:

cphoneme.old

The other part of the fix doesn't seem to apply to the European based devices as the file that MVL mentioned to add/ edit phrases in simply isn't present on a European machine - Renaming the file in the map folder though will make a noticable difference - Mike
Back to top
View user's profile Send private message Send e-mail MSN Messenger
JaguarV12e
Regular Visitor


Joined: Feb 07, 2005
Posts: 171
Location: Cambridge UK

PostPosted: Fri Mar 19, 2010 8:39 pm    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
Mally1957
Lifetime Member


Joined: Sep 10, 2006
Posts: 146
Location: London

PostPosted: Fri Mar 19, 2010 9:34 pm    Post subject: Reply with quote

Quote:
Quite possibly, the file you need to re-name is in the Western_Europe map folder and is called:

cphoneme.dat

Which you rename to:

cphoneme.old


I to have renamed the file and can confirm that it does make a noticable difference.

One thing though, I assume I am right that the cphoneme file updates at every map update so will have to be renamed every time the map is updated.
_________________
Malcolm

A now retired Tomtom 940 v9.541.3145439.1 OS:1493118, GPS v1.20 Boot 5.5120, West Europe Map v1025.9386
Back to top
View user's profile Send private message
dhn
Frequent Visitor


Joined: Oct 08, 2007
Posts: 2544
Location: Toronto CANADA

PostPosted: Fri Mar 19, 2010 10:10 pm    Post subject: Reply with quote

Unless and until TT corrects the inherent problems with TTS, then yes, a rename for every new map would be in order.
_________________
David
Back to top
View user's profile Send private message
loriannod
Occasional Visitor


Joined: Sep 25, 2008
Posts: 27

PostPosted: Sun Mar 21, 2010 9:54 am    Post subject: Reply with quote

JaguarV12e wrote:

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.


Don't know about control codes but the string looks like a regular expression, as used by grep in UNIX.

http://www.regular-expressions.info/reference.html

the manual pages for the unix "tr" (translate) pages should help too.

http://unixhelp.ed.ac.uk/CGI/man-cgi?tr+1

I think you will have problems splitting the "11" and "98" into individual digits. I'm not sure if you can do that, but I have not used tr much in the last decade.


Last edited by loriannod on Sun Mar 21, 2010 11:35 am; edited 1 time in total
Back to top
View user's profile Send private message
JaguarV12e
Regular Visitor


Joined: Feb 07, 2005
Posts: 171
Location: Cambridge UK

PostPosted: Sun Mar 21, 2010 11:34 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
dhn
Frequent Visitor


Joined: Oct 08, 2007
Posts: 2544
Location: Toronto CANADA

PostPosted: Sun Mar 21, 2010 12:33 pm    Post subject: Reply with quote

I don't know whether it'll help, but take a scroll through this thread from a US based forum.
_________________
David
Back to top
View user's profile Send private message
JaguarV12e
Regular Visitor


Joined: Feb 07, 2005
Posts: 171
Location: Cambridge UK

PostPosted: Fri Apr 02, 2010 5:43 pm    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
what-are-the-chances
Occasional Visitor


Joined: Feb 27, 2006
Posts: 9

PostPosted: Sun Apr 04, 2010 5:22 pm    Post subject: Reply with quote

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 )
Back to top
View user's profile Send private message







Posted: Today    Post subject: Pocket GPS Advertising

Back to top
Display posts from previous:   
Post new topic   Reply to topic    Pocket GPS World Forum Index -> TomTom Portable Navigation Devices All times are GMT + 1 Hour
Goto page 1, 2, 3 ... 15, 16, 17  Next
Page 1 of 17

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Make a Donation



CamerAlert Database

Click here for the PocketGPSWorld.com Speed Camera Database

Download Speed Camera Database
21.094 (27 Sep 23)



WORLDWIDE SPEED CAMERA SPOTTERS WANTED!

Click here to submit camera positions to the PocketGPSWorld.com Speed Camera Database


12mth Subscriber memberships awarded every week for verified new camera reports!

Submit Speed Camera Locations Now


CamerAlert Apps



iOS QR Code






Android QR Code







Terms & Privacy


GPS Shopping