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.

Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Postby GizmoGuy411 » Wed Jan 18, 2012 7:07 pm

[Please note that this lead post is edited periodically to reflect updated information, with any changes highlighted in the color of the date that follows:]

Post edit history:
2014-08-24 The Big List is now maintained entirely as a Google document and it no longer sourced from an Excel file.
2014-08-16 Every entry in the Big List has now finally been tested. A number of new entries also added.
2014-03-06 Column added to List to differentiate ROUTING TTS from DESTINATION TTS results.
2013-09-16 Minor rewrites of various paragraphs.
2012-10-31
2012-09-24
2012-09-06
2012-08-20
(earlier post edit history not maintained)



This is a list of abbreviations and acronyms that are being added to two sandbox test rigs, to be tested in the Waze clients to learn their TTS output results for North America. (Jenncard maintained a second test rig.)

All tests are with the Nuance female "Samantha" voice only as used in North America. While we expect that the other English voice choice for NA, "Tom", is likely to use the same TTS databases, we have not tested for it.

The list includes all the official and alternate abbreviations of the United States Postal Service, all the English abbreviations for Canada Post, a subset of the French abbreviations for Canada Post, a subset from the U.S. Federal Manual on Uniform Traffic Control Devices plus a number of others suggested by Waze users. (Additional abbreviations from the MUCCD for individual U.S. States and from any equivalent list for Canadian Provinces, have not yet been compiled.)

Official abbreviation list sources for specific states or providences are linked from their respective names in the test list.

If you already know or learn any TTS results, please post them here. Please submit only results that you are absolutely sure of, with the exact spelling (including any capitalization) of the abbreviation, and the confirmed TTS output result.

Also submit any additional abbreviations that you feel should be part of the list for testing and/or for future inclusion in the TTS system.

Some current abbreviations such as "Penn" (which generates "Pennsylvania") should probably be removed from the TTS system in favor of using the capitalized two letter State and Province abbreviation standards. We should also discuss others for consideration that may need to be removed from the TTS.

To hear the most current TTS results from your Waze client device, it may be necessary to clear your current TTS cache. Enter "cc@tts" without quotes in the Navigation search to clear the cache. Waze should reply with a "TTS cache has been cleared!" popup box. Then wait for "Searching ..." to end.

This list will be updated periodically. (The initial list was submitted 2012-01-18, which took a month for Waze to process, and for us to test in the Waze Clients.)

Once we learn what the TTS currently knows, we can add the results of this list to the Wiki, plus
we can use it to submit our requested TTS "wishlist" changes to Waze. Please note that entries in this are for testing purposes and do NOT automatically imply that we endorse them. This list is primarily to research as many possible abbreviations that we can test to learn what Waze currently recognizes or not.

To learn how to hear the TTS files on your Android device manually, read the side notes in the following post: viewtopic.php?f=10&t=15178&p=144296#p144296

A section on Abbreviations has been added to the Waze Wiki. The link below takes you to a selection of countries. Select your country from the list and follow the links to the abbreviations in your country:
Editing Manual > How to label and name roads (by country)

In the United States you can go directly to the US Abbreviations and acronyms list.

Google Drive Spreadsheet:
Text-to-Speech (TTS) Abbreviations in Waze Clients - Test List for North America aka the "Big List" or the "Big TTS Test List".

Last edited by GizmoGuy411 on Wed May 09, 2012 6:42 pm, edited 32 times in total.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Wed Jan 18, 2012 11:12 pm

CBenson:
Excellent points CBenson. Some of the words you mentioned were already in the list I believe, however I'll be sure to add the ones you mentioned. At the Palo Alto Meet-Up there was discussion about many of the issues you mentioned. We did kick around the idea of using "St." for "Saint" and "St" for "Street" as you mentioned. I'll be sure to add "St." The list does have NE. NW, SE, & SW to see what they generate, but I forgot about the issue of differentiating roads named with a letter such as "E" from "east" as the current "E" abbreviation currently says. Since there are fewer roads named with a letter than roads that include a direction, we will have to think of a way to make them different. Maybe with quotes? Anyone else have ideas here?

I suppose I should test every letter of the alphabet to see what they say. N, E, S, & W may not be the only ones that produce a word.

mapcat:
Your welcome... altough I don't think I got any points for making that list did I? :)

AlanOfTheBurg:
Actually Alan, the list was to be multipurposed. Intially to learn what abbreviations the TTS already knows, and secondly to be a basis for creating our TTS "wishlist" for Waze. I'll see if I can make that clearer in the lead post. Thanks.

jason300
Thanks Jason.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Thu Jan 19, 2012 12:08 am

gettingthere wrote:... We'll need to add a bunch of Spanish abbreviations since there are loads of streets in many states where the street name is in Spanish. ...


Geez, I wonder who we could ask that might know those!
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Thu Jan 19, 2012 6:19 am

Timbones wrote:Does TTS not say "saint" when St is at the beginning, and "street" when it is at the end? This is how I'd expect it to work...

via TapaTalk


According to this post, it may not work that way:
leungjf wrote:Hello, all

I've come upon a peculiar problem in my area - St. Louis, MO.

I recently updated some of the entrance ramps to I-64 in the area to incorporate the control city per the Wiki. For example, "To I-64 E" became "To I-64 E St. Louis".

The changes finally went live with the last map update, and then I noticed the problem:

The abbreviation I used for "St. Louis" - "St." - is also the abbreviation for "Street" and the client's TTS is saying it as "I-64 East Street Louis". I haven't seen any postings with this problem (and please forgive me if there have been - still a bit new at this AM thing).
...

[Original post: viewtopic.php?f=10&t=15041]
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Thu Jan 19, 2012 7:27 am

I've added everyone's suggestions to the list, however I have not added anything to my sandbox yet. (Nor have I achieved any editing points in the last day! :( )

Among the items added were:
Doctor = Dr.
Junior = Jr.
Saint = St.

Following that convention I've also added the following for the time being:
C (cee) = C.
E (ee) = E.
N (en) = N.
S (ess) = S.
W (double-u) = W.

Additionally all the state and province abbreviations were added.

A link at the bottom of the spreadsheet to Post Canada shows their official abbreviations, that I will probably merge with the current list at a later time.
Last edited by GizmoGuy411 on Mon Jan 30, 2012 10:35 pm, edited 1 time in total.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Sat Jan 21, 2012 12:38 am

Not at my PC at the moment, but my best guess is that the are using this based on files I've explored on my phone: http://www.nuance.com/for-business/by-p ... /index.htm

Sent from my Galaxy Nexus using Tapatalk
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Mon Jan 23, 2012 5:02 am

Less is better is also my opinion.. However for the purposes of this list more is better to learn how the TTS works. Then we can make our suggestions to Waze including everything we think that should be pruned.

Also looked into Nuance some more and found their product called Vocalizer that specifically included our two voice choices; Samantha, and Tom.

Interestingly Waze x.120 has voice files that include a canned set of English and Hebrew prompts? Many that I have never heard before.

Sent from my Galaxy Nexus using Tapatalk
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Tue Feb 14, 2012 5:26 pm

The results are back for the first abbreviations that were tested that started with the letters "A" and "B".

It is a slow process to test, as I need to drive to the location, and use my Android device to hear the TTS output. Then I need to hunt down the TTS file created and copy it to my PC. Each road in the sand box test rig has multiple abbreviations separated by spaces and slashes. Since slash marks still do not produce a pause, the playback needs to be slowed down and listened to repeatedly until each abbreviation can be heard. So far I have not been able to find the TTS files in iPad. (Slashed have now been replaced with commas to help in this process.)

I have not yet added any suggestions from this thread to the test rig in the sand box, as I wanted to experiment with the initial submissions first. I will also test to see if commas create a pause, and if colons create pauses all the time or just after the word "Exit".

Now that I have a process, hopefully I can test the results of the remainder of the initial submissions soon. Once complete, I'll submit the remainder of the abbreviations in the list, and add those suggested in this tread.

The link to the file has changed to:
The https://docs.google.com/spreadsheet/ccc ... TRzYUhGN0E
(I'll try to figure out how to to change the document without changing the link in the future. [DONE])


As a side note, GizmoGuy411 wrote:
For those interested in playing the TTS files on their PC, I've tried several audio players to attempt to slow down the playback without changing the pitch. Audacity had the capability, however the playback of the TTS files (in AAC file format) was distorted, even in normal play. I eventually gave up and just used Windows Media Player, which at least allowed me to slow down the playback. Since I use the Nuance Samantha voice in Waze, she was still understandable at slow speeds. Although she sounds like she should have gave up smoking many years ago.

[Update: If I append a dot MP2 or dot MP4 to the TTS file name, the WM player adjusts the pitch automatically as the speed is slowed down. Now she just sounds like she is off the cigs and on some bad drugs.]

[2012-08-20 Update: To hear the most current TTS results from your Waze client device, it may be necessary to clear your current TTS cache. Enter "cc@tts" without quotes in the Navigation search to clear the cache. Waze should reply with a "TTS cache has been cleared!" popup box. Then wait for "Searching ..." to end.]

If you would like to hear the TTS files on your Android device, I would recommend using the "ES File Explorer" app.: https://play.google.com/store/apps/deta ... oid.pop&hl

Navigate to /sdcard/waze/tts/database/lucal_nuance_8_mp3_Samantha_Female or /sdcard/waze/tts/database/local_nuance_8_mp3_Tom_Male to see the files. The file path may be slightly different with different os verions.

The file explorer actually has an audio player that will play the files fine.

So far I have not found a way to see the files directly on an Apple iOS device.
Last edited by GizmoGuy411 on Sun Mar 11, 2012 11:04 pm, edited 14 times in total.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Fri Feb 17, 2012 6:49 am

jenncard wrote:Does anyone have any thoughts about "one half", "three quarters", or (my personal favorite for the sheer ridiculous factor) "fifty one-hundredths"?


No.... :)
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

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

Postby GizmoGuy411 » Fri Feb 17, 2012 8:05 am

All suggestions from this forum (except for Jenn's last ones) are added to the list as of this post. Thanks everyone.

The letters of the alphabet were also added as uppercase letters and as uppercase capital letters in quotes. Additionally, the letters , "N", "E", "S", and "W" were also added with all combinations of upper and lower case, with single and double and with and without trailing periods.

I will add all the above to the sandbox test rig as soon I as get a chance.

As Jenn suggested (thanks Jenn), all the slashes have been removed in the rig and replaced with commas, so that after the next map updates, it should be easier to understand the TTS output. Currently it is a very slow process.

The list now includes results for the initially submitted abbreviations from "A" through "H".

In my above post, viewtopic.php?f=10&t=15178&p=144296#p144296 i've updated the bottom "side note" to include another playback trick to keep the pitch understandable.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 227 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users