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 AlanOfTheBerg » Thu May 01, 2014 12:20 am

PesachZ wrote:
AlanOfTheBerg wrote:Yes, noted in the thread with pkwy example specifically.

In the meantime should the name be changed to spell out 'parkway' or 'north'?

No. Honestly, it's been this way for quite some time. The impact to drivers is fairly minimal. Many more drivers are hearing "nebraska" instead of northeast. I've got an email in to the abbreviations queen at Waze as well as Noam, our US community manager to give us an update about it. Tomorrow is their last day before the weekend, so if I don't hear from them by 4am PDT, I will contact them again.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Thu May 01, 2014 6:16 am

I think that TTS was being updated this evening as I had several minutes of no street names at all, and then NE started saying "northeast."
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Fri May 09, 2014 4:32 pm

I now have more problems with "N" being pronounced "enn" instead of "north" on segments which have never had a problem before. It's getting worse instead of better. And communication from Waze has all but completely disappeared again. Despite assurances to the contrary.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Fri May 16, 2014 9:51 pm

qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow

'X' should be sufficient to say "ex" instead of "tenth."
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Fri May 16, 2014 9:51 pm

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.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Fri May 16, 2014 9:52 pm

"St" is properly saying "street" in all positions in my testing.
"St." is properly saying "saint" in all positions in my testing.

There still could be anomalies around/after other custom abbreviations.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Mon May 19, 2014 1:45 pm

bowieb2 wrote:
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?

As noted above by bgodette, clearing tts cache is done by navigating to cc@tts (case sensitive).
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Mon May 19, 2014 1:53 pm

Look up codes in the wiki for more. :)
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Thu May 22, 2014 3:06 pm

I've verified that today, the fix is in place for "N". At least one test case run so far, "I-5 BUS N" (fictitious street) works correctly and is voiced "north" instead of "enn."
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

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

Postby AlanOfTheBerg » Thu May 22, 2014 4:21 pm

Pkwy and Expy abbreviations with N after are also now working just fine. Here are three tests:

Expressway Exit
I-5 BUS N
Parkway N
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 8.4 | Waze v4a
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23340
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1057 times
Been thanked: 4385 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users