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

This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby PhantomSoul » Tue Aug 13, 2013 2:58 pm

Does anyone know if the common abbreviation "Twp" gets expanded to Township?
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby PhantomSoul » Mon Nov 11, 2013 5:20 pm

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.


I've seen both happen, but only intermittently and only in some places. It seems like sometimes in some places, it would say Garden State Parkway North and other times in other places Garden State Parkway En.

Also, any updates on Br being read as branch despite many places using Br to mean Bridge? Or should we be using Brg for bridge, even though it conflicts with local signage?
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby PhantomSoul » Wed Nov 13, 2013 4:36 pm

qwaletee wrote:
GizmoGuy411 wrote:
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.


Yeah, love those. Been bitten by them a few times. And why I say bite, I mean by a fit of laughter.

I also saw a UR flaming Waze for 9W. I'm not sure exactly what Waze spoke, but the complaint was that there are two separate NY highways, 9 and 9W, and blah blah blah east and west of Hudson River. UR was on 9W, maybe Waze said "to route 9 west," which he took to mean "state route 9, direction west."

There ought to be a way to flag a piece of text as being "non-abbreviated," so that Waze pronounces it exactly as-is. Or, alternatively, a way to type in the pronounced version of a segment name, so that Waze speech in fine tuned for a problematic reading.


I've actually seen exactly what you were talking about when I was up in Newburgh last week. My guess would be that someone (I didn't look at the segments in WME) made the road US-9 instead of US-9W (what it probably should be) in order to get the shield to render correctly. Currently shields do not draw correctly for any highway that has a letter as part of its number (this occurs a lot in New York). In any case, this is a bad reason, because the shield rendering engine is being fixed to accommodate highway markers with letters on them.

Also, I believe at one time the TTS would read US-9W as You Ess Nine West, so the W may have been removed to prevent confusion on the road that actually runs north/south. I think that's supposed to be fixed now - so as if the W is in the same word (not separated by a space) as a highway number (in this case, US-9), it will be read as W and not West. So I would imagine the road should be changed back to US-9W.

Any thoughts from Hudson Valley area managers?
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby PhantomSoul » Thu Nov 14, 2013 2:43 pm

To further the 9W phenomenon, I've seen the portion of this road in New Jersey named US-9w, with a lowercase w. I'm not sure, however, if this is a workaround for the west problem or whether it even causes the w to be read as a w instead of west.
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby PhantomSoul » Fri Dec 27, 2013 6:04 pm

Is it possible that frequently encountered TTS data - like, say, reading the same phrases over and over again because you keep driving to work the same way - causes that TTS data to be accessed from a local cache?

In an unrelated observation, we seem to have a bunch of Tnl abbreviations on the Turnpike in northern NJ being read as its letters (tee en el), as opposed to Tunnel. This makes the Turnpike's references to the Holland and Lincoln Tunnels sound really weird. Is this a known bug/limit of the TTS and the Tnl abbreviation?
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby PhantomSoul » Wed Jan 01, 2014 1:56 am

I'll try the new voice if you still need testers. iPhone here.
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 565
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 80 times

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

Postby pydagenais » Tue Jul 23, 2013 6:24 pm

Hi, in the client version "est" is an abbreviation for "estate" but in the quebec province in canada some roads use the term "Est" meanning "East" in english,...

i can see 2 solutions... and 1 option

1- Remouve the abbreviation and change all the recurrence of "est" for "estate" in all north america !!

2- Miss spelling the word "Est" so it dosent come as an error to the ear's of wazers but typing error... but for waze immage

3- Simply add an control ponctuation that confirm that an abbreviation is in place

This error is also on page 19 of this topic !!

Thanks
AM Grand-Montréal / Rive-Nord
Nokia C7-0 / waze v2.0
ImageImageImage
http://sign.wme-tools.com/home/
pydagenais
 
Posts: 225
Joined: Tue Apr 09, 2013 6:56 pm
Location: Montréal, Qc, Canada
Has thanked: 35 times
Been thanked: 17 times

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

Postby qwaletee » Mon Nov 04, 2013 10:43 pm

Br is commonly used for Bridge in my area. Disconcerting to frequently be told to bear left onto XYZ Branch. Example: https://www.waze.com/editor/?lon=-74.20 ... s=31973592

The other segments in the area leading to the Goethals have mostly been changed to say Brg instead of Br, but the fact remains that all the signs actually say Br, and any editor attempting to duplicate the text of the signs is bound to introduce more Br's.

It would be interesting to know the distribution of signs using Br for Bridge versus using Br for Branch, so that we could know which to assign causing the fewest issues.
Active in New York and New Jersey (USA)
qwaletee
Waze Mentor
Waze Mentor
 
Posts: 376
Joined: Wed Feb 13, 2013 1:42 am
Has thanked: 51 times
Been thanked: 59 times

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

Postby qwaletee » Wed Nov 13, 2013 3:17 pm

GizmoGuy411 wrote:
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.


Yeah, love those. Been bitten by them a few times. And why I say bite, I mean by a fit of laughter.

I also saw a UR flaming Waze for 9W. I'm not sure exactly what Waze spoke, but the complaint was that there are two separate NY highways, 9 and 9W, and blah blah blah east and west of Hudson River. UR was on 9W, maybe Waze said "to route 9 west," which he took to mean "state route 9, direction west."

There ought to be a way to flag a piece of text as being "non-abbreviated," so that Waze pronounces it exactly as-is. Or, alternatively, a way to type in the pronounced version of a segment name, so that Waze speech in fine tuned for a problematic reading.
Active in New York and New Jersey (USA)
qwaletee
Waze Mentor
Waze Mentor
 
Posts: 376
Joined: Wed Feb 13, 2013 1:42 am
Has thanked: 51 times
Been thanked: 59 times

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

Postby qwaletee » Fri Nov 15, 2013 4:04 pm

PhantomSoul wrote:I've actually seen exactly what you were talking about when I was up in Newburgh last week. My guess would be that someone (I didn't look at the segments in WME) made the road US-9 instead of US-9W (what it probably should be) in order to get the shield to render correctly. Currently shields do not draw correctly for any highway that has a letter as part of its number (this occurs a lot in New York). In any case, this is a bad reason, because the shield rendering engine is being fixed to accommodate highway markers with letters on them.

Also, I believe at one time the TTS would read US-9W as You Ess Nine West, so the W may have been removed to prevent confusion on the road that actually runs north/south. I think that's supposed to be fixed now - so as if the W is in the same word (not separated by a space) as a highway number (in this case, US-9), it will be read as W and not West. So I would imagine the road should be changed back to US-9W.

Any thoughts from Hudson Valley area managers?


I figured out what was going on. Here are my findings.

1) In the West Point area, the highway is labelled as US-9w, with a lowercase W, no space.
2) On the livemap, that shows as labelled.
3) In the Waze app map it shows a shielded 9, no W
4) In the Waze app route highlighter, it shows as 9 in a box, no W
5) In direction lists, both browser and app, it shows as US-9w
6) I don't see anywhere that it is milabelled as US-9 withoyt the W, sorry PhantomSould
7) Speech? Dunno, I wish there was a way to force Waze to speak out a series of directions without traveling, so we could test this sort of thing. Ditto getting a route in the editor using the unposted changes, so we can verify that we produce good results without having to wait for an update (especially since if we found out its wrong, that means another day's cycle to fix, frustrating for other motorists, frustrating for the editor). But 'm off topic now.

So basically, the user's problem was a bug in way that I was not aware of for lettered shields.
Active in New York and New Jersey (USA)
qwaletee
Waze Mentor
Waze Mentor
 
Posts: 376
Joined: Wed Feb 13, 2013 1:42 am
Has thanked: 51 times
Been thanked: 59 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users