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 AlanOfTheBerg » Wed Aug 22, 2012 6:50 pm

GizmoGuy411 wrote:Just confirmed a "101st St" in my area. So far so good. I'll have to add it specifically to the list.

No luck finding any "xxxrd Rd" yet that I can drive to however.

I found one in my state so far, but it's not exactly near by.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Aug 22, 2012 6:54 pm

And I kinda went near this one in Idaho a month ago...
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Thu Aug 23, 2012 4:14 pm

harling wrote:
AlanOfTheBerg wrote:I think it would still be worth it to verify things like 41st St, 141st St, and other combinations that combine "rd" and "Rd" like 33rd Rd, 63rd Rd, etc. I would figure if one or two pass, others will too.

I'm willing to bet that "33rd Rd" and "33 rd Rd" will be pronounced differently.

I would expect that as well. Because it is not formatted properly.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

Re: Strange TTS behavior

Postby AlanOfTheBerg » Thu Sep 06, 2012 6:30 pm

GizmoGuy411 wrote:jhfrontz reported to me that a street, called "Sulgrave Dr" was being pronounced "Sulgrace Dee Are" instead of "Sulgrave Drive".

I've had TTS do this to Dr before too, but then with the same segment two minutes later on a return trip, pronounced it as "drive."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Tue Sep 11, 2012 12:58 am

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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Sep 12, 2012 4:22 pm

GizmoGuy411 wrote:..."bee eye aye" ...

FYI, in my area of the country "eye" and "aye" are both pronounced the same. :lol:

Phonetic representation of that would be "eɪ" as in "say," but that makes me realize there is no real easy was to represent vowel-only sounds without resorting to "as in" or using the phonetic characters.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Oct 31, 2012 4:48 pm

I spell out "Branch" and "Bridge" because Br is a valid abbreviation for both. I've see Brg for bridge, but haven't looked at the list to see if Waze pronounces it properly. It probably does.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Oct 31, 2012 10:29 pm

harling wrote:I can tell you definitively that Brg = "bridge".

Cool. I still think "Bridge" looks better. :)
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Sun Nov 04, 2012 4:25 pm

Hospital shouldn't be abbreviated IMO.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users