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.

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

Postby GizmoGuy411 » Wed Jun 04, 2014 4:49 am

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?
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Wed Jun 04, 2014 6:19 am

qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow


Although I had recently submitted the "Malcolm X" issue to Waze, I have since removed the submission as there is a larger issue with Roman Numerals that needs to be addressed. In another thread elsewhere, I posted the following:

GizmoGuy411 wrote:While testing other TTS issues, the "Malcolm X" issue was mentioned again in the TTS test thread.

Here are the very inconsistent results I found testing just a few Roman Numeral examples:

Fred IV = Fred eye vee
Fred X = Fred ex
Fred XIV = Fred fifth
Louis IV = Louis eye vee
Louis X = Louis ex
Louis XIV = Louis fifth
John IV = John the forth
John X = John the tenth
John XIV = John the four-teenth
Malcolm IV = Malcolm the fourth
Malcolm X = Malcolm the tenth
Malcolm XIV = Malcolm the four-teenth
Mark IV = Mark eye vee
Mark X = Mark ex
Mark XIV = Mark fifth

Curiously the results for [Malcolm X] are correct for Roman Numeral usage, but wrong for what we need for that particular name,whereas other names with "X" say "ex" as in the letter x.

We may need to use [Malcolm "X"] to get the results we want, in order to differentiate from Roman Numerals usage. This would be consistent with the use of quotes around N, E, S, and W to get the letters pronounced instead of the cardinal directions.

Also note that for some names "XIV" is pronounced "fifth" and other others "fourteenth".
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

Re: Roman numerals

Postby GizmoGuy411 » Wed Jun 04, 2014 6:55 am

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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

Re: Roman numerals

Postby GizmoGuy411 » Wed Jun 04, 2014 3:10 pm

dbraughlr wrote:
GizmoGuy411 wrote:Therefore we may need to follow suite for the letters used for Roman Numerals too.

From what you listed, there are thousands of them. That's clutter.
What range do you really intend to cover?

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

That doesn't seem likely, at least not if you intend to cover a range beyond 1 to 30.

What's wrong with using Louis the 14th instead of Louis XIV.? If anything, our experience with N/E/S/W should tell us that it was a bad precedent that should not be expanded.


I agree with sketch in that I am really not very concerned about Roman Numerals and that the letters themselves are more important at least for North America using the English voices.

What I am MORE concerned with is why these variations exist in the first place and if they are indicators of some bad RegEx that needs to be addressed at the Waze end, as other parts of the world may need Roman Numerals.

So any submission I may to Waze at this point will be to just point out the inconsistencies. We have plenty of one off issues with TTS pronunciation that is something that may be able to be adjusted in the future via the editor on an individual basis.

Issues like "Sulgrave Dr" being pronounced in the past as "Sulgrave Doctor" however where of concern as in this case it may have been indicative of a wider problem that could effect other names as Doctor vs Drive was more of a global concern.

Actually I don't think there are many more instances than those I listed as potential conflicts with Roman Numerals. This was limited to valid Roman Numerals, not simply every possible combination of letters used in Roman Numerals. I'll edit that in the prior post.
Not sure I agree with you that there are thousands of RN combinations, as many combinations of the letters in RNs are not actually valid RNs.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

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

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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 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 ...
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Fri Jun 13, 2014 5:09 am

I've edited the BIG TTS List to correct an error regarding the sources of abbreviations for Bridge. The chart below also shows the corrected abbreviation sources and current usages.

Please note that nothing has ever been submitted to Waze for change for "Branch" or "Bridge". The current Waze abbreviation usage shown below is how it has always been. That implies that Nuance matched the USPS over MUTCD for their abbreviation choices for their mobile customized version of their Vocalizer TTS product. This does not mean that we can't fix it for Waze.

I agree that we should probably follow actual signs, along with MUTCD before USPS and Canada Post as much as is practical when there are conflicts.

I proposed the change below if we can confirm that signs use "Br" for "Bridge" and that there is more use of "Bridge" than "Branch".

Abbreviation Source - Word >BranchBridge
MUTCDn/aBr
USPS StandardBrBrg
USPS Common BrnchBr
Canada Postn/a n/a
Waze CurrentBr
Brnch
Brg
Waze Proposed
Change
remove Bradd Br
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Thu Jul 10, 2014 3:40 pm

DwarfLord wrote:While perusing the "big list" I came upon a misspelling. It should be "crescent" with a c after the s. This is so minor it hardly seems worth mentioning, but it is a reference...


Done.
Thanks. Corrections however small appreciated.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Thu Jul 24, 2014 4:29 am

KB_Steveo wrote:
PesachZ wrote:Try "CR-C T" it should give you the results you want.
I was just doing some testing, thanks though. I only mentioned it since it didn't look like it had been confirmed in the list.


Try "CR-C.T." to force it tp pronounce the letters as we have done that for other letters that we would like pronounced.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users