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 CBenson » Mon Jan 28, 2013 1:53 pm

This exit has been named "Exits 13A-B-C: US-301 / MD-3 Richmond / Crofton" to match the BGS for quite some time. I drive through it regularly. TTS says: "Exits thirteen ayybeesea...youess threeohone...emdee three Richmond...Crofton." It sounds fine to me. I've never seen or heard a complaint.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Mon Jan 28, 2013 2:05 pm

Wajo357 wrote:1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Mon Jan 28, 2013 5:03 pm

Wajo357 wrote:When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.

Not that I know of. But I kind of like waze being quick about it.

orbitc wrote:Maybe, it's changed?

Maybe. I'll try it again.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Wed Jan 30, 2013 11:04 pm

So I think I can confirm that "'E' St NW" is now pronounced "ee street northwest."* Unfortunately, I tested E St and I'm finding it really difficult to hear the difference between "ee" and "east." I'll try 'N' now.

* Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington." I don't recall actually having heard "en double you" when reaching my destination. I wonder why this file is there.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Wed Jan 30, 2013 11:14 pm

My gut reaction is just to change E, N, S and W. My vote would be to use the capital letter inside single quotes, but GizmoGuy stated that the recommendation to waze was to use double quotes. I don't remember (if I ever knew) why the preference for double quotes.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Thu Jan 31, 2013 11:42 am

CBenson wrote:Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington."

OK, I can confirm that the sound file is used as the destination location if you select your destination by press and holding the location on the map. If you search for a destination, the announced destination location appears to be the search result you select. However, if you press and hold to give the destination, waze creates the destination location announcement. However, as waze gives the street name anyway this is redundant.
So if I press and hold to route to a location on F St NW, when I get there waze says: "You have reached your destination eff street en double you Washington at eff street northwest." Sometimes if waze determines the street number it seems to include the number: "You have reached your destination 601 eff street en double you Washington at eff street northwest."
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Fri Feb 01, 2013 7:40 pm

sketch wrote:it should be "Exit" rather than "Exits", if that's what the big green sign says

Just to clarify, you are saying it should be what the big green sign says, correct?
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Fri Feb 01, 2013 8:19 pm

CBenson wrote:So I think I can confirm that "'E' St NW" is now pronounced "ee street northwest."* Unfortunately, I tested E St and I'm finding it really difficult to hear the difference between "ee" and "east." I'll try 'N' now.

"'N' St SW" is pronounced "en street northwest" in the turn instructions.
I'm planing to change E, N, S and W street to include the single quotes.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Fri Feb 08, 2013 8:00 am

So I just came across the first UR that I have seen that objects to the spelling of an abbreviation. The UR states: "xing is not how you spell crossing!'" The TTS here does speak "xing" as "crossing." So this objection is purely a display objection. Should we not use the abbreviation "xing" if users (or at least one user) objects to the spelling but the TTS is correct?
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

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

Postby CBenson » Fri Feb 08, 2013 2:42 pm

orbitc wrote:Also, Colony Crossing is an actual street name, therefore, it should be Colony Crossing.

Its not Colony Crossing Street

I think of "Colony" as the name and "Crossing" as the road type.
Thus:
Colony Street - Colony St
Colony Drive - Colony Dr
Colony Boulevard - Colony Blvd
Colony Avenue - Colony Ave
Colony Road - Colony Rd
Colony Crossing - Colony Xing

I
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1811 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users