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 jondrush » Wed May 29, 2013 6:40 pm

Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?
Keeping the Waze maps tidy since 2009
Northeast Region Assistant Coordinator
jondrush User Page
ImageImage
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2299
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 111 times
Been thanked: 362 times

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

Postby jondrush » Tue Apr 15, 2014 4:56 pm

AlanOfTheBerg wrote:Jr. B St. Dr. = "junior bee saint doctor"

That's a real place?
Keeping the Waze maps tidy since 2009
Northeast Region Assistant Coordinator
jondrush User Page
ImageImage
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2299
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 111 times
Been thanked: 362 times

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

Postby Jpere » Sun Oct 13, 2013 12:20 pm

sketch wrote:
taddison1 wrote:
jasonh300 wrote:What was the exact name of the expressway, as named on the Waze map? It's working fine at the expressway near me.


It's "N Central Expy".

Whatever this TTS problem is, it doesn't seem to be consistent. Most streets announce fine, there seem to be just a few that don't.

I haven't figured out if it's always the same streets that fail to announce the abbreviations correctly, or if it's just a random failure that can occur on any street. Unfortunately, the streets that I've heard fail are far from my house so I can't easily go and drive them again.

All the examples I saw with the "N" problem seem to be where Waze doesn't expect a "north", that is, wherever the N is not preceded by a street abbreviation or a numerical highway designation. So it didn't work on "Cesar Chavez N" or "I-35W N", while I assume it would work on "Cesar Chavez Dr N" or "I-35 N".


You could be on to something. There are some ramps I need to fix in the Miami area that read out as "Florida's Turnpike N" instead of "Florida's Turnpike North" and it might be because it's not expecting that N to be there.
Jpere
Beta tester
Beta tester
 
Posts: 198
Joined: Tue May 10, 2011 3:52 am
Has thanked: 41 times
Been thanked: 5 times

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

Postby Kandralla » Fri Sep 14, 2012 8:34 pm

GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!


Am I correct in my assumption that this means that William Penn Highway will now be called "William Penn Highway" as oppoesed to "William Pennsylvania Highway"?

If so thanks, that was annoying.
Area Manager for Pittsburgh and Erie, PA
Kandralla
 
Posts: 67
Joined: Wed Jan 18, 2012 7:15 am
Has thanked: 0 time
Been thanked: 0 time

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

Postby kentsmith9 » Fri Aug 03, 2012 11:21 pm

Cord is what I will be wrapping around my neck if we go a second month with no map updates in NA.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Sun Aug 05, 2012 8:12 am

jasonh300 wrote:
kentsmith9 wrote:Cord is what I will be wrapping around my neck if we go a second month with no map updates in NA.


A second month??? We're almost 3/4 of the way through the second month!

See. I am getting so whacked I forgot we are almost into our third month. :oops:
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Fri Aug 17, 2012 4:15 am

bgodette wrote:
WeeeZer14 wrote:There have been situations were Waze has cached the TTS audio files for frequently used streets/ramps. Users had to manually delete these files to get the effects of new TTS rules. I don't remember the details, but just wanted to point that out if you see slightly different pronunciation in different cases. It could be the case or it could be cached data.

Entering cc@tts into waze's search will clear the tts cache.

It's all my phone's fault for using Tapatalk.

I have been thinking about adding the known codes into the Wiki. I started collecting what I could find in the forums. I can create the Wiki page (unless someone knows it is there and I missed it) and add what I have found so far.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Fri Aug 17, 2012 4:18 am

I thought I have recently heard some directions not be spelled out.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Sat Aug 18, 2012 1:48 am

kentsmith9 wrote:I thought I have recently heard some directions not be spelled out.

I was wrong. I usually have to have the TTS off when my wife is in the car so she does not get too annoyed being reminded about the hundreds of hours I spend on Waze instead of her. :oops:

What I was hearing was really "EAST", but the "AST" portion was so quiet that the road noise drown it out.

I did notice that "W"s sound a little compressed. When I hear "Washington" it is as if I only hear the second portion of the "W" or maybe a bit of the middle of the letter's sound is missing.

I will try to update the TTS file with the code above and check it again.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Sat Aug 18, 2012 6:20 am

kentsmith9 wrote:I have been thinking about adding the known codes into the Wiki. I started collecting what I could find in the forums. I can create the Wiki page (unless someone knows it is there and I missed it) and add what I have found so far.

Complete. viewtopic.php?f=276&t=24723
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3128
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users