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

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

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

Postby Kandralla » Fri Sep 14, 2012 8:34 pm

GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!


Am I correct in my assumption that this means that William Penn Highway will now be called "William Penn Highway" as oppoesed to "William Pennsylvania Highway"?

If so thanks, that was annoying.
Area Manager for Pittsburgh and Erie, PA
Kandralla
 
Posts: 67
Joined: Wed Jan 18, 2012 7:15 am
Has thanked: 0 time
Been thanked: 0 time

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

Postby jemay » Sun Sep 16, 2012 5:07 am

Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks
PLEASE READ: Wiki Resources: FAQ|Map Editor|Best Practices|Editing issues?
Global Champ | Regional Coordinator for US South West - CA,NV,UT,AZ,NM,CO,HI | CM for US

Samsung Galaxy Note® 4 (SM-N910V) - Verizon - Waze Ver. 3.9.8.0
jemay
Waze Global Champs
Waze Global Champs
 
Posts: 1953
Joined: Tue Nov 09, 2010 1:26 am
Location: US South West - Lakewood, CA
Has thanked: 560 times
Been thanked: 886 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 6:08 am

jemay wrote:Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks


Unfortunately there is only one solution at the moment, and that is to rename the road [West Avenue 'n']. You could also name it [W Ave 'n'] however I would opt to be as close to however the local signage displays it.

Note that 'N' will not work, only a lower case 'n' works so far that we have found for TTS to actually pronounce the letter instead of the cardinal direction. So same holds, 'e', 's', and 'w'.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby jemay » Sun Sep 16, 2012 6:39 am

GizmoGuy411 wrote:
jemay wrote:Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks

Unfortunately there is only one solution at the moment, and that is to rename the road [West Avenue 'n']. You could also name it [W Ave 'n'] however I would opt to be as close to however the local signage displays it.

Note that 'N' will not work, only a lower case 'n' works so far that we have found for TTS to actually pronounce the letter instead of the cardinal direction. So same holds, 'e', 's', and 'w'.

Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?
PLEASE READ: Wiki Resources: FAQ|Map Editor|Best Practices|Editing issues?
Global Champ | Regional Coordinator for US South West - CA,NV,UT,AZ,NM,CO,HI | CM for US

Samsung Galaxy Note® 4 (SM-N910V) - Verizon - Waze Ver. 3.9.8.0
jemay
Waze Global Champs
Waze Global Champs
 
Posts: 1953
Joined: Tue Nov 09, 2010 1:26 am
Location: US South West - Lakewood, CA
Has thanked: 560 times
Been thanked: 886 times

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

Postby txemt » Sun Sep 16, 2012 6:51 am

jemay wrote:Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?


Let's hope it does. :)
Just wazeting my time to help you waze your route smoothly.
txemt
Area Manager
Area Manager
 
Posts: 4769
Joined: Tue Jul 17, 2012 7:03 pm
Location: Miami, Fl
Has thanked: 42 times
Been thanked: 1032 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 4:59 pm

jemay wrote:...
Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?


Yes it should, but please report back to let us know how the TTS sounds.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby loadbang » Mon Sep 17, 2012 10:52 am

AlanOfTheBerg wrote:
xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!

I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.

We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.
AM for West Midlands (UK)
Image
http://audioguy.co.uk/
loadbang
 
Posts: 249
Joined: Mon Nov 28, 2011 7:12 pm
Has thanked: 4 times
Been thanked: 2 times

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

Postby GizmoGuy411 » Tue Sep 18, 2012 6:00 am

simonhowes wrote:...
We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.


That's our motto here. "When in doubt, spell it out!"
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby Kuhlkatz » Fri Sep 21, 2012 3:56 pm

Hi,

In South Africa we use the N,R,M naming convention for major routes : N - National, M - Metropolitan and R - Regional, supposedly.

I do not always have a headset plugged in, nor have it connected to the Radio via Bluetooth. I do however always have the radio on and barely ever listen to TTS.
I recently noticed that that TTS prompts me to turn onto the 'North One North' or 'North One South' where the road designations are 'N1 North' or 'N1 South'. It's named with no spacing between the N and the 1, so I would typically assume this should be pronounced 'Enn One'.

I would assume that the English version of TTS is global and not Country specific as this is likely handled with the 'nasal twang' for US voices and the occasional 'Keep left, mate' instead of 'Keep left' for Aussie versions ;)

Is there any way we can override this behavior with other naming conventions, or how do we handle this ?
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 4.4.2, v5.11.401.10)
Image
South African Wiki Waze Wiki Map Editing
Kuhlkatz
Localizers
Localizers
 
Posts: 883
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 26 times
Been thanked: 143 times

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

Postby AlanOfTheBerg » Fri Sep 21, 2012 4:24 pm

As is mentioned in this thread and elsewhere, we have no ability to influence TTS pronunciation. We have requested a phonetic field which would help in many cases, but would not likely be able to influence accents.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.2.1 | Waze v4.2b
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23416
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4507 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users