Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

[ img ] This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderator: MapSir

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby zheka160 » Thu Apr 27, 2017 2:27 pm

Causeway Blvd is pronounced like "Causewuh"

But if I change Blvd to St or Ave, then it pronounces then edging "way" correct
zheka160
 
Posts: 55
Joined: Tue Jun 28, 2016 4:05 pm
Location: Tampa, Sarasota, North Port, Port Charlotte
Has thanked: 29 times
Been thanked: 2 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby CCATjockey » Tue Apr 25, 2017 6:15 pm

RussPA wrote:Conshohocken (Con-sho-hocken) is now pronounced Conshilstocken or something unintelligible. Used to pronounce correctly. Road with that name here.


If it can't handle Conshohocken, what comes out for Schuylkill? :D
CCATjockey
Area Manager
Area Manager
 
Posts: 75
Joined: Tue Nov 17, 2015 5:05 am
Location: Coos Bay, OR, USA
Has thanked: 61 times
Been thanked: 23 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby RussPA » Tue Apr 25, 2017 5:37 pm

Conshohocken (Con-sho-hocken) is now pronounced Conshilstocken or something unintelligible. Used to pronounce correctly. Road with that name here.
RussPA
State Manager
State Manager
 
Posts: 1110
Joined: Fri Nov 06, 2015 9:05 pm
Location: Bucks County, Pennsylvania
Has thanked: 137 times
Been thanked: 326 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby krzycholub » Fri Apr 21, 2017 1:58 am

Per a UR in New Jersey, the pronunciation of Netcong needs to be corrected.
the pronunciation is "Net-kong", not "Net can't"

PL to UR: https://www.waze.com/editor/?env=usa&lo ... st=7352681

and PL to the segmnet with the name: https://www.waze.com/editor/?env=usa&lo ... s=32025917
krzycholub
Map Editor - level 2
Map Editor - level 2
 
Posts: 257
Joined: Mon Feb 06, 2017 5:22 pm
Location: North-West New Jersey
Has thanked: 127 times
Been thanked: 15 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby ldriveskier » Thu Apr 20, 2017 2:33 pm

Per a UR in Ohio, the pronunciation of Loudonville needs to be corrected. Here is a segment that has the name: https://www.waze.com/en-US/editor/?env=usa&lon=-81.94891&lat=40.79282&s=121634163&zoom=5&segments=38475688

UR:
Ll'nville is how it was pronounced. Proper is "Loud" with a w replacing the d, "Don" with emphasis on the d, and "ville"
ldriveskier
Map Editor - Level 4
Map Editor - Level 4
 
Posts: 156
Joined: Fri Feb 19, 2016 9:05 pm
Location: Northeast Ohio, United States
Has thanked: 298 times
Been thanked: 83 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby tcalvert317 » Wed Apr 12, 2017 10:22 am

Thanks for keeping me in the loop. I let the SCR know the TTS status.
tcalvert317
State Manager
State Manager
 
Posts: 380
Joined: Tue Jul 03, 2012 11:47 pm
Location: San Antonio, TX
Has thanked: 54 times
Been thanked: 47 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby Jakflash » Wed Apr 12, 2017 1:14 am

tcalvert317 wrote:Does anyone have a status on when the TTS will stop speaking gibberish?


From Abigail regarding the TTS issue:

We deployed a change to address this problem and also another one to force the client to request all of Jane's texts again (to avoid receiving a cached bad file).

If the issue is not fixed, it could be because the change to force the client to request Jane's texts again has failed. Then try clearing the cache.

If the issue remains after clearing cache - let your RC know. Abigail will need the logs.
Jakflash
US Waze Champs
US Waze Champs
 
Posts: 3289
Joined: Wed Oct 24, 2012 10:21 pm
Location: Edgewater, FL and Lampasas, TX
Has thanked: 178 times
Been thanked: 2542 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby sketch » Tue Apr 11, 2017 7:04 pm

Not exactly, but hopefully not long. We got a hold of staff and they are now working on it actively.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6042
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1502 times
Been thanked: 2045 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby tcalvert317 » Tue Apr 11, 2017 10:04 am

Hello,

Does anyone have a status on when the TTS will stop speaking gibberish?

Thanks,

Ted
tcalvert317
State Manager
State Manager
 
Posts: 380
Joined: Tue Jul 03, 2012 11:47 pm
Location: San Antonio, TX
Has thanked: 54 times
Been thanked: 47 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby jdeyoung » Thu Apr 06, 2017 7:12 pm

I have a couple of name pronunciations for correction:
Steger Rd https://www.waze.com/editor/?env=usa&lon=-87.52798&lat=41.46841&zoom=3&segments=14663464
Currently it is pronounced "Steeger" (long e), but the preferred one would be "Stayger"
The other references I saw for Steger were all in the same area, so there should be no conflict for regional differences.

Also, in Chicago:
Paulina https://www.waze.com/editor/?env=usa&lon=-87.66535&lat=41.73118&zoom=5&segments=15118890
This is pronounced Pauleena, but the correct way should be Pul-line-uh.
I notice there may be overlap with city names in both Oregon and Louisiana, so not sure if this is regional.
jdeyoung
 
Posts: 465
Joined: Tue Jun 07, 2011 10:04 pm
Location: Greater Chicago Metro area, NW Indiana, SW Lower MI, USA
Has thanked: 29 times
Been thanked: 194 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users