SteveInArk wrote:

PesachZ wrote:

SteveInArk wrote:I've been "off-internet" for 3 days. I've looked, but not seen any comments on the forum, or here, that JANE is pronouncing all "leading" directions as the letter itself.

IAW, "N Main St" is pronounced alled "N" Main Street", not "North Main Street".

Sorry if it's posted elsewhere and I've just missed it.

Can you give us a permalink to the exact segment causing this failure?

Sent using Tapatalk for Android

I'm not on the road now, so no exact PL that I could post with confidence. But EVERY instance of driving I've done, everywhere, since JANE was defaulted to my phone app, has been that way. No exceptions that I have noted, here in Arkansas.

EDIT: Wait! I did navigate down SE and SW 14th today, in Bentonville. It announced SW 14th as such, not "southwest". Hope that helps.
https://www.waze.com/editor/?env=usa&lo ... s=65215588

PesachZ wrote:The double letter direction (SW) we are looking into now, but the single letter Cardinal directions have all been working for us in testing and on my drives. Perhaps you need to clear your local tts cache and see it it is still happening. Search on you app as if searching for a destination. Type in cc@tts and press search. If it still is happening after that please send us the exact location where it happens so we can try to reproduce it.

Sent using Tapatalk for Android

The double cardinals (NE, NW, SE, SW) should all be working properly now. Please clear your TTS cache (search for cc@tts) and try it out again. If the issue persists please advise us. Thanks

Sent using Tapatalk for Android

BarfmanTheGreat wrote:I have a user reporting that voice said Drive instead of Doctor for this segment:
https://www.waze.com/editor/?env=usa&lo ... s=83508873
called "Dr. Martin Luther King Jr St S"

I see that Jr probably needs a period, but why would Dr. say drive?

They were turning right to go north on that segment, and they said it was the default voice.

Can you confirm this has been fixed now please?

Sent using Tapatalk for Android

taco909 wrote:"Object on road ahead" still sounds like "I objEct, your honor"
"Madre" is pronounced "Mad-reh" rather than "Mod-ray"

Object on road is already on the to-do list, I think madre is to, if not it will be now

SocalToe wrote:Still happening with N&W (I assume it's happening with E&S)

It's North not 'N'

West not 'W'

etc. (haven't hit any E or S streets lately)

This happens on ALL streets that I come across with N & W......



I've already cleared the TTS cache...........

What is happening? Can you give PL to any specific streets with the error?

Sent using Tapatalk for Android

SocalToe wrote:Here's 2

to Ming Ave W, Bakersfield, California

https://www.waze.com/editor/?env=usa&lo ... ts=6598585

to SR-99 N, Bakersfield, California

https://www.waze.com/editor/?env=usa&lo ... ts=6606393


I might be able to give you a whole geographical area tomorrow when I return to Inglewood
(I was constantly getting 'W' instead of west, but that was before I cleared the cache)

I tested both of these now specifically, and they both said it correctly.

"Keep right to Ming Avenue West"

"Turn left to ess are ninety nine north"

Either there is a problem with your client, or somehow your TTS is not being cleared.
When you search for cc@tts, are you seeing a confirmation popup which says your TTS cache has been cleared?
If yes, and after that you still hear this problem, please submit debug logs so we can investigate further. (Put your app in debug mode before the drive so it can capture the events.)

Instructions for sending debug logs
(You don't have to open a support ticket, we will handle it, just let us know after you sent the logs.)
We need to know exactly what time you heard the wrong prompt, so they can find it in your logs.

Sent using Tapatalk for Android

I'm going to go out on a limb and say this issue is somehow related to your client. Can you please submit debug logs, and note here what time you heard the wrong prompts. I will ask the devs to check it.

Also please confirm which version of the Waze app you are running,
Your device model,
OS version #,
and which voice you're using.

Thank you, hopefully we can figure it out.

Sent using Tapatalk for Android

SocalToe wrote:I'll get you some debug logs when it happens again. (I just turned debug on)

3.7.8.0

On android 2.3.4

It's Jane now. Worked before when I had Samatha

Is there a specific reason you are not upgrading to the latest versions (were at 3.9.5.0 now)? I now have a good reason to believe this is client related. I can't say for certain without the logs, but I'm pretty confident this is happening because you have an outdated client.

Sent using Tapatalk for Android

SocalToe wrote:Old phone, not enough memory to download update.

Might be able to squeeze in a download by bypassing play store..........

Do you have a link that I can download directly from?

A Google search for [Waze android download] or similar will yield several results, I don't vouch for the validity of any of them though.

It should be 37.56MB, this version was published on July 7.

Sent using Tapatalk for Android

Regardless a fix has been pushed to make the cardinals backwards compatible again. So you should start hearing North South... In the next few days, even without upgrading.

Sent using Tapatalk for Android

Slightly off topic, but just trying to help out. Here is a certified download source for the latest android app version 3.9.5.0
Md5 Checksum: b2d09e1ba4b8fd8b3479e7c130cdd72a

There were some bugs on some devices causing crashes, if that doesn't work for you, you can use 3.9.4.0.

Sent using Tapatalk for Android