PhantomSoul wrote:I'm not sure if this has been resolved yet or not, but I'm still getting the letter N pronounced as the letter N (instead of North) when it is the last word of a name and follows either the word Pkwy or Tpke, as in Garden State Pkwy N or New Jersey Tpke N. I have not seen this happen with S/South when used the same way.

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?

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.18 ... s=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.

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.
http://img.tapatalk.com/d/14/05/02/ujuzyvuh.jpg
It said " Keep left at eye 87 South, Maj Deagan Expressway, Manhattan, Queens "

Sent using Tapatalk for Android 4.4.2

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/agfluap6dbfpp ... 3471-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.

AlanOfTheBerg wrote:

PesachZ wrote:...RFK Br is sounding like RFK branch
https://www.dropbox.com/s/7fphov5fayuoc ... 743-23.mp3

Did we ever get "Br" submitted to be "Bridge"?

AlanOfTheBerg wrote:

PesachZ wrote:

AlanOfTheBerg wrote: Did we ever get "Br" submitted to be "Bridge"?

it worked elsewhere I'll try to get another audio file

If you check the TTS testing file in the OP, "Br" is supposed to be "Branch" as a USPS standard. "Brg" is supposed to be used for Bridge.