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: adriansinger

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

Postby GizmoGuy411 » Mon Nov 19, 2012 4:58 pm

LittlestLou wrote:Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...



Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".
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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

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

Postby GizmoGuy411 » Mon Nov 19, 2012 5:10 pm

xteejx wrote:OK its all St are now saying Saint. Wtf guys? The Street Paul's Street I could live with as Saint is only some roads, but now every Street is Saint, seriously sort it out and revert all recent changes to the UK TTS. Or better yet, give one of us access to the rules on Vocalizer and we can do it in a few minutes!

Sent from my GT-I9100 using Tapatalk 2


Send a message about this "Support" and see what happens. They don't read this thread.

On the other hand, I have been in contact recently with Waze about this and a few other issues, and they are looking for a possible solution.

I doubt that giving us direct access to the Vocalizer interface will be a possibility however. They would probably have to build an interface to it.

To make matters worse, the issue may not be something solvable with Vocalizer. There are actually two issues at hand. One is the overall TTS database and customized "mobile app" database from Nunance, and another is the exception rule system that Vocalizer can adjust for individual things.

Since I've never found any public documentation for the Nuance Vocalizer, so I really do not know how it interacts with the databases, nor what exceptions it can handle.
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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

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

Postby GizmoGuy411 » Mon Nov 19, 2012 5:13 pm

xteejx wrote:St at the end is now saying Saint. Will look into this at my end as I didn't name it and it might have a dot.

Sent from my GT-I9100 using Tapatalk 2



What "voice" are you using for Waze? In the US we use Nuance's "Samantha" or "Tom", however I suspect that the voice(s) for the UK, may not use the same TTS databases.
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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

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

Postby GizmoGuy411 » Tue Nov 20, 2012 2:31 am

jasonh300 wrote:
How about CR-##?


Last February it worked. For some reason I had an "Add" notation for it. Guess I should retest it.

Now that the tile turn around time has shortened I need to test the rest of the list. Hopefully before mid January.
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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

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

Postby GizmoGuy411 » Wed Nov 28, 2012 4:19 am

sbelekevich wrote:...
Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)



Thanks for reconfirming that.
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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

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

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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 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

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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 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

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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 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

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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 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

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: 1293
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 349 times
Been thanked: 211 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users