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 bowieb2 » Tue May 13, 2014 4:32 pm

I just cleared the cache for the app. I'll see what it does at lunch and then send you a map link if the problem is still there.
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Mon May 19, 2014 1:42 pm

AlanOfTheBerg wrote:
bowieb2 wrote:Any update on NE being pronounced "Nebraska"? My office is currently on the corner of "Nebraska 17th Court" and "Nebraska 14th Avenue" according to Waze.

This is a cached street name. NE was fixed quite a while ago.


I am still getting the Nebraska pronunciation as of this morning. I cleared the cache before I left the house (Application Manager --> Waze --> Clear Cache). Is there something else I need to do?
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Mon May 19, 2014 1:52 pm

AlanOfTheBerg wrote:As noted above by bgodette, clearing tts cache is done by navigating to cc@tts (case sensitive).


Ah! I must have missed that. That's an odd way of doing things. I would have expected a button in the configuration or something.

Hopefully that will have fixed it. I'll test it in the morning (navigation does not speak those road names on the way home).
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Wed May 21, 2014 1:11 pm

bowieb2 wrote:
AlanOfTheBerg wrote:As noted above by bgodette, clearing tts cache is done by navigating to cc@tts (case sensitive).


Ah! I must have missed that. That's an odd way of doing things. I would have expected a button in the configuration or something.

Hopefully that will have fixed it. I'll test it in the morning (navigation does not speak those road names on the way home).


That worked! Thanks for the help!

Bowie
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bretmcvey » Sat Aug 22, 2015 1:58 am

A couple of pronunciation issues I've encountered with the Jane voice:
  • Burt St - incorrectly pronounced as "Bear-t Street" but should be "Bir-t Street"
  • Ashland - incorrectly pronounced as "Eyes-Land" but should be "Ash-Land"
Country Manager: USA / State Manager: Nebraska
Areas of Focus: Nebraska, Iowa, Kansas, South Dakota, North Dakota, Wyoming and NW Missouri

Image
bretmcvey
Country Manager
Country Manager
 
Posts: 214
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 14 times
Been thanked: 48 times

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

Postby bretmcvey » Sun Aug 23, 2015 1:20 am

PesachZ wrote:
bretmcvey wrote:A couple of pronunciation issues I've encountered with the Jane voice:
  • Burt St - incorrectly pronounced as "Bear-t Street" but should be "Bir-t Street"
  • Ashland - incorrectly pronounced as "Eyes-Land" but should be "Ash-Land"

Please provide examples where you've heard it wrong. Specifically with Ashland it has been reported before but is not always said wrong, it depends on the surrounding context. Examples and PLs are very important.

Sent using Tapatalk for Android


The example permalinks to the WME for each were linked at the start of each bullet point, do I need to provide something else or in a different format?
Country Manager: USA / State Manager: Nebraska
Areas of Focus: Nebraska, Iowa, Kansas, South Dakota, North Dakota, Wyoming and NW Missouri

Image
bretmcvey
Country Manager
Country Manager
 
Posts: 214
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 14 times
Been thanked: 48 times

Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Postby BrianCanFixIT » Sun Mar 04, 2012 4:51 pm

I've just encountered a sign with "Drwy" for Driveway. so I guess the other permutation for this would also be valid: drwy, drway.
Area Manager: Sacramento & rural California
iPhone 4s, iOS 5.0.1 JB
BrianCanFixIT
 
Posts: 37
Joined: Sun Dec 19, 2010 10:58 pm
Location: Northern California
Has thanked: 0 time
Been thanked: 0 time

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

Postby Bruce1224 » Thu Jul 17, 2014 3:23 pm

It's rare to see roads using just the letter "i" in the name but I have seen a couple.

I found a UR indicating that a county road, "CR-I-7" (that's the capital letter 'I') was pronounced "Interstate 7" by Waze tts directions. Can someone confirm if this can be alleviated by labeling the road "CR-'i'-7" similar to the convention, e.g., CR-'e' ?
Image
Bruce1224
Map Raider
Map Raider
 
Posts: 71
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 29 times
Been thanked: 6 times

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

Postby Bruce1224 » Fri Jul 18, 2014 1:22 pm

Re: the reply from Sketch two posts back -
I was able to drive to a county road late yesterday without going too many miles out of the way, properly labeled "CR-I" and tts did indeed pronounce it correctly as "eye". I'm too far from the road with the UR to check it out anytime soon, which is labeled "Rd I-7" but I put a message on the UR asking the reporter to confirm what he heard.
Image
Bruce1224
Map Raider
Map Raider
 
Posts: 71
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 29 times
Been thanked: 6 times

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

Postby Bruce1224 » Tue Aug 05, 2014 8:56 pm

Re: the letter i in street names

Regarding how tts says roads with the letter i as a part of the name, a couple weeks ago I wrote about a UR I saw where the reporter said that "Rd I-7" was called "interstate 7". Since it's unlikely I'll get to drive to that road to check it due to it's distance, I decided to take advantage of the plentiful farm land in Indiana where I am to test a few alternatives. I created segments of 3 different roads at least several miles apart in the fields of unsuspecting farmers. Each road started "CR-xxx" and tts called each one "County Road". No surprise there.

Here's what I heard for the rest of the label, using single quotes or a period after the letter i:

CR-'I'-7 was pronounced "eye minus 7" - I didn't expect it to call the hyphen "minus".

CR-I.-8 was pronounced "eye minus 8", but with a distinct, short pause after the letter i as though it was paying attention to the period.

CR-I-4 was pronounced correctly as "eye 4"

This last one is consistent with what Sketch said. I believe the tts pronunciation would be the same whether the 'CR' is separated from the letter and/or number by either a space or hyphen, but in my little test the single quotation marks or period didn't help. I didn't get a reply from the reporter of the UR I saw, so I didn't get anything confirmed from them.
Image
Bruce1224
Map Raider
Map Raider
 
Posts: 71
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 29 times
Been thanked: 6 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users