Home PageFacebookRSS News Feed
PocketGPS
Web
SatNav,GPS,Navigation
SurfShark VPN for Streaming TV
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 Previous  1, 2, 3 ... 9, 10, 11 ... 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
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Sun Sep 05, 2010 5:53 pm    Post subject: Reply with quote
trooper wrote:
Greenglide wrote:
By appending the contents of one of the .rex files given earlier to this thread the numbers come out correctly without losing anything such as the SMS abbreviations.

Could you post a link to the .rex file you used?


Code:
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4 \5 \6 \pause=120 \spell=no \8"
"(^|[ \t]+)([A|B])[ \-]*([1-9])0([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 oh \Nx \4 \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])0([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4 oh \Nx \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4 \5 oh \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])0([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 oh \4 oh \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])00([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4_ oh, oh \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])00([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3_ oh, oh \4 \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])000([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 thousand \pause=120 \spell=no \5"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4 \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])0([1-9])([;:,\.]?)($|[ \t]+)"= "\1 \s \2 \3 oh \4 \pause=120 \spell=no \6"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4 oh \pause=120 \spell=no \6"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])00([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 hundred \pause=120 \spell=no \5"


This is the content I am currently using - you can copy and paste the contents of the box - highlight all of the text in the box, control+c to copy and then ctrl+v to paste it wherever you want it.

Alternatively this is MARVIN2003's version

Code:
"(^|[ \t]+)([A|B])[ \-]*([1-9])([0-9])([0-9])([0-9])?([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \Nx \3 \4 \Nx \5 \6 \pause=120 \spell=no \8 "
"(^|[ \t]+)([A|B|M])[ \-]*([1-9][0-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \Nr \3 \pause=120 \spell=no \5"
"(^|[ \t]+)([A|B|M])[ \-]*([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \pause=120 \spell=no \5 "


The original version which involves several files is located here http://www.darklight.info/downloads/Loq7fix.zip

Good luck!
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
Back to top
View user's profile Send private message
trooper
Occasional Visitor


Joined: May 01, 2005
Posts: 37
PostPosted: Sun Sep 05, 2010 5:57 pm    Post subject: Reply with quote
Thanks, I'll give it a try.
Back to top
View user's profile Send private message
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Sun Sep 05, 2010 8:56 pm    Post subject: Reply with quote
Just had a try with the .rex file and found a few errors where "one seven" was read as "seventeen" etc when there was a digit before it.

I have inserted \Nx parameters to correct this.

Two consecutive zeros are still pronounced with a slight hesitation espacially with number like 1200, 1002 doesnt seem as bad.

I think the "oh, oh" (used to stop it running the two words into one) needs replacing by phonetics or maybe "oh owe", "owe owe" or "owe oh". I may try that during the week.

The inserts in the .rex file is now:-

Code:
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \Nx \3 \4 \Nx \5 \6 \pause=120 \spell=no \8"
"(^|[ \t]+)([A|B])[ \-]*([1-9])0([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 oh \Nx \4 \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])0([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \Nx \3 \4 oh \Nx \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \Nx \4 \5 oh \pause=120 \spell=no \7"
"(^|[ \t]+)([A|B])[ \-]*([1-9])0([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 oh \4 oh \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])([1-9])00([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \4_ oh, oh \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])00([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3_ oh, oh \4 \pause=120 \spell=no \6"
"(^|[ \t]+)([A|B])[ \-]*([1-9])000([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 thousand \pause=120 \spell=no \5"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])([1-9])([1-9])([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \Nx \4 \5 \pause=120 \spell=no \7"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])0([1-9])([;:,\.]?)($|[ \t]+)"= "\1 \s \2 \3 oh \4 \pause=120 \spell=no \6"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])([1-9])0([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 \Nx \4 oh \pause=120 \spell=no \6"
"(^|[ \t]+)([M|A|B])[ \-]*([1-9])00([;:,\.]?)($|[ \t]+)" = "\1 \s \2 \3 hundred \pause=120 \spell=no \5"


The advantage of this technique is that it is only used for GB English so it shouldnt mess up any other languages (hopefully)
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
Back to top
View user's profile Send private message
trooper
Occasional Visitor


Joined: May 01, 2005
Posts: 37
PostPosted: Mon Sep 06, 2010 10:03 am    Post subject: Reply with quote
Tried this latest fix on my 930 running WC&E maps but sadly didn't work.
Keep up the good work and hopefully you'll get a fix that works on all versions.
Back to top
View user's profile Send private message
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Mon Sep 06, 2010 1:10 pm    Post subject: Reply with quote
trooper wrote:
Tried this latest fix on my 930 running WC&E maps but sadly didn't work.
Keep up the good work and hopefully you'll get a fix that works on all versions.


So what doesnt work? Is it punctuation being read out (comma, semi-colon etc)?

Were you using the small number of rules or MARVIN2003's version with the smaller number?

The WC&E maps do give problems and I don't think anyone has cracked the issue yet. Logically the contents of the EnglishGbTT.rex file and the trace facility "should" enable this to be fixed. I dont have the WC&E map Sad
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
Back to top
View user's profile Send private message
MARViN2003
Regular Visitor


Joined: Nov 27, 2005
Posts: 132
Location: Stroud, Gloucestershire
PostPosted: Mon Sep 06, 2010 4:51 pm    Post subject: Reply with quote
I'm testing the EnglishGbTT.rex file fix on the W&CE map...
Back to top
View user's profile Send private message Visit poster's website
trooper
Occasional Visitor


Joined: May 01, 2005
Posts: 37
PostPosted: Mon Sep 06, 2010 11:43 pm    Post subject: Reply with quote
Replaced the .rex file with the full version and extra code appended to the end. It did not make the slightest change to how it pronounced the road numbers. Stiill e.g. 'two hundred and three' or 'three thousand and thirty seven'.
Would it matter where the extra code was placed?
Back to top
View user's profile Send private message
MARViN2003
Regular Visitor


Joined: Nov 27, 2005
Posts: 132
Location: Stroud, Gloucestershire
PostPosted: Tue Sep 07, 2010 10:16 am    Post subject: Reply with quote
First of all, these rules will only work with Loquendo 7.

If you add the new rules to the end of the EnglishGbTT.rex file, you should not need any of the other files, as this file gets read by default, as long as you are using a UK English voice.

Note: This file also includes a rule that replaces 0 0 with nil nil which you may need to remove for some road numbers.

Putting the code in this file does seem to stop the 'semi-colon' and 'comma' problems, although I have only given it a quick test.

It still seems to ignore the rules for B roads though on the W&CE map.
Back to top
View user's profile Send private message Visit poster's website
trooper
Occasional Visitor


Joined: May 01, 2005
Posts: 37
PostPosted: Tue Sep 07, 2010 10:33 am    Post subject: Reply with quote
I am using Loquendo V7. I'm not sure what the 'semi-colon' and 'comma' problems are. However it does not read the road numbers, on the short test, I did any differently.
If the original .rex file is where it gets the numbers information from then surely where the new code is placed in the file becomes important - or have I got that wrong?
Back to top
View user's profile Send private message
Pocketgps
Lifetime Member


Joined: Nov 16, 2004
Posts: 2145
Location: Midlands, UK
PostPosted: Tue Sep 07, 2010 12:12 pm    Post subject: Reply with quote
I have just tried MARViN2003's files on my Go530 using UK & ROI v8.55 maps.

It reads out the A roads okay as well as the M roads, but I get no B roads, just says the road name and no B or numbers. Is this correct Question

eg
'A1234 london road' are okay
'M6' okay

'B1234 london road' - says 'london road' only - no B or numbers read out.
Back to top
View user's profile Send private message
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Tue Sep 07, 2010 3:04 pm    Post subject: Reply with quote
Pocketgps wrote:
I have just tried MARViN2003's files on my Go530 using UK & ROI v8.55 maps.

It reads out the A roads okay as well as the M roads, but I get no B roads, just says the road name and no B or numbers. Is this correct Question

eg
'A1234 london road' are okay
'M6' okay

'B1234 london road' - says 'london road' only - no B or numbers read out.


Is this with the extra lines appended to the EnglishGbTT.rex file leaving all the previous lines present?

I have the larger set on my previous posting in the EnglishGbTT.rex file on my 540 with version 855 maps and it works fine on motorways, A roads and B roads.

I will try it on my 520 with version 855 maps tonight to check if it works on that (it has Loquendo version 7 installed).

I am using the cphoneme.dat file in the map - renaming it did not give any improvement to pronunciation that I noticed. Could this be the problem? Otherwise, you havent got MARVIN2003s other files installed as well have you?
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
Back to top
View user's profile Send private message
Pocketgps
Lifetime Member


Joined: Nov 16, 2004
Posts: 2145
Location: Midlands, UK
PostPosted: Tue Sep 07, 2010 6:15 pm    Post subject: Reply with quote
Greenglide wrote:

1. Is this with the extra lines appended to the EnglishGbTT.rex file leaving all the previous lines present?

2. I will try it on my 520 with version 855 maps tonight to check if it works on that (it has Loquendo version 7 installed).

3. I am using the cphoneme.dat file in the map - renaming it did not give any improvement to pronunciation that I noticed. Could this be the problem?

4. Otherwise, you havent got MARVIN2003s other files installed as well have you?


1. No, will try that
2. Loquendo version 7 is installed
3. I am using the cphoneme.dat file
4. I installed the 5 files that are in the zip file - is this wrong then ?
Back to top
View user's profile Send private message
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Tue Sep 07, 2010 8:01 pm    Post subject: Reply with quote
Pocketgps wrote:
Greenglide wrote:

1. Is this with the extra lines appended to the EnglishGbTT.rex file leaving all the previous lines present?

2. I will try it on my 520 with version 855 maps tonight to check if it works on that (it has Loquendo version 7 installed).

3. I am using the cphoneme.dat file in the map - renaming it did not give any improvement to pronunciation that I noticed. Could this be the problem?

4. Otherwise, you havent got MARVIN2003s other files installed as well have you?


1. No, will try that
2. Loquendo version 7 is installed
3. I am using the cphoneme.dat file
4. I installed the 5 files that are in the zip file - is this wrong then ?


You either place MARVIN2003s files in the \loquendo\data folder or you append the additional lines (either the 10 or so lines to read "0" as "oh" rather than zero or the smaller set in MARVIN2003s zip file).
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
Back to top
View user's profile Send private message
Greenglide
Lifetime Member


Joined: Apr 04, 2006
Posts: 295
Location: South East Northumberland, UK
PostPosted: Tue Sep 07, 2010 8:55 pm    Post subject: Reply with quote
Greenglide wrote:

I will try it on my 520 with version 855 maps tonight to check if it works on that (it has Loquendo version 7 installed).


Appended the set of rules that read "oh" rather than zero (the larger one) on my 520T with 855 maps and it works fine.

It works with B roads and correctly identifies double 0 despite the condition earlier in the existing file.

I can see no reason why it should work on a 520 with a version of Loquendo v7 from an x30 device and a 540 both with UK & Ireland map 855 but not work on a x30 device.

Might be worth checking installation and if desperate using the trace facilty but that is excedingly verbose!

I think I am happy to live with the solution so far though.
_________________
TomTom Go 540 - V9.058, Map GB & Ireland 860.3101
TomTom Go 520T, V8.351, TTS V7, Map GB & Ireland 855.2884
Nokia 5800 with Google Maps & OVI Maps
Google Nexus One with Google Maps & NDrive
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: Wed Sep 08, 2010 6:24 pm    Post subject: Reply with quote
With a bit of trepidation I've removed the five files from the DATA folder and edited the EnglishGbTT.rex file by adding the larger set of rules posted by Greenglide.

I've done a desktop demo and the punctuation errors appear to be gone, and the B4009 close by was pronounced as "B four oh oh nine" although a bit jittery.

I'm back to driving up the "High Strit" instead of street though, although this may not be due to the recent changes, it's just that maybe I haven't done something when upgrading to the latest map!
_________________
Mike
TT GO6000 (Europe); iPhone and iPad Pro with iOS TT GO & MyDrive + CamerAlert
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 Previous  1, 2, 3 ... 9, 10, 11 ... 15, 16, 17  Next
Page 10 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
22.044 (24 Apr 24)


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