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 sketch » Wed Jun 11, 2014 9:55 pm

AlanOfTheBerg wrote:
driving79 wrote:On a ramp in Jacksonville, FL this is saying STREET: to I-295 S St. Augustine.

That looks like a malformed segment name. Shouldn't it be either "to I-295 S / St. Augustine" or "to I-295 / S St. Augustine"?

I agree, but should it matter? Wasn't the point to take position awareness out of the "Saint"/"Street" dichotomy entirely, making every "St." "Saint" and every "St" "Street"? So, did only the latter actually happen?
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5849
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1387 times
Been thanked: 1882 times

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

Postby AlanOfTheBerg » Wed Jun 11, 2014 9:53 pm

driving79 wrote:On a ramp in Jacksonville, FL this is saying STREET: to I-295 S St. Augustine.

That looks like a malformed segment name. Shouldn't it be either "to I-295 S / St. Augustine" or "to I-295 / S St. Augustine"?
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23589
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1123 times
Been thanked: 4770 times

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

Postby AlanOfTheBerg » Wed Jun 11, 2014 8:52 pm

usa_iv3ckt44 wrote:What would you guys think of ...

Interesting idea, but really the wrong thread to post something like this. Please in the Waze app forum, and not part of an existing thread which is unrelated to your idea.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23589
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1123 times
Been thanked: 4770 times

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

Postby driving79 » Wed Jun 11, 2014 5:09 pm

On a ramp in Jacksonville, FL this is saying STREET: to I-295 S St. Augustine.
driving79
US Waze Champs
US Waze Champs
 
Posts: 1867
Joined: Mon Jul 18, 2011 6:45 am
Location: Florida
Has thanked: 138 times
Been thanked: 1045 times

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

Postby usa_iv3ckt44 » Wed Jun 11, 2014 2:51 pm

What would you guys think of a cheap remote that wirelessly reports the most common/important incidents (crash/police/red light cameras)? I think if there was a device that you could clip on your steering wheel/air vent or anywhere in the car that doesn't require you to take your eyes off the road. I'm trying to do a DIY project at home so I don't have to spend 10 seconds with my eyes on my phone and off the road each time I want to report an incident.

Thanks guys!
usa_iv3ckt44
 
Posts: 3
Joined: Wed Jun 11, 2014 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby PesachZ » Tue Jun 10, 2014 1:58 pm

GizmoGuy411 wrote:
PesachZ wrote:[... quote reduction ...] The Maj was not expanded into Major.
BTW this is still not working. is there a fix in the pipes, or should I change the ramp name?

https://www.dropbox.com/s/agfluap6dbfpp0r/1402392486-303471-1.mp3

Sent using Tapatalk for Android 4.4.2


I have this on a list to submit once Waze catches up with a few other previous submissions. So please hold off changing the ramp name yet.

Will do, just wasn't sure what the situation was. please let me know when to check it again. Thanks

Sent using Tapatalk for Android 4.4.2
Last edited by PesachZ on Wed Jun 11, 2014 3:59 pm, edited 1 time in total.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4339
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1979 times
Been thanked: 2174 times

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

Postby GizmoGuy411 » Tue Jun 10, 2014 1:54 pm

PesachZ wrote:[... quote reduction ...] The Maj was not expanded into Major.
BTW this is still not working. is there a fix in the pipes, or should I change the ramp name?

https://www.dropbox.com/s/agfluap6dbfpp0r/1402392486-303471-1.mp3

Sent using Tapatalk for Android 4.4.2


I have this on a list to submit once Waze catches up with a few other previous submissions. So please hold off changing the ramp name yet.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 648 times
Been thanked: 427 times

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

Postby PesachZ » Tue Jun 10, 2014 9:33 am

PesachZ wrote:
GizmoGuy411 wrote:
PesachZ wrote:On April 27th this ramp to the I-87 S was pronounced "Keep left to eye 87 South, Maj Deegan Expressway, Manhattan, Queens". The Maj was not expanded into Major.


Thanks for the link.

Can you clear your TTS cache, and test this again in the next few days to see if anything changed again after the update Alan mentioned? If you can not get to it, let us know and we can try to test it remotely.

I cleared my cache and got a bar at the top that it was preparing navigation voice. I waited till after the bar went away then drive through.
[ img ]
It said " Keep left at eye 87 South, Maj Deagan Expressway, Manhattan, Queens "

Sent using Tapatalk for Android 4.4.2

BTW this is still not working. is there a fix in the pipes, or should I change the ramp name?

https://www.dropbox.com/s/agfluap6dbfpp0r/1402392486-303471-1.mp3

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4339
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1979 times
Been thanked: 2174 times

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

Postby PesachZ » Sun Jun 08, 2014 5:48 pm

PesachZ wrote:
GizmoGuy411 wrote:
GizmoGuy411 wrote:On going problems with "N" not being pronounced as "North" STILL!

I'll try to test this issue more to resubmit it AGAIN to Waze.

The two other strange issues mentioned earlier are still not submitted to them, as testing has been tenuous at best lately with the ongoing zero byte TTS file returns as many of you have noticed in the beta clients.



Initial tests are not confirming the problem:

http://www.gizmoguy411.com/Waze/TTS/Gar ... wy%20N.mp3

http://www.gizmoguy411.com/Waze/TTS/New%20Jersey%20Tpke N.mp3

Could you provide segment Permalinks so they can also be tested?

After just clearing my TTS (cc@tts) again I'm still hearing "... Parkway enn" at this on ramp to the Bronx river parkway.

I believe there are others as well if you need more PLs, I can try to find them again.

Sent using Tapatalk for Android 4.4.2

GizmoGuy411 wrote:
dbraughlr wrote:Whether Louis XIV is read as lewis ex eye vee or lewis fourteenth, it won't be perfect.

I think we want C, D, I, L, M, V, and X pronounced as letters. It seems that Roman numerals are the exceptions and should require special notation if used at all.


While the logic that the Roman Numerals are the exceptions, and therefore should require special notations seems correct, we have to remember that we have already have set a precedence to use quotes around the letters N, E, S, and W, to get the them pronounced as letters instead of the cardinal directions.

Therefore we may need to follow suite for the letters used for Roman Numerals too.

Of course there are other conflicts to consider as well including: (examples using valid Roman Numerals only, and not every combination of the letters used in Roman Numerals)

CD = cd or 400 ?
CM = centimeter or 900 ?
DC = District of Columbia or 600 ?
MD = Maryland or 1500 ?
MI = Michigan or 1001 ?
MIX = Mix or 1009 ?
MM = millimeter or 2000 ?

So maybe Roman Numerals could use a period after them instead of quotes to differentiate them.

GizmoGuy411 wrote:
AlanOfTheBerg wrote:
sketch wrote:https://www.waze.com/editor/?lon=-90.18022&lat=29.99981&zoom=5&layers=1925&env=usa&segments=20949819 "to Clearview Pkwy N"

I tried 16 times to download the TTS for this segment and got empty files every time. Not sure what's going on here. I know with 100% I heard two different "Pkwy N"-ending segments pronounced with "north" so this is ... confusing/concerning. The TTS system appears to be pretty unstable right now.

Finally got it: https://www.dropbox.com/s/sxefwon98h5s2 ... _1.mp3.mp3

Question is, why isn't the app getting this same thing?


Here is the TTS audio file from that actual segment (rather than web TTS test) using the Android beta client:
http://gizmoguy411.com/Waze/TTS/Clearvi ... wy%20N.mp3

It still sounds correct, saying, "then stay to the right to Clearview Parkway north".

And here is the same segment TTS from the Android non-beta client 3.7.8.0:
http://gizmoguy411.com/Waze/TTS/Clearvi ... .7.8.0.mp3

It also sounds correct saying, "at Clearview Parkway north".

I'm beginning to wonder if the "cc@tts" command is not always clearing the cache correctly.

Note: I deleted my previous post and reposted this to Alan's post regarding this, and my addition of the non-beta TTS audio file.

"cc@tts" emptied the entire nuance Samantha folder 3 tines in a row for me.
I now get "N" pronounced as "north" on 3 different segments each of the three times.

TTS files from android production client.
Bronx River Pkwy N
Hutchinson River Pkwy N

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4339
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1979 times
Been thanked: 2174 times

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

Postby GizmoGuy411 » Sun Jun 08, 2014 4:58 pm

Kobes1878 wrote:


Hi all -

First off, great work @gizmoguy. I've been following this forum and cleared my cache as advised above. Here is another example of the "Enn" error getting on to the NJTpke over here. Id imagine a lot of these ramps would produce the same pronunciation.


I just tested your segment in both the current beta client and in the non-beta 3.7.8.0. client and both said "... north" for me.

However while testing I noticed something curious and troubling at this segment street named "Exit 4: SR-73 / Camden / Philadelphia":
url=https://www.waze.com/editor/?lon=-75.0722&lat=39.86048&zoom=5&layers=933&segments=66875972&env=usa

In the beta client, it incorrectly said "exit 4, ess arr 73, Camden, Phildelphia" and in the non-beta the same segment it correctly said "exit4, state route 73, Camden, Phildelphia ...
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 648 times
Been thanked: 427 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users