Good news!

As a result of our 2013 Waze Champ Global Meet-Up, I am now in direct contact with Waze staff in regards to the topics covered in this forum thread.

I have submitted an initial issue that needs to be resolved regarding dual TTS issue where there is a difference between the TTS output during a route vs what is said at the destination.

The list of ten things for them to consider that was submitted last year, will be submitted again once the issue above is resolved.

The reason for this is that testing for the other issues will be less complicated once there is only one TTS result, and not two!

Ok... just slightly off topic, but have you heard that the person behind "Samantha", our favorite Waze TTS voice product from the company Nuance here in the US has finally revealed her true identity?

Her name is Susan Bennett from the Atlanta area.

The story broke on CNN, a couple days ago, when she revealed that she was the voice of Siri on iOS products.

So if want to see who sometimes misdirects you in unfathomable ways, check out this story, along with the accompanying video.

I think I like hearing our Samantha talk even more now!

CNN Article: http://edition.cnn.com/2013/10/04/tech/ ... one-voice/

We'll I could be wrong. But from reading the news articles, I assumed that the Samantha voice was Siri. Unless Siri was a custom voice only used for iOS?


Sent from my iPad using Tapatalk - now Free

Thortok2000 wrote:Weird bug happened today.

I set a destination on Casey Avenue. When it said to turn onto it, it said Casey Avenue. When I arrived at my destination, it said 'Casey Ave', like the word ave, rhymes with have. That was weird. Any way to fix?

This is a known issue that Waze is working on. Quite a few destinations are pronounced different than what is said in route. Look at the spreadsheet linked in the opening post of this thread to see several examples.

orbitc wrote:I have a few instances as well:

to Garden State Pkwy N wasn't correct. It read as "enn" not as "North"
Also, it's reading "Dr" as Doctor.

Is "Dr" being pronounced as "Doctor" wide spread or isolated?

Can you send me some examples?

I want to know if there is any correlation to the occurrence of "Sulgrave Dr" being pronounced as "Sulgrave Doctor" that we have found before in multiple locations.

4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category.
For example: California would be abbreviated to C.A. not CA and Victoria to VIC.

If I am reading this correct, I have an exception to this.

We have been pushing for 2 years now for Waze to adopt the USPS (and others) two letter (without punctuation) for the US States, and Canadian Provinces.

Will chime in as soon as I have some time to address several recent posts.

Thortok2000 wrote:The main bug I have is that the TTS given of a destination when you've reached it seems to use a different TTS than the TTS of turn instructions.

As a turn instruction, 'Ave' is always Avenue, but as a destination, it rhymes with 'have.' =/

If you look at the list, you will see two columns for TTS results. While not many have been retested for both results, a few in the list are rather interesting for their differences.

Recently I tried to check the dual file results as I had done before, however was only able to find the files prefixed with "at" in my Android device.

AlanOfTheBerg wrote:The map update cycle is failing on the NA server, but if there are existing segments which have the following abbreviations, please find a way to re-test client TTS and post the results:

Dr.
Penn
BUS
St.
Jr.
CR-###
Intl
Int'l
Nat'l
SH-###
Thwy

Easier said than done. Will email you with developments in the the lack of progress in testing.

CBenson wrote: ...
I still get "Street Stephens Church Road" here without the period. (with Samantha)

Are you clearing your TTS cache before each test?