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.

Moderator: delilush

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

Postby PesachZ » Tue Dec 16, 2014 6:29 pm

GizmoGuy411 wrote:Your help is needed!

Several reports have been received that certain roads with the "Dr" abbreviation have been voiced by TTS as "doctor" instead of "drive", and only intermittently.

In the Boston area it has happened with "Memorial Dr W" and I believe "Memorial Dr E".

In New York City it has happened with "FDR Dr N" and possibly with "FDR Dr S".

This does not seem to happen all the time.

My suspicion, is that it MAY be occurring during periods when the abbreviation "Dr" is being in heavy use by the TTS server. So if it is rush hour on the west coast and a lot of "Dr" abbreviations are being used, then it COULD also happen on the east coast at the same instant.

In order to help Waze determine the issue, we need to provide them with examples with the following infomation:

- The WME permalink with the segment that you heard the TTS for selected. (Not where you were at the time you heard it, but the segment that was being spoken in the TTS instruction.)

- Your time zone.
- A copy of the actual TTS file from your mobile device.
- The timestamp of the TTS file.

Acquiring a copy of the TTS file and its timestamp can be accomplished as follows:
- For Android devices, download the "ES File Explorer File Manager" app for your device.

- For iOS devices, download a program such as "iFunBox" (no jailbreak needed) to your Mac or Windows computer, and connect your device to your computer via a cable. You may also be able to use Wifi with some programs such as iFunBox.

- Navigate to the location in your device where the TTS files are stored.

Android:
Local/waze/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Local/waze/tts/database/local_nuamce_8_mp3_Tom_Male/

iOS:
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Tom_Male/

Once you have found the file, please either upload it to cloud space such as Dropbox or Google Drive and share the link, or just sent it to my Waze@GizmoGuy411.com email address as an attachment.
(It is not possible to sent via a Private Message.)

Heard this again today on v3.9.3.0RC
File:1418745951-821344-70.tts
downloaded 2014-12-16 11:05:52 EST
Segment: to FDR Dr S / Battery Pk
travelled/heard TTS: 2014-12-16 11:19

Debug logs sent at 2104-12-16 11:20
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Tue Dec 16, 2014 5:42 pm

russblau wrote:Is there any way to get Waze to pronounce "HOV" as individual letters instead of as "hove"?

Currenty using "H.O.V." works, but perhaps we can ask Waze to add HOV as an exception to the abbreviation list.
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Mon Dec 15, 2014 5:58 pm

SeZAKxing wrote:Any suggestions for keeping editors form changing Psge (Passage) to Page?

Communication with the editors, a [NOTE] UR might work too

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Tue Dec 09, 2014 4:45 pm

MGODLEW wrote:I discovered an issue with TTS the other day for this "Place" Magisterial District Court 11-3-07 Its official name is Eleven Three Zero Seven however waze pronounces 11-3-07 as Novermber 3rd, 2007. "Arriving Magisterial District Court Novermber 3rd, 2007"

Keep in mind that's a destination prompt which uses raw nuance. There many problems with is using raw nuance.

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Tue Dec 09, 2014 4:44 pm

MGODLEW wrote:I discovered an issue with TTS the other day for this "Place" Magisterial District Court 11-3-07 Its official name is Eleven Three Zero Seven however waze pronounces 11-3-07 as Novermber 3rd, 2007. "Arriving Magisterial District Court Novermber 3rd, 2007"

Keep in mind that's a destination prompt which uses raw nuance

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Tue Dec 09, 2014 9:21 am

GizmoGuy411 wrote:Your help is needed!

Several reports have been received that certain roads with the "Dr" abbreviation have been voiced by TTS as "doctor" instead of "drive".

In the Boston area it has happened with "Memorial Dr W" and I believe "Memorial Dr E".

In New York City it has happened with "FDR Dr N" and possibly with "FDR Dr S".

This does not seem to happen all the time.

My suspicion, is that it MAY be occurring during periods when the abbreviation "Dr" is being in heavy use by the TTS server. So if it is rush hour on the west coast and a lot of "Dr" abbreviations are being used, then it COULD also happen on the east coast at the same instant.

In order to help Waze determine the issue, we need to provide them with examples with the following infomation:

- The WME permalink with the segment that you heard the TTS for selected. (Not where you were at the time you heard it, but the segment that was being spoken in the TTS instruction.)

- Your time zone.
- A copy of the actual TTS file from your mobile device.
- The timestamp of the TTS file.

Acquiring a copy of the TTS file and its timestamp can be accomplished as follows:
- For Android devices, download the "ES File Explorer File Manager" app for your device.

- For iOS devices, download a program such as "iFunBox" (no jailbreak needed) to your Mac or Windows computer, and connect your device to your computer via a cable. You may also be able to use Wifi with some programs such as iFunBox.

- Navigate to the location in your device where the TTS files are stored.

Android:
Local/waze/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Local/waze/tts/database/local_nuamce_8_mp3_Tom_Male/

iOS:
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Tom_Male/

Once you have found the file, please either upload it to cloud space such as Dropbox or Google Drive and share the link, or just sent it to my Waze@GizmoGuy411.com email address as an attachment.
(It is not possible to sent via a Private Message.)

This happened again at a different on ramp "to FDR DR N"
TTS file from device Timestamp 2014-12-08 18:42:09 EST 1418082129-259329-32.tts
Logs submitted just after hearing it at about 2014-12-08 19:20 EST
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Sun Dec 07, 2014 3:26 am

davielde wrote:
PesachZ wrote:
miked_64 wrote:Speaking of problems with letter abbreviations - this UR in Michigan for West "AB" Ave (W AB Ave in the editor) reports that it's pronounced as West Alberta Avenue.

edited url

you may have to change the name of the segments in waze to "W 'AB' Ave", unless the street sign says something different.

If that doesn't pronounce as Alberta, won't it pronounce as "ab" and not the intended "aye bee"? Local usage is to distinguish each letter as this is used in a north to south mile grid. Kalamazoo county would also have a similar issue with "DE Ave" pronouncing as Delaware instead of "Dee Eee" (although that is not as long of a street or in as populated of an area as AB Ave). Maybe use "A B" and "D E" instead?

For now I renamed this one segment as [W A'B Ave] which I believe will work, let's see after a tile build. I imagine [W A B Ave will work as well, though I'm not sure which is worse on the eyes.

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Thu Dec 04, 2014 10:40 am

miked_64 wrote:Speaking of problems with letter abbreviations - this UR in Michigan for West "AB" Ave (W AB Ave in the editor) reports that it's pronounced as West Alberta Avenue.

edited url

you may have to change the name of the segments in waze to "W 'AB' Ave", unless the street sign says something different.
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Tue Oct 14, 2014 7:10 pm

sketch wrote:We have seen this problem before, where "N" is correctly pronounced as "north" only after certain abbreviations (e.g., St, Blvd, Ave) and after numbers (e.g., SR-135) — but after other things, like, other words (e.g., Cesar Chavez), alphanumerics ending in letters (e.g., SR-13A), and abbreviations ending in "y" (e.g., Pkwy) it does not work properly and instead says "en".

but I thought it had been fixed, what gives?
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

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

Postby PesachZ » Mon Oct 13, 2014 7:45 pm

GizmoGuy411 wrote:
Kayos_On_The_Road wrote:I found a couple of TTS errors:

"to Hwy 91A N / Annacis Island" is translated as "to highway nighty one eh en" pause "annacis island"
"to Hwy 13 / 264 St / Aldergrove" is tanslated as "to highway thirteen thousand two hundred sixty four street" followed by the pause for the second slash an "aldergrove"

These are both segments starting with "to" Could this be what is causing the issue?

Kayos


These errors have been found in several Ramp names where a combination of abbreviations that work elsewhere, do not with in ramp names where the slash mark appears.

Would you mind sending the Permalink for these examples to me directly and I will add it to our list of such examples that we will present to Waze to figure out?

Over the last week I started seeing a lot more of these N errors, did something change again? Do you want a list of PLs?

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users