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

[ img ] 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 Webs101 » Mon Jun 18, 2012 11:55 am

Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Also, along with Saint, there is also Sainte for the feminine. Normally abbreviated St and Ste without periods.
Webs101
Waze Local Champs
Waze Local Champs
 
Posts: 507
Joined: Sun Feb 26, 2012 9:09 pm
Location: Montreal, Quebec
Has thanked: 22 times
Been thanked: 164 times

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

Postby Panda47 » Sun May 20, 2012 1:10 am

Hi. Can we get the following special character in it? I know you have it already surrounded by single quotes, but what about w/o the quotes? What about with a street name?

Character = ½
Example: 30th ½ St
Example: 31st ½ St

Thanks, and keep up the good work.
Panda47
 
Posts: 122
Joined: Tue May 01, 2012 7:59 am
Location: Mission, Texas, USA
Has thanked: 0 time
Been thanked: 0 time

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

Postby vectorspace » Sat May 12, 2012 3:20 pm

Another topic: Indian Reservations in the US...

I've not been a part of this discussion and have searched the 18 pages on TTS without finding anything. This is also probably a topic for textual road abbreviations on the client.

There are a lot of American Indian reservations in the US Southwest. I am starting to address some of the roads there now in New Mexico. I see that these are not well represented in the material on Waze likely because they have fewer drivers. Some areas are high traffic from tourism or casino traffic. These regions actually have a large amount of autonomy from the US Government and therefore different road naming conventions than states or interstates.

One convention is "Indian Service Route XXX." Many times these are named inconsistently in the current map with the usual abbreviation "Indian Svc Rte XXX" being used, but sometimes other variations being used for highway-like roads. Other lesser streets have names like "Indian Rd XXX." Other states may use other naming conventions.

It would seem that the primary textual values on the map are displayed on an often-cramped client display, a much shorter version could be used. This would impact the TTS as well. Obviously the smallest abbreviation might be "ISR-XXX." That's one I prefer because it seems brevity is the primary driver due to a small client display.

It would be nice if we considered the US Indian reservations in both the textual abbreviations and the TTS.

As a relative outsider (6 months new) and pragmatist, I am often struck by how the Waze software team seems distant from the dedicated AM/editor group both dynamically and by setting standards. Maybe that is part of what makes a world-wide social app work. Efforts here are commendable. Client/Server software seems like the place to solve a lot of these issues with ability to parse a wide range of naming conventions and abbreviations. If Waze is truly successful in having a community-based editing crowd, many less-dedicated and formalized editors will name things however they want and that crowd will overwhelm dedicated editors.
vectorspace
 
Posts: 1183
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 420 times

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

Postby floppyrod84 » Thu May 10, 2012 10:32 am

In that case the first one ()

Sent from my Telenor_OneTouch using Tapatalk
floppyrod84
 
Posts: 2569
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 » Thu May 10, 2012 5:33 am

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


Types of brackets (quoted in part from Wikipedia):
( ) — round brackets, open brackets, brackets (UK), or parentheses (called parentheses by Microsoft)
[ ] — square brackets, closed brackets, or brackets (US), (called square brackets by Microsoft)
{ } — curly brackets, definite brackets, swirly brackets, curly braces, birdie brackets, Scottish brackets, squirrelly brackets, braces, gullwings, seagull, fancy brackets, or DeLorean Brackets, (called curly brackets by Microsoft; see Character Map - %windir%\system32\charmap.exe)

I hate to say it, but I guess we need to test N/E/S/W with all of them.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 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"
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 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 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: 2569
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: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: 2569
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"

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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users