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 Wajo357 » Tue Jan 29, 2013 3:36 pm

GizmoGuy411 wrote:Single letters to be pronounced as letters when a capitalized letter is surrounded by double quotes was the suggestion made to Waze back in October 2012.

When I have not retested all the permutations, it looks like from those who have tested the letters, N, E, S, and W, that Waze has changed functionality so that upper or lower case letters surrounded by single or double quotes will now say the letter and not the cardinal direction.

I'll amend the list once I can test more permutations.


Sounds good. So now that your tests are done, here come the questions concerning Brooklyn, NY:

1) Should we change Ave N, E, W, S?
2) If yes, would you prefer single or double quotes?
3) Would that screw up navigation search if someone just enters in 1304 Ave S, Brooklyn NY, since it is now only Ave "S"? Would adding an alternate name of Ave S help?
4) Should we just blanket all of the letters in Brooklyn with the quotes specified in 2?
5) I assume we should lock the roads with the changes, correct?

Thanks!

Sincerely,
Joey
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby GizmoGuy411 » Tue Jan 29, 2013 3:30 pm

Single letters to be pronounced as letters when a capitalized letter is surrounded by double quotes was the suggestion made to Waze back in October 2012.

When I have not retested all the permutations, it looks like from those who have tested the letters, N, E, S, and W, that Waze has changed functionality so that upper or lower case letters surrounded by single or double quotes will now say the letter and not the cardinal direction.

I'll amend the list once I can test more permutations.
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 orbitc » Tue Jan 29, 2013 5:00 am

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



Just a thought: Is it possible that K comes before the st? unlike what we have here is: Avenue N.
orbitc
Master Raider
Master Raider
 
Posts: 5840
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2198 times
Been thanked: 4856 times

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

Postby Wajo357 » Mon Jan 28, 2013 5:07 pm

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


Please do. Because we need you ready for a crazy toll behavior OrbitC and I are working on.
Hint - single penalty for multiple consecutive toll segments may be wrong! I'll be starting a new thread as we do more testing soon...
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 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.
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 orbitc » Mon Jan 28, 2013 2:48 pm

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


On my test here putting single or double quotes helped.
In both situations;
Waze said: Avenue enn when I put Avenue "N" or Avenue 'N' for the Avenue "Avenue N" in NY and not Avenue north.

Maybe, it's changed?
orbitc
Master Raider
Master Raider
 
Posts: 5840
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2198 times
Been thanked: 4856 times

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

Postby Wajo357 » Mon Jan 28, 2013 2:33 pm

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


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.
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Mon Jan 28, 2013 2:31 pm

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


This was tested over the weekend, and seems to be a new functionality. You may want to retest it for yourself.
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 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.
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 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.
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

PreviousNext

Return to United States

Who is online

Users browsing this forum: stephenr1966