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 davidg666 » Tue Jan 29, 2013 5:08 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.

Do we have any word from Waze - or do we have any way of communicating with them - about getting TTS behaviour tweaked in general?

I ask because there's an issue that affects TTS here in Ireland - and presumably also in South Africa, where they use similarly-named roads - that could easily be resolved by making the TTS behave slightly differently.

Most major highways here are referred to with the letter 'N' and a number - for example "N4", "N81" and so on. So split divided highways might be named "N4 N" and "N4 S" on the map. However, Waze TTS always pronounces the letter 'N' as "north", so directions to turn onto one of these roads get spoken as (for example) "turn left onto north four north" instead of "turn left onto enn four north", as they should be.

Naming roads like this with quotes of any kind would look ugly and certainly wouldn't match what's seen on the road signs. I know most countries seem to use a combination of letters and digits for road designations, so it's just unfortunate that some countries happen to use letters that are also the same letters used for cardinal directions. However, if Waze TTS could pronounce letters that flow together with digits as the letters that they are, that would make a lot more sense than the current practice.

++David \ davidg666
davidg666
Waze Local Champs
Waze Local Champs
 
Posts: 604
Joined: Thu Jan 12, 2012 6:58 pm
Location: Wicklow, Ireland
Has thanked: 35 times
Been thanked: 104 times

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

Postby txemt » Tue Jan 29, 2013 4:38 pm

So, when you have 125 S Ave W E, it should read out how?
txemt
Area Manager
Area Manager
 
Posts: 4764
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby Wajo357 » Tue Jan 29, 2013 4:29 pm

jasonh300 wrote:
Wajo357 wrote: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?


What you name a street currently has no bearing on address searches. The street names we assign in WME are only for TTS and display purposes.


Perfect. I'm just trying to make sure all basis are covered before we screw anything up :)
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 jasonh300 » Tue Jan 29, 2013 4:25 pm

Wajo357 wrote: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?


What you name a street currently has no bearing on address searches. The street names we assign in WME are only for TTS and display purposes.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 403 times
Been thanked: 978 times

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

Postby orbitc » Tue Jan 29, 2013 3:50 pm

Wajo357 wrote:
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


If I may persuade GizmoGuy411, I would tink, it would be nice if all change to single quote and keep Avenue as is. For example: Avenue 'N'
orbitc
Master Raider
Master Raider
 
Posts: 5908
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2249 times
Been thanked: 4910 times

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: 1410
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 661 times
Been thanked: 433 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: 5908
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2249 times
Been thanked: 4910 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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users