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

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

Postby GizmoGuy411 » Tue May 08, 2012 2:17 pm

xteejx wrote:Actually, enclosing N/E/S/W in brackets also makes it say the directions.


Actually did not know that. However it is not surprising, as almost any representation of them produces the cardnal directions.

Unfortuneatly, on the other hand, so far, the only way we have found (primarily with Jen's testing) to get TTS to speak N, E, S, and W, as letters of the alphabet is by enclosing the lowercase letter desired in single qoutes. Not exactly optimal.
ImageImageImageImage

U.S. based 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 S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1373
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 541 times
Been thanked: 359 times

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

Postby GizmoGuy411 » Tue May 08, 2012 3:14 pm

AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?


I think I missed that post of yours way back when. Yes you are correct. However the list i posted for positional testing of variations of "st" was just to learn how TTS currently behaves.

And you are very correct. We definitely want to avoid any any TTS variations due to position.

It is already so complicated that we have had to resubmit variations for testing multiple times, and we still don't have a definitive answer. (Well maybe we do, but we have not heard every TTS result of the last tests yet.)
ImageImageImageImage

U.S. based 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 S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1373
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 541 times
Been thanked: 359 times

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

Postby GizmoGuy411 » Tue May 08, 2012 4:30 pm

The majority of jenncard's testing results from 2012-03-22 have now finally been added to the list.

This brings the list to 725 items for testing, with 719 entered into WME, and 523 or 72% of those actually tested.

Google Docs Spreadsheet:
Text-to-Speech (TTS) Abbreviations in Waze Clients - Test List for North America
ImageImageImageImage

U.S. based 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 S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1373
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 541 times
Been thanked: 359 times

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

Postby floppyrod84 » Tue May 08, 2012 6:26 pm

Is there no way Waze would be willing to allow direct access to the TTS API so this could all be tested easily? Or at least give us a list of the exceptions they have in place. From that, we can conclude that everything else will be said the same as on the Nuance Vocalizer Demo online.
floppyrod84
 
Posts: 2582
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby invented » Tue May 08, 2012 8:56 pm

xteejx wrote:Actually, enclosing N/E/S/W in brackets also makes it say the directions.

Do the parenthesis insert spaces before and after the cardinal direction?

eg.

Hwy 900 (W) / Anytown

= "Highway nine hundred [pause] west [pause] anytown"

?
HTC one, GPE, Android 4.4
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby floppyrod84 » Wed May 09, 2012 1:06 am

We use a space before and after, not inside the brackets. It does create a slight pause, yes.

Sent from my Telenor_OneTouch using Tapatalk
floppyrod84
 
Posts: 2582
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby floppyrod84 » Wed May 09, 2012 1:07 am

Can't see from phone if it's there, but Cr gives County Road. Annoying here as it's our convention for Crescent.

Sent from my Telenor_OneTouch using Tapatalk
floppyrod84
 
Posts: 2582
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby GizmoGuy411 » Wed May 09, 2012 6:27 pm

xteejx wrote:Can't see from phone if it's there, but Cr gives County Road. Annoying here as it's our convention for Crescent.

Sent from my Telenor_OneTouch using Tapatalk


Yes you are correct. The TTS result for "Cr" is "County Road". Also as an example, "CR-123" would say "County Road One Two Three".

For "Crescent" the USPS and Canada Post both use "Cres" for their official abbreviation. Waze also recognizes "Cres" with the TTS output of "Crescent". So, it looks like "Cres" is our best option on this side of the pond. There are also some longer, less optimal abbreviations that are commonly used for "Crescent" that are in our test list, but have not been tested yet. Of course all this is for North America, and not for across the pond. Hopefully someday you will have your own TTS server.
YouTube Video of the hilarious British Daniel talking for Waze!

xteejx wrote:Is there no way Waze would be willing to allow direct access to the TTS API so this could all be tested easily? Or at least give us a list of the exceptions they have in place. From that, we can conclude that everything else will be said the same as on the Nuance Vocalizer Demo online.


As far as direct access to the TTS exceptions, I have a feeling that Waze has made changes on their end and they have not necessarily documented them. From what I have read, Nuance provides a tool to make such changes, however Waze has not found a way to provide the tool to us. Plus there are two issues. Exceptions should be just that. Such a tool could provide us with a way to change the TTS on a per segment basis, but not with the global TTS result.

The global (as in country TTS server wide) TTS results for abbreviations would still need to be handled by Waze and or Nuance. From our communications with Waze at the Palo Alto meet-up, they do NOT have a list of the known TTS results. That is one reason why we are doing it ourselves.

And using the Demo at Nuance is not much help either. The Demo is not for their custom "Automotive" package, which I assume it what Waze is using for TTS. So anything we test in the Demo, could be different from the Nuance Automotive solution, and further different as a result of the exceptions added by Waze.

On Sat 2012-Feb-18, 01:02:55, GizmoGuy411 wrote:For those who would like to hear Samatha or Tom (plus others) convert text to speech, here is link to Nuance's interactive demo of their "Vocalizer for Netrork 5" product. Note that although the database is similar, it is not customized with their automotive product, or with Waze customizations.

Interactive TTS Demo: http://www.nuance.com/vocalizer5/flash/index.html

The sister product that Waze appears to use, is Nuance's "Vocalizer for Automotive" (no demo found), that has a preconfigured database customized for automotive use, and includes their Vocalizer Studio, which allows for a customization like several people in the various threads here about TTS have talked about; "it also allows customized text processing and the creation of user dictionaries for exception pronunciations."

The Nuance Language Portfolio for their Automotive Services, for the US English in the Americas, shows Samantha and Tom which Waze uses and Lisa who is not available in Waze. Check it out for other voices.

Edited 2012-05-09 to include additional relevant links to Nuance.
Last edited by GizmoGuy411 on Wed May 09, 2012 7:25 pm, edited 2 times in total.
ImageImageImageImage

U.S. based 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 S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1373
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 541 times
Been thanked: 359 times

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

Postby invented » Wed May 09, 2012 11:56 pm

Confirmed that "3rd Street" comes out as "Third street"
HTC one, GPE, Android 4.4
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby GizmoGuy411 » Thu May 10, 2012 12:36 am

invented wrote:Confirmed that "3rd Street" comes out as "Third street"


That is good news. Now I wonder how far we should test to. I suppose a look at New York City would be the best guess for max.

Sent from my Galaxy Nexus using Tapatalk 2
ImageImageImageImage

U.S. based 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 S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1373
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 541 times
Been thanked: 359 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users