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 jenncard » Thu Mar 01, 2012 6:07 pm

I just encountered a "Ste" (someone had intended as state) which I am pretty sure was pronounced as "suite"
Image
Recovering Waze addict, occasional driver and editor in LA.
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 8 times

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

Postby jenncard » Sun Mar 04, 2012 7:14 pm

jasonh300 wrote:Fortunately, I learned to drive a stick-shift when I was about 11. :lol:

I taught myself when i was 13. It is amazing how much one can learn by watching very, very closely...

So, still no map update? At this rate, I'm thinking I should have kept adding more and more roads to my TTS playground!
Image
Recovering Waze addict, occasional driver and editor in LA.
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 8 times

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

Postby jenncard » Fri Mar 23, 2012 6:07 pm

A few interesting observations from my testing:
- CASE vs. case definitely DOES matter
- use of ' or " has interesting (and unpredictable) results
- and testing these rigs isn't has hard as one might imagine :-)

Of the following segment names:
Code: Select all
1: “E” Rd, 2: 'E' Rd, 3: E. Rd, 4: “E.” Rd, 5: 'E.' Rd,
1: “e” Rd, 2: 'e' Rd, 3: e. Rd, 4: “e.” Rd, 5: 'e.' Rd, 6: e Rd,

Some were "gobbledegook", many were "East Rd" and only one actually delivered "Eee Road"
Code: Select all
'e' Rd

And while "Wash Rd", and "Wash. Rd" were pronounced as the word, "WASH Rd" somehow or another came out as "Washington Rd"

For "unknown" words, the TTS engine has two different behaviors:
- spell out the letters, e.g. TR = "tee ar"
- attempt pronounciation, e.g. "Tline" = "t'line" (or whatever you might imagine that to sound like)
I thought that this was varied based on UPPER CASE = spell it out, Mixed Case = attempt to pronounce, but this is not consistent.

As far as this being easier than anticipated to actually test, here are the tips:
- spreadsheets are your friend (this is generally always the case)
- Name the segments as I've done above, with multiple test values identified numerically (with colo) and comma separated
- I set up segment names with up to 10 different test values, and still only had to replay one or two more than once
- create the segments in a radial, coming out from one junction
- attach a small segment at the end of the "test named" segment with a short name. This makes it easy to select the destination.
- Most important, it isn't actually necessary to HEAR the tts on your phone! If you are close enough to the junction with your test segment, the .tts file will be created. "Stop nav" to that destination, navigate to the next, and so on. Not even necessary to move your car.... or even be in your car. I sat at the dining room table (just in front of my big bad junction)

This is about what mine looks like at 100m/500ft zoom. The northern "radial" was more than adequate for me to be able to select the destination segments
Attachments
tts setup.jpg
tts setup.jpg (26.28 KiB) Viewed 1119 times
Image
Recovering Waze addict, occasional driver and editor in LA.
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 8 times

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

Postby jondrush » Mon Sep 10, 2012 11:22 pm

How do I keep Penn St from being announces as Pennsylvania street?
Keeping the Waze maps tidy since 2009
Northeast Region Assistant Coordinator
jondrush User Page
ImageImage
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2289
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 109 times
Been thanked: 361 times

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: 2289
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 109 times
Been thanked: 361 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: 2289
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 109 times
Been thanked: 361 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: 3092
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 507 times
Been thanked: 581 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: 3092
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 507 times
Been thanked: 581 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: PvilleT