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 citeman » Tue Nov 18, 2014 10:27 pm

citeman
State Manager
State Manager
 
Posts: 699
Joined: Tue Dec 03, 2013 3:02 am
Location: Long Beach, CA
Has thanked: 852 times
Been thanked: 300 times

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

Postby e-sarge » Fri Nov 07, 2014 6:16 pm

Here's another example. It's in Canada, but this is the best thread I found for drive being mis-pronounced doctor.

https://www.waze.com/editor/?env=usa&lon=-78.91376&lat=43.88275&layers=933&zoom=8&segments=80654014

    Segment is named "Glen Hill Dr S".
    Should be pronounced "Glen Hill Drive South".
    TTS said "Glen Hill Doctor South".

Please add this to the list.
e-sarge
Area Manager
Area Manager
 
Posts: 412
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 223 times
Been thanked: 44 times

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

Postby GizmoGuy411 » Thu Oct 23, 2014 8:35 pm

jaywazin wrote:
harling wrote:'Storrow Dr E' is supposed to be "storrow drive east", not "storrow doctor east" or "storrow doctor ee". And each time someone comes up with an example that we haven't anticipated, the rules (and code) become messier and harder to maintain.

All these conditions and exceptions are easy enough for a human to follow, but to a computer, context-sensitive grammars are brittle. Trust me, I have done this for a living. Better to start now with as straightforward and literal a system as possible, or it will turn into a perpetual problem, where fixing one case will break several others.


Back to Page 2 (1/2012)!! -

Over the last couple weeks I've noticed this popping up again.

Memorial Dr W is now "Memorial Doctor West"
and Storrow Dr E is now "Storrow Doctor East"


Could not duplicate the issue with "Memorial Dr W". Suspect TTS server/routing server cliches. (A more detailed reply sent to jaywazin via PM, along with other content.)


To harlings point, the results of the exception issues are compounded when the system simply falls back to defaults, and confuses people more.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 times

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

Postby sketch » Wed Oct 22, 2014 5:40 pm

Propose we hard-code Dr. to Doctor and Dr to Drive – if I'm not mistaken, both are currently handled by Nuance default behavior.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

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

Postby jaywazin » Wed Oct 22, 2014 5:48 am

harling wrote:'Storrow Dr E' is supposed to be "storrow drive east", not "storrow doctor east" or "storrow doctor ee". And each time someone comes up with an example that we haven't anticipated, the rules (and code) become messier and harder to maintain.

All these conditions and exceptions are easy enough for a human to follow, but to a computer, context-sensitive grammars are brittle. Trust me, I have done this for a living. Better to start now with as straightforward and literal a system as possible, or it will turn into a perpetual problem, where fixing one case will break several others.


Back to Page 2 (1/2012)!! -

Over the last couple weeks I've noticed this popping up again.

Memorial Dr W is now "Memorial Doctor West"
and Storrow Dr E is now "Storrow Doctor East"
jaywazin
State Manager
State Manager
 
Posts: 276
Joined: Wed Jan 15, 2014 10:01 pm
Location: Massachusetts
Has thanked: 54 times
Been thanked: 113 times

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

Postby CBenson » Sat Oct 18, 2014 10:11 am

Yesterday, N was not voiced as "en" in this ramp name "to Baltimore-Washington Pkwy N / Baltimore / BWI Marshall Airport" found here.
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

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

Postby GizmoGuy411 » Wed Oct 15, 2014 3:53 am

It was fixed for instances where they existed as the sole abbreviation.

The combinations of abbreviations did not work.

All bets are off at the moment to what STILL works.

We will just have to submit the examples we have and see if they can figure it out.

So if you have more examples, add them here I guess and we can compile them and send them next week then that team is more accessible.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 times

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

Postby sketch » Tue Oct 14, 2014 7:35 pm

PesachZ wrote:
sketch wrote:We have seen this problem before, where "N" is correctly pronounced as "north" only after certain abbreviations (e.g., St, Blvd, Ave) and after numbers (e.g., SR-135) — but after other things, like, other words (e.g., Cesar Chavez), alphanumerics ending in letters (e.g., SR-13A), and abbreviations ending in "y" (e.g., Pkwy) it does not work properly and instead says "en".

but I thought it had been fixed, what gives?

I thought so too. Maybe it's been fixed in some cases (end of string) and not others (mid-string, e.g., before a space followed by a slash).
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

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

Postby PesachZ » Tue Oct 14, 2014 7:10 pm

sketch wrote:We have seen this problem before, where "N" is correctly pronounced as "north" only after certain abbreviations (e.g., St, Blvd, Ave) and after numbers (e.g., SR-135) — but after other things, like, other words (e.g., Cesar Chavez), alphanumerics ending in letters (e.g., SR-13A), and abbreviations ending in "y" (e.g., Pkwy) it does not work properly and instead says "en".

but I thought it had been fixed, what gives?
PesachZ
Wiki Master
Wiki Master
 
Posts: 4389
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1990 times
Been thanked: 2223 times

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

Postby sketch » Tue Oct 14, 2014 5:41 pm

We have seen this problem before, where "N" is correctly pronounced as "north" only after certain abbreviations (e.g., St, Blvd, Ave) and after numbers (e.g., SR-135) — but after other things, like, other words (e.g., Cesar Chavez), alphanumerics ending in letters (e.g., SR-13A), and abbreviations ending in "y" (e.g., Pkwy) it does not work properly and instead says "en".
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users