MGODLEW wrote:I discovered an issue with TTS the other day for this "Place" Magisterial District Court 11-3-07 Its official name is Eleven Three Zero Seven however waze pronounces 11-3-07 as Novermber 3rd, 2007. "Arriving Magisterial District Court Novermber 3rd, 2007"

SeZAKxing wrote:Any suggestions for keeping editors form changing Psge (Passage) to Page?

russblau wrote:Is there any way to get Waze to pronounce "HOV" as individual letters instead of as "hove"?

GizmoGuy411 wrote:Your help is needed!

Several reports have been received that certain roads with the "Dr" abbreviation have been voiced by TTS as "doctor" instead of "drive", and only intermittently.

In the Boston area it has happened with "Memorial Dr W" and I believe "Memorial Dr E".

In New York City it has happened with "FDR Dr N" and possibly with "FDR Dr S".

This does not seem to happen all the time.

My suspicion, is that it MAY be occurring during periods when the abbreviation "Dr" is being in heavy use by the TTS server. So if it is rush hour on the west coast and a lot of "Dr" abbreviations are being used, then it COULD also happen on the east coast at the same instant.

In order to help Waze determine the issue, we need to provide them with examples with the following infomation:

- The WME permalink with the segment that you heard the TTS for selected. (Not where you were at the time you heard it, but the segment that was being spoken in the TTS instruction.)

- Your time zone.
- A copy of the actual TTS file from your mobile device.
- The timestamp of the TTS file.

Acquiring a copy of the TTS file and its timestamp can be accomplished as follows:
- For Android devices, download the "ES File Explorer File Manager" app for your device.

- For iOS devices, download a program such as "iFunBox" (no jailbreak needed) to your Mac or Windows computer, and connect your device to your computer via a cable. You may also be able to use Wifi with some programs such as iFunBox.

- Navigate to the location in your device where the TTS files are stored.

Android:
Local/waze/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Local/waze/tts/database/local_nuamce_8_mp3_Tom_Male/

iOS:
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Samantha_Female/ or
Connected Devices, [your device name], User Applications, [Waze]//Library/Caches/tts/database/local_nuamce_8_mp3_Tom_Male/

Once you have found the file, please either upload it to cloud space such as Dropbox or Google Drive and share the link, or just sent it to my Waze@GizmoGuy411.com email address as an attachment.
(It is not possible to sent via a Private Message.)

Kayos_On_The_Road wrote:For the last few months (I don't know exactly how long as I don't take this route often) this exit has been voiced as "to highway ninety one eh en, annacis island". Segment name is "to Hwy 91A N / Annacis Island"

https://www.waze.com/editor/?env=usa&lo ... s=59598325

and this one as "exit eleven, highway ninety one eh en, annacis island, new westminster". Segment name is "Exit 11: Hwy 91A N / Annacis Island / New Westminster"

https://www.waze.com/editor/?env=usa&lo ... s=59586780

Do these segments need to be changed to have the N voiced as "north"?

Thanks,
Kayos

voludu2 wrote:How responsive are they to a TTS test interface, similar to the demo nuance provides on its website?

This would allow you to input strings and listen to the results immediately.

It would make it easier for them to provide the service they want to provide.

beej666 wrote:i still don't understand how the fix gets made. i've been made to understand that somebody from the Google Waze team will need to fill out some sort of request upstream with the TTS provider. who is that person? how does my request get in their inbox?

• The process start with you posting here. (Done)
• Some research into the popularity of the name, and any potential conflifts with other names. Also research on proper pronunciation in different regions. (If a name is pronounced differently in doesn't locales it likely won't be fixed either since it will always be wrong somewhere.)
• Once it's determined a fix is required, a group of champs who spend a lot of time on this project (incl. GizmoGuy411, sketch) can then craft a string that will sound right when read by the TTS engine, and test it in various contexts. (Bueno might be converted to "bwen oh" for example)
• Code is developed to determine when the name should be replaced in context.
• That pair of name and converted string with the filtering code for when to use it is then submitted to Waze staff for inclusion in their TTS software as a custom abbreviation.

DwarfLord wrote:In a test this evening, TTS (iPhone, v3.9.4, Samantha) pronounced "Cañada" as "Canada". Which sounds wrong -- shouldn't it say Canyada? -- until one remembers that until quite recently TTS pronounced it "Ca-plus-minus-ada".

I don't know if this is in any way associated with the new version of the app. But it suggests we should finally be able to use ñ in street names without fear of egregiously weird pronunciation. Yay!

DwarfLord wrote:

PesachZ wrote:Can you tell me the full exact street name you tested?
When I tested it sounded like caada street, which is still better then ca ± ada Street.

Odd! I used "Cañada Rd" for the test. It was on a PR type road, and the announcement was for a right turn from a PS onto the PR. Pretty clearly sounded like Canada to me, but admittedly I've only run the test once in that one location.