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 bmitch3020 » Mon Jan 23, 2012 7:15 pm

banished wrote:
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.


I picked Geo Wash Pkwy on purpose because it's such a bad example. Trying to code the TTS for every situation like this would be a mistake. Like I said, we need a TTS override field where we can enter what is said, and still allow us to match the labels to the BGS.

(Sorry for not keeping up with the conversation, it seems that forum notifications are among the list of things that are breaking lately.)
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

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

Postby GizmoGuy411 » Mon Jan 23, 2012 5:02 am

Less is better is also my opinion.. However for the purposes of this list more is better to learn how the TTS works. Then we can make our suggestions to Waze including everything we think that should be pruned.

Also looked into Nuance some more and found their product called Vocalizer that specifically included our two voice choices; Samantha, and Tom.

Interestingly Waze x.120 has voice files that include a canned set of English and Hebrew prompts? Many that I have never heard before.

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

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

Postby AlanOfTheBerg » Mon Jan 23, 2012 1:32 am

banished wrote:
AlanOfTheBerg wrote:I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect.


Yes, I meant to include those. But other than a very small set of abbreviations, such as those, it makes sense to put a period after words not contained in that set, e.g., "Dr." for doctor and "Dr" for drive; "Wash." for Washington, and "wash" (no period) for wash, as in Wash Ave.

I feel, as mapcat noted, that we should not be going hog wild on things like Wash. vs Wash and Geo vs. George. The smaller set of abbreviations, the better. If it's Wash, it's always Wash, otherwise spell out Washington if that's what it is.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23590
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4773 times

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

Postby banished » Mon Jan 23, 2012 1:16 am

AlanOfTheBerg wrote:I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect.


Yes, I meant to include those. But other than a very small set of abbreviations, such as those, it makes sense to put a period after words not contained in that set, e.g., "Dr." for doctor and "Dr" for drive; "Wash." for Washington, and "wash" (no period) for wash, as in Wash Ave.
banished
Waze Global Champs
Waze Global Champs
 
Posts: 776
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 217 times
Been thanked: 163 times

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

Postby mapcat » Sun Jan 22, 2012 3:42 pm

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


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

Rationale: "Wash" is not wholly uncommon word in street names.

In cases such as this it makes much more sense to change the street name, IMO. If we acknowledge that some street names can be shortened, and not just commonly abbreviated prefixes/suffixes/directionals, we'd only over-complicate things, with little upside.
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 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: 23590
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4773 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: 776
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 217 times
Been thanked: 163 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: 6117
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 106 times
Been thanked: 309 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 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: 6117
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 106 times
Been thanked: 309 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users