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 berestovskyy » Mon May 20, 2013 6:28 pm

PhantomSoul wrote:But in the long run, unless Waze creates some kind of administrator certification program to teach people these backdoor hacks [...]

"Certification program" for "backdoor hacks"? Oh, come on! :lol: Every single system or game has settings. They are confusing sometimes, that is why UI developers hide them under the "Settings" ;)

Yes, I really think the feature we use for one of a 100 road segments really deserve "to bypass the UI development process" like you said. And it's not only about immediate returns, but also about cluttering WME interface.

Examples?
  1. "Toll roads". There are many countries with no toll roads at all. But the option is there, easily accessible.
  2. "Lock", now with a dropdown box. How often do we use this feature? New editors especially.
  3. On the other hand, every single segment has an address. But we have to click "Edit" next to "Unnamed segment" and then "Apply".
So no, I don't like the way "WME system appears to be headed" :(
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

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

Postby bgodette » Thu Jan 19, 2012 4:38 am

Basically there needs to be positional awareness for handling things like St, Dr, N/S/E/W. Can anyone think of a name where St isn't Saint unless it's at the end of the name and therefore Street? Same thing for Dr.

N/S/E/W is the letter name if it's in the middle of the street name, or the only "word" before the St/Rd/Blvd/etc. So you can have "W N St" for "West Enn Street" and "N St" for "Enn Street", if you need "West North Street" you'll just have to use "W North St".

CR-### should be County Road, I'm not sure what we should use for State/County Route, maybe RT-### and TTS be "Route ###". (Rowwt or Root? it's regional)
SH-### should be State Highway ###.
US-### should be You Ess ### or You Ess Highway ### (I'd prefer to not have Highway but that's just me)
I-### should be Eye ###
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Thu Jan 19, 2012 6:23 pm

jenncard wrote:One of my cities out in the hinterlands is littered with "27 1/2 Rd", "D 1/4 Rd", or one of my personal favorites "E 50/100 Rd". Unfortunately, I've actually never Wazed there so I have NO IDEA what TTS does! That said, I've never seen a UR saying "should be one-half Rd not one {pause} two Rd".

I can tell you that when it comes to "Co Rd 3 1/2" what TTS says is "Co Road Three One Slash Two", with the Co as the first syllable of "cooperative", I have yet to change one of these to CR-3.5 or CR 3.5 to see what happens.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Thu Jan 19, 2012 10:21 pm

I think we all realized going into this that it was not going to be trivial. I agree with Harling that whatever we come up with needs to be consistent and easy to implement in the parser.

Perhaps the way we should be approaching this is by what abbreviations are ambiguous; What else is there beyond the compass directions, St, Dr, and Bus? Are there other conflicts for Spanish and French? And then there's the ROTW once they get TTS.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Fri Jan 20, 2012 11:12 pm

bmitch3020 wrote:Any automated solution is going to result in a lot of one-off or edge cases that don't work correctly. I think the best solution is to provide a TTS input under the Label input. Use the default TTS rules if no values are provided, and show the expanded value. And if "customize TTS" or some other checkbox is selected, allow the map editor to put in plain English (or their language of choice) into the TTS box. E.g.:

Label: Dr. Martin Luther King Jr. St N
TTS: Doctor Martin Luther King Junior Street North

Label: N St.
TTS: N Street

Label: Geo Wash Pkwy
TTS: George Washington Parkway

This way the label can match the sign, but the editor can fix the TTS if we see the default isn't correct.
Actually this needs to be expanded on further, what we need to know is which Open Source TTS engine is being used so we know what the TTS hinting syntax is, so we have direct control to correct regional pronunciation as well as non-English words in a predominately English environment.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Wed Feb 15, 2012 12:27 am

jenncard wrote:Does anyone have any thoughts about "one half", "three quarters", or (my personal favorite for the sheer ridiculous factor) "fifty one-hundredths"?

I keep forgetting to convert some of those Co Rd X 1/2 to CR-X.5 to see what happens. In any case it's just more TTS preprocessing to handle fractions.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Wed Feb 15, 2012 3:18 am

jenncard wrote:Then there is also the case where X<>number, like "F 1/2 Rd" :roll:

Isn't that F#?
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Wed Feb 15, 2012 4:05 am

jenncard wrote:No. I think that it is actually "BJ Rd".

:lol:
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Mon Feb 27, 2012 9:04 pm

jasonh300 wrote:Not sure if anyone else confirmed this, but last night, I found that St. is pronounced as "Saint". This was in "Bay St. Louis". I don't know whether it's the positioning or the period that makes it work. It pronounces Louis "Lou-ee", but that's another issue.

Sketch pointed out yesterday in another thread that "Iberville" is pronounced "d'Iberville", which is surprising. We pronounce the street "EYE-ber-vil" whereas d'Iberville, like the town in Mississippi, is usually pronounced "dee-IHB-er-vil".

Didn't I already say Wanda is a French-Canadian Mexican?
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

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

Postby bgodette » Tue Aug 14, 2012 7:45 am

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.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users