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 sketch » Mon Feb 23, 2015 9:38 pm

Thanks for your post. I had this problem too, over the weekend, in Lake Buena Vista, FL. We'll check it out. This might be the kind of thing that's universal enough to change countrywide.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5912
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1418 times
Been thanked: 1936 times

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

Postby beej666 » Mon Feb 23, 2015 7:35 pm

hi all,

one of my country managers (USA), kentsmith9, suggested i seek feedback here. i made a post at https://www.waze.com/forum/viewtopic.php?f=3&t=129244 because i'm trying to figure out the procedure for getting a TTS failure addressed.

i recently made a UR about the fact that a street named "Buena Vista Ave" has the "Buena" pronounced "Byoonah" by the TTS. the map editor who handled the UR uploaded this video demonstrating it: https://www.youtube.com/watch?v=EJ2Iw-L9__A

cheers,
marc
beej666
 
Posts: 35
Joined: Fri Nov 25, 2011 8:22 pm
Has thanked: 13 times
Been thanked: 1 time

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

Postby AlanOfTheBerg » Sun Jan 04, 2015 9:02 pm

voludu2 wrote:How responsive are they to a TTS test interface, similar to the demo nuance provides on its website?

This would allow you to input strings and listen to the results immediately.

It would make it easier for them to provide the service they want to provide.

Those who wish to dive into the app debug logs can find the url the app uses. That is what I use for immediate testing. But we will not publicize it.

Supposedly the Editor will eventually have such a feature built in.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23598
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4781 times

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

Postby PesachZ » Sun Jan 04, 2015 5:37 pm

voludu2 wrote:How responsive are they to a TTS test interface, similar to the demo nuance provides on its website?

This would allow you to input strings and listen to the results immediately.

It would make it easier for them to provide the service they want to provide.

AFAIK "fuggedaboutit"

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4387
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1990 times
Been thanked: 2223 times

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

Postby voludu2 » Sun Jan 04, 2015 5:30 pm

How responsive are they to a TTS test interface, similar to the demo nuance provides on its website?

This would allow you to input strings and listen to the results immediately.

It would make it easier for them to provide the service they want to provide.
voludu2
Map Editor - Level 5
Map Editor - Level 5
 
Posts: 2402
Joined: Thu Jul 24, 2014 12:33 pm
Location: Chester County, Pennsylvania
Has thanked: 498 times
Been thanked: 754 times

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

Postby GizmoGuy411 » Sun Jan 04, 2015 10:26 am

CBenson wrote:Do we have any current indication that waze is working to fix the bug? N is voiced "en" for this segment named "Baltimore-Washington Pkwy N / to I-95 / Baltimore" as well.


This has fallen back into my lap. Waze IS aware that a problem exists. However they are waiting for me to send specific examples.

I have somewhat narrowed the issue down to some combination of abbreviations and the slash mark.

Without out trying to narrowed the issue further, I will try to compile my findings along with theseveral recent examples and send them.

No action on abbreviations has been possible for the last few months as Waze was making changes. Just in the last couple weeks they now are ready to resume TTS issue resolutions.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1405
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby GizmoGuy411 » Sun Jan 04, 2015 10:12 am

Yes it is hard to find information in the forums when threads get this large.

The solution is to use a period. A number of places around the coutry that have "Saint" in a street name have helped us come to the conclusion that "St." is used for "Saint" and "St" is used for "Street".

You mentioned "here" without clarification. If you are referring to a specific place, it may be possible for us to get you some help to add the periods where necessary.

We may also be able to run a script to make most of the changes for the occurrences where "Saint" is the first word in the name.

Such changes based on placement however must be considered carefully however as exceptions have been discivered in the past.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1405
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby DrakeAnnDisorderly » Sun Jan 04, 2015 9:56 am

Just making a note for beating the 5 threads and a few hundred pages of posts dead horse.

So many cities begin with the word Saint here and are abbreviated as "St". So Saint Cloud or Saint Louis Park are read off as Street Cloud or "Keep right to Street Louis Park" and so very much a headache.
DrakeAnnDisorderly
 
Posts: 2
Joined: Thu Nov 13, 2014 10:44 pm
Location: Minnesota
Has thanked: 1 time
Been thanked: 1 time

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

Postby CBenson » Wed Dec 24, 2014 11:14 am

Do we have any current indication that waze is working to fix the bug? N is voiced "en" for this segment named "Baltimore-Washington Pkwy N / to I-95 / Baltimore" as well.
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 PesachZ » Tue Dec 23, 2014 6:17 pm

Kayos_On_The_Road wrote:For the last few months (I don't know exactly how long as I don't take this route often) this exit has been voiced as "to highway ninety one eh en, annacis island". Segment name is "to Hwy 91A N / Annacis Island"

https://www.waze.com/editor/?env=usa&lo ... s=59598325

and this one as "exit eleven, highway ninety one eh en, annacis island, new westminster". Segment name is "Exit 11: Hwy 91A N / Annacis Island / New Westminster"

https://www.waze.com/editor/?env=usa&lo ... s=59586780

Do these segments need to be changed to have the N voiced as "north"?

Thanks,
Kayos

No it is a bug Waze has to fix

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4387
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1990 times
Been thanked: 2223 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users