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 Mar 04, 2014 7:53 pm

Will chime in as soon as I have some time to address several recent posts.
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: 540 times
Been thanked: 359 times

Re: business loop/spur/alternative route

Postby dbraughlr » Mon Mar 17, 2014 7:47 am

Those who are interested in the discussion of "Business" in the highway name, please see this thread on the subject to address the first matter of updating the wiki to standardize naming without the abbreviation "Bus".
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

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

Postby egnralnc » Sat Mar 29, 2014 3:24 pm

Hi all,
I have an issue in Raleigh NC with an exit ramp (https://www.waze.com/editor/?lon=-78.80 ... 12&env=usa). When approaching this exit, Samantha says "Aviation Parkway N" instead of "Aviation Parkway North". I've not seen anything in this forum to suggest that this shouldn't work. Any thoughts?
ImageImageImage
Homebase: NW Raleigh & RTP NC
Extended areas covered: Greenville SC, Lincolnton/Denver NC
Waze running on Samsung Galaxy S3
egnralnc
 
Posts: 44
Joined: Sat Mar 29, 2014 6:59 am
Has thanked: 14 times
Been thanked: 4 times

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

Postby sketch » Sat Mar 29, 2014 8:30 pm

This has been reported in a few places around the forums. There's been some kind of bug propagating over the past couple months where "N" is not pronounced "north" after certain words — "Pkwy" and "Expy", for example, and I think perhaps in "Cesar Chavez N" as well.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5690
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1244 times
Been thanked: 1704 times

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

Postby txemt » Sat Mar 29, 2014 9:56 pm

sketch wrote:This has been reported in a few places around the forums. There's been some kind of bug propagating over the past couple months where "N" is not pronounced "north" after certain words — "Pkwy" and "Expy", for example, and I think perhaps in "Cesar Chavez N" as well.


And Florida's Turnpike N
Just wazeting my time to help you waze your route smoothly.
txemt
Area Manager
Area Manager
 
Posts: 4769
Joined: Tue Jul 17, 2012 7:03 pm
Location: Miami, Fl
Has thanked: 42 times
Been thanked: 1032 times

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

Postby sketch » Sat Mar 29, 2014 11:44 pm

Possible, then, that instead of failing to pronounce it as "north" after certain words/abbreviations, it's failing to pronounce it as "north" except after certain words/abbreviations. Same result (as far as we know); different causation.

In other words, it seems more likely that something in there is telling it to say "north" after a given list of things (e.g., "St", "Blvd", any numbers) than it is that something in there is telling it not to say "north" after "Pkwy", "Expy", "Chavez", and "Turnpike".
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5690
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1244 times
Been thanked: 1704 times

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

Postby Thortok2000 » Sun Mar 30, 2014 12:46 am

The main bug I have is that the TTS given of a destination when you've reached it seems to use a different TTS than the TTS of turn instructions.

As a turn instruction, 'Ave' is always Avenue, but as a destination, it rhymes with 'have.' =/
Image
ImageImage
Area Manager of Greenville, SC! ^_^
Thortok2000
Area Manager
Area Manager
 
Posts: 722
Joined: Tue Oct 15, 2013 1:01 am
Location: Greenville, SC
Has thanked: 190 times
Been thanked: 140 times

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

Postby sketch » Sun Mar 30, 2014 12:51 am

Thortok2000 wrote:The main bug I have is that the TTS given of a destination when you've reached it seems to use a different TTS than the TTS of turn instructions.

As a turn instruction, 'Ave' is always Avenue, but as a destination, it rhymes with 'have.' =/

That may be the "at" instruction some of us here are/were so curious about. Short summary: Waze generates 2 TTS files for everything, one by itself and one with the "at" prefix, or something like that. I think the latter is for the destination, but we aren't certain.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5690
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1244 times
Been thanked: 1704 times

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

Postby Thortok2000 » Sun Mar 30, 2014 2:01 am

The one with the at is the turn instruction, I would assume. The one without the at is the destination.
Image
ImageImage
Area Manager of Greenville, SC! ^_^
Thortok2000
Area Manager
Area Manager
 
Posts: 722
Joined: Tue Oct 15, 2013 1:01 am
Location: Greenville, SC
Has thanked: 190 times
Been thanked: 140 times

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

Postby GizmoGuy411 » Sun Mar 30, 2014 3:27 am

Thortok2000 wrote:The main bug I have is that the TTS given of a destination when you've reached it seems to use a different TTS than the TTS of turn instructions.

As a turn instruction, 'Ave' is always Avenue, but as a destination, it rhymes with 'have.' =/


If you look at the list, you will see two columns for TTS results. While not many have been retested for both results, a few in the list are rather interesting for their differences.

Recently I tried to check the dual file results as I had done before, however was only able to find the files prefixed with "at" in my Android device.
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: 540 times
Been thanked: 359 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users