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 bgodette » Fri Jan 20, 2012 11:12 pm

bmitch3020 wrote:Any automated solution is going to result in a lot of one-off or edge cases that don't work correctly. I think the best solution is to provide a TTS input under the Label input. Use the default TTS rules if no values are provided, and show the expanded value. And if "customize TTS" or some other checkbox is selected, allow the map editor to put in plain English (or their language of choice) into the TTS box. E.g.:

Label: Dr. Martin Luther King Jr. St N
TTS: Doctor Martin Luther King Junior Street North

Label: N St.
TTS: N Street

Label: Geo Wash Pkwy
TTS: George Washington Parkway

This way the label can match the sign, but the editor can fix the TTS if we see the default isn't correct.
Actually this needs to be expanded on further, what we need to know is which Open Source TTS engine is being used so we know what the TTS hinting syntax is, so we have direct control to correct regional pronunciation as well as non-English words in a predominately English environment.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3436
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby GizmoGuy411 » Sat Jan 21, 2012 12:38 am

Not at my PC at the moment, but my best guess is that the are using this based on files I've explored on my phone: http://www.nuance.com/for-business/by-p ... /index.htm

Sent from my Galaxy Nexus using Tapatalk
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1416
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 684 times
Been thanked: 453 times

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

Postby CBenson » Sat Jan 21, 2012 2:49 am

The credits for the Android Waze 2.9.99.120 says: "Text to Speech: (c) Copyright 2011 Nuance Communications, Inc."
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

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

Postby Scorp42 » Sat Jan 21, 2012 6:33 am

bmitch3020 wrote:Any automated solution is going to result in a lot of one-off or edge cases that don't work correctly. I think the best solution is to provide a TTS input under the Label input. Use the default TTS rules if no values are provided, and show the expanded value. And if "customize TTS" or some other checkbox is selected, allow the map editor to put in plain English (or their language of choice) into the TTS box. E.g.:

Label: Dr. Martin Luther King Jr. St N
TTS: Doctor Martin Luther King Junior Street North

Label: N St.
TTS: N Street

Label: Geo Wash Pkwy
TTS: George Washington Parkway

This way the label can match the sign, but the editor can fix the TTS if we see the default isn't correct.



In another life, I dealt with TTS quite a bit. The idea of a 'TTS override' field is very common.

The first field should match the street signs as closely as possible, and be visible in the UI. the TTS field should default to empty, and only be filled in if the spoken TTS is wrong or pronounces something oddly. For instance, barberton OH is pronounced like barber-ton (think haircuts) but many TTS engines will pronouns it bar-burton (with the 'Berton' part emphasized for some reason.)

Anyway, +1 for the TTS override field.

Sent from my Kindle Fire using Tapatalk
Scorp42
 
Posts: 225
Joined: Wed Dec 07, 2011 9:21 pm
Location: Southwest Florida
Has thanked: 1 time
Been thanked: 5 times

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

Postby jasonh300 » Sat Jan 21, 2012 7:09 am

Just a note: Bus, as in US Hwy 90 Bus E is being pronounced 'bus' again. I don't know when this happened, but it was working before and now it isn't.
jasonh300
 
Posts: 7568
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 408 times
Been thanked: 986 times

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

Postby dmcconachie » Sat Jan 21, 2012 10:01 am

You can find the engine being used in the preferences file. One of our users (Xteejx) located it and tried sending commands manually but it didn't even adjust for "St" as "Street". Waze is clearly intervening in the command before it is sent to the engine!
dmcconachie
 
Posts: 6119
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 106 times
Been thanked: 310 times

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

Postby harling » Sat Jan 21, 2012 2:26 pm

dmcconachie wrote:You can find the engine being used in the preferences file. One of our users (Xteejx) located it and tried sending commands manually but it didn't even adjust for "St" as "Street". Waze is clearly intervening in the command before it is sent to the engine!

That's how I heard it explained (by Ehud IIRC). The routing engine parses the street names into phrases, and passes them to the client along with the original names. When the time comes to announce a street, the client displays the un-parsed name, but sends the parsed name to the TTS engine. So, changing how Waze "reads" street names does not require a client update, as it's all done on the server side.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

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

Postby dmcconachie » Sat Jan 21, 2012 2:43 pm

Sounds like everything is there. I don't see why you wouldn't add an extra field to override the TTS. Default (grey out the field) to the street name but allow overrides!
dmcconachie
 
Posts: 6119
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 106 times
Been thanked: 310 times

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

Postby banished » Sun Jan 22, 2012 1:37 pm

bmitch3020 wrote:Label: Geo Wash Pkwy
TTS: George Washington Parkway.


Any abbreviation other than the standard N, E, W, S, St, Rd, Ave, Dr., etc., needs to include a period. For example,

Label: Dr = TTS: Drive
Label: Dr. (note the period) = TTS: doctor

Label: Geo. Wash. Pkwy = TTS: George Washington Pkwy

Rationale: "Wash" is not wholly uncommon word in street names.
banished
Waze Global Champs
Waze Global Champs
 
Posts: 793
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 239 times
Been thanked: 185 times

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

Postby AlanOfTheBerg » Sun Jan 22, 2012 2:19 pm

I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect. Not sure how they work at the end or in the middle of the name.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4823 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users