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

This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby GizmoGuy411 » Sat Jan 05, 2013 1:21 am

imajica12345 wrote:I live in Quebec and often we have streets with directions like east/west, but here it is spelled est/ouest. it pronounces the ouest as west which is fine, but it pronounces est as "Estate".

Something to eventually fix i assume


I've set up a couple of test to see how this can be handled.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 12:56 pm

txemt wrote:I have confirmed, today, that "SH" for "State Highway" is NOT working. :(


Correct. Along with "SH" I have also just tested for "SH-123" also, and can re-confirm that is still does not work either.

I've also tested for various forms of abbreviations for "Township" and "Township Road" and did not find any that worked.

I'll add these results to the list shortly.

What I did discover was another anomaly, for differing results between the two audio files that are created for any given segment. One file always says just the "Street Name" property contents, while the other file says, the word "At" followed by "Street Name" property contents.

The test for "SH-123" resulted in one audio file that said "At ess-aitch one two three" and the other file said, "ess-aitch one hundred twenty three". Very curious.

The last such similar anomaly was with a test of “Borough”, “Parade”, and “Parish”, by using the abbreviations of "Boro par ph".

One file said "At borough parade phone, and other other said, "borough par pea-aitch".
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 2:07 pm

AndyPoms wrote:Pkwy confirmed by several people as Parkway.


Andy, do you happen to know which capitalization variations were confirmed?

Unfortunately, the TTS results are often defendant on capitalization, punctuation, and position with other words, not to mention the other issue I just mentioned in my previous post.

These make the TTS list that much larger and complicated, as most of the early tests did not take any of these depandancy issues into consideration.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 4:32 pm

hmarian wrote:The same for me.
"Pkwy" is reading out "Parkway" on the client and is more consistent with road signage.
Could someone finish this test and add to the TTS Log FIle?

Thanks,
Hagay.


rcenteno_davis wrote:... Do we need to add a separate row?


I've added "PARKWY, parkwy, Parkwy, PKWAY, pkwy, Pkway, PKWY, pkwy, Pkwy, PKY, pky, Pky, PKWAYS, pkways, Pkways" to the test rig for completeness, and will update the list in a couple of days, once the map tiles update and I can listen to the results.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Tue Jan 15, 2013 2:56 pm

The list was updated yesterday with the results for most of the abbreviations and capitalization variations for:

Boro, Borough, Center, Centers, Centre, Estate, Estates, Rail Road, Ranch Road, Ranch to Market, Rural Route, State Highway, Township, Township Road.

Update: Parkway and Parkways also added to list.

The most significant change was the addition of a new column to reflect the test results for both audio files that are created by Waze.

After tweaking the text more today, here is the note that was added to the file to explain the change:

In the Text-to-Speech (TTS) Abbreviations in Waze Clients
Test List for North America, GizmoGuy wrote wrote:

• Waze creates two TTS audio files for every routed road segment on the Android. One file speaks just the names contained in the segment name property. The other prefixes the segment name with the word "at". (On iOS devices, only the prefixed files have been found thus far.) It was not until late 2012 that a distinction in the TTS results between the two files was noticed. Testing of both files started on 2013-01-12, when a second result column was added. Therefore, until all items are re-tested, an entry in the Non "at" prefixed audio file column, will be either for the prefixed or the non-prefixed results if the "at" prefixed audio file column is empty.



I have not yet edited the opening post to reflect this.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 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.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Thu Jan 31, 2013 3:58 am

Regarding roads named as letters, I agree that surrounding the capitalized letter with single quotes will look the best as Alan said. I have yet to retest for the various test from the list for the letters, N, E, S, and W, however multiple Wazers have indicated recently that the result are now different that what is shown in the list.

Using a period after a letter may lead to confusion, as it looks like a standard cardinal direction abbreviation, as Jason said.

However using periods with multiple letters, such as A.T.T. or N.Y.C. to get the abbreviation pronounced as individual letters should be fine, if it really is working that way universally now.

One problem is that we have found in the past that many factors affect the TTS results.

The position of the abbreviation relative to other words, punctuation around it, capitalization, and the various combinations of those factors.

When list here was created, I used a space a forward slash and a space around every abbreviation, with multiple abbreviations per test segment. We expected a forward slash to produce a pause, as Waze said it would be any easy change. Since it did not happen as soon as we hoped, the TTS results were very hard to understand without any pauses. Another editor, jenncard, was helping at the time with the project, and created a test rig of her own with each abbreviation with a comma and a space. The results were much easier to understand.

Last spring I started to use her method for testing. Since that time however there has been suspicion that the comma may even cause a change in the results. Furthermore, it may be possible that ANY other words on a segment besides the abbreviation to be tested may create a different result.

If you look at the most recent entries in the list, you may notice that several test segments have created TWO TTS audio files which are actually different from each other. (On Android, one file is created with just the words in the segment name, and another file is created with the segment name prefixed with the word "at".)

A few examples:
- The abbreviation "RR" for "Rural Route", says the letters "ar ar" in one file and "Rural Route" in the other.
- The abbreviation "Cent" for "Center", say "Cent" in one file and "Center" for the other.
- Several abbreviations for "Parkway", say the letters for one file if the abbreviation is capitalized , and say "Parkway" for the other file.
- While testing "SH-123" as am abbreviation for "State Highway 123", one file said the letters and the numbers "one hundred twenty-three", where the other file said the letters and "one two three".

And in one case were I was testing the abbreviations "boro, par, ph" for Borough, Parade, and Parish, I had TTS results that said "borough par pea-aitch", and the other file said "borough parade phone".
When "ph" was tested again by itself, the results were the letters "pea-aight" for both files.

Testing for every possibility is a bit overwhelming at this point.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Sat Feb 02, 2013 5:42 am

To insure that we have tested as many possibilities for BOTH TTS files generated, here are the re-tests I just submitted to my test rig. (They are NOT in the list yet.)

N / n / E / e / S / s / W / w / NE / ne / NW / ne / SE / se / SW / sw
N. / n. / E. / e. / S. / s. / W. / w.
'N' / 'n' / 'E' / 'e' / 'S' / 's' / 'W' / 'w'
"N" / "n" / "E" / "e" / "S" / "s" / "W" / "w"
/N , /n , /E , /e , /S , /s , /W , /w

Please wait until the results are in for all of these before changing any segment names.

They were entered into WME 2013-02-03 05:30 UTC, so the results may not be available until Monday. I'll will try to audio test them as soon as they are incorporated into the map updates.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Sat Feb 02, 2013 5:57 am

Regarding "Avenue S", I feel that since the word "Avenue" is not used as a suffix, and that it is used in this case more as a proper noun and not as an adjective, that it probably should remain spelled out, which would mean the name entry would be [Avenue 'S'], even though it implicitly implies that the road is an avenue.

As an example, there is a road near me called "West Course Road". I have it named in Waze as [West Course Rd] rather than [W Course Rd]. The word "West" in this case is part of the proper noun for the name of the road, and NOT a cardinal prefix adjective.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Thu Feb 21, 2013 5:53 pm

Sorry all, but I have been too busy lately to work on the list. I'll try to get the latest results posted once I have some time.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1106
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 169 times
Been thanked: 105 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users