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 kentsmith9 » Wed Feb 05, 2014 1:01 am

It looks like one of our Australian editors was making some changes for the Australian pages and then came in making changes here as well.

sketch wrote:
bgodette wrote:
qwaletee wrote:That page needs serious copyediting.
Go right ahead, and be sure to submit it to a new page or sandbox so others can review your work.

It's not copyediting that page needs, it's a full rewrite, and maybe just a removal of that first section. Those are not the rules, at least in the US, and they don't belong on a country-nonspecific page. (They are, indeed, also pretty difficult to understand.)

I would agree and I am fine if qwaletee wants to take a first crack at it.

I created a separate page linked to the original just for easy locating if we all forget about it. Whoever holds up their hand first should be given initial control over the page and then ask for input from this forum. I have temporarily assigned it to qwaletee, but if someone else steps up or wants it just change the name at the top of the page linked above.

Once we all agree or get enough consensus we can just cut and paste the new content over the old. No need to track our session edits before the final. The history will hold the original page changes for reference.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 4378
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 945 times
Been thanked: 1101 times

Re: Forest Service and Bureau of Indian Affairs

Postby kentsmith9 » Tue Feb 25, 2014 4:58 am

dbraughlr wrote:There are prefixes like "I-" and "US-" don't get special pronunciation.
For all these that you propose, I would be fine with just the letters being pronounced.

Otherwise, what the harm is there in shortening them?
  • IRR-xxx → "Reservation Road".
  • ITR-xxx → "Tribal Road".

Are you proposing two possible options for "IRR-123" to be pronounced either
1. "Eye Are Are One Two Three"
or
2. "Reservation Road One Two Three"

Was there a desire not to have it say the whole thing, or were you just offering ideas to shorten it?
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 4378
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 945 times
Been thanked: 1101 times

Re: Forest Service and Bureau of Indian Affairs

Postby kentsmith9 » Tue Feb 25, 2014 9:35 pm

bgodette wrote:
kentsmith9 wrote:
dbraughlr wrote:There are prefixes like "I-" and "US-" don't get special pronunciation.
For all these that you propose, I would be fine with just the letters being pronounced.

Otherwise, what the harm is there in shortening them?
  • IRR-xxx → "Reservation Road".
  • ITR-xxx → "Tribal Road".

Are you proposing two possible options for "IRR-123" to be pronounced either
1. "Eye Are Are One Two Three"
or
2. "Reservation Road One Two Three"

Was there a desire not to have it say the whole thing, or were you just offering ideas to shorten it?
Perhaps the reasoning is much like with County Roads. The generic is just County Road even tho they may be signed or locally known as <Countyname> County Road ###.

Yes that does make sense. So I would support number 2 based on that logic for consistency.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 4378
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 945 times
Been thanked: 1101 times

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

Postby khaytsus » Sun Nov 11, 2012 11:57 pm

Anyone know the proper abbreviation for Sideroad? I thought it was Srd and had been using this, but that is pronounced "S R D". Not seeing it in the spreadsheet either.
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 856
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

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

Postby khaytsus » Tue Nov 13, 2012 12:22 am

jasonh300 wrote:
khaytsus wrote:Anyone know the proper abbreviation for Sideroad? I thought it was Srd and had been using this, but that is pronounced "S R D". Not seeing it in the spreadsheet either.


Is this really a street type? Post an example.

In my case, it's usually when a street has a side road which leads to businesses, or the road has been replaced with a wider road and the original road left paralleling the new road.

http://goo.gl/maps/K9k52 (ignore the name, Google and Bing both have it as the same name of the main road, but other sources have it as "Srd".

http://goo.gl/maps/2KZQh (this case they have the name right).

http://en.wikipedia.org/wiki/Side_road
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 856
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

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

Postby khaytsus » Wed Nov 14, 2012 1:01 am

GizmoGuy411 wrote:
khaytsus wrote:Anyone know the proper abbreviation for Sideroad? I thought it was Srd and had been using this, but that is pronounced "S R D". Not seeing it in the spreadsheet either.


Remember that the list is a test to learn every possible abbreviation that the TTS knows, and not necessarily a recommendation of what to use.

I consider it the authoritative list, since we don't otherwise get one from the Waze folks ;) But as you say, no abbreviation so I went ahead with "Side Road". Not that many in town, just "S R D" isn't good either. :)
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 856
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

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

Postby Kobes1878 » Fri Jun 06, 2014 9:10 pm

PesachZ wrote:
GizmoGuy411 wrote:
GizmoGuy411 wrote:On going problems with "N" not being pronounced as "North" STILL!

I'll try to test this issue more to resubmit it AGAIN to Waze.

The two other strange issues mentioned earlier are still not submitted to them, as testing has been tenuous at best lately with the ongoing zero byte TTS file returns as many of you have noticed in the beta clients.



Initial tests are not confirming the problem:

http://www.gizmoguy411.com/Waze/TTS/Gar ... wy%20N.mp3

http://www.gizmoguy411.com/Waze/TTS/New%20Jersey%20Tpke N.mp3

Could you provide segment Permalinks so they can also be tested?

After just clearing my TTS (cc@tts) again I'm still hearing "... Parkway enn" at this on ramp to the Bronx river parkway.

I believe there are others as well if you need more PLs, I can try to find them again.

Sent using Tapatalk for Android 4.4.2


Hi all -

First off, great work @gizmoguy. I've been following this forum and cleared my cache as advised above. Here is another example of the "Enn" error getting on to the NJTpke over here. Id imagine a lot of these ramps would produce the same pronunciation.
ImageImageImageImageImage
State Manager | New Jersey, USA
Kobes1878
Map Raider
Map Raider
 
Posts: 616
Joined: Thu Jun 19, 2014 11:37 pm
Location: South-Central NJ, USA
Has thanked: 173 times
Been thanked: 234 times

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

Postby kodi75 » Sun Aug 03, 2014 4:48 pm

Cord St near Middle River, MD is pronounced as "County Road" in TTS.
Reporter on July 31, 2014
The text to voice says "county road street"


I'm aware that "Co" (and "CR") is pronounced "county", and "rd" as "road", however I didn't know it would parce groups of letters in the middle of a word (not separated by a space).
Image
State Manager: Maryland
Area Manager: Central MD/ West central PA

Edit for Usability, Simplicity & Retention
All about Junctions Check your Work!
kodi75
 
Posts: 531
Joined: Mon Jul 02, 2012 3:43 am
Location: Central Maryland
Has thanked: 440 times
Been thanked: 106 times

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

Postby Kuhlkatz » Fri Sep 21, 2012 3:56 pm

Hi,

In South Africa we use the N,R,M naming convention for major routes : N - National, M - Metropolitan and R - Regional, supposedly.

I do not always have a headset plugged in, nor have it connected to the Radio via Bluetooth. I do however always have the radio on and barely ever listen to TTS.
I recently noticed that that TTS prompts me to turn onto the 'North One North' or 'North One South' where the road designations are 'N1 North' or 'N1 South'. It's named with no spacing between the N and the 1, so I would typically assume this should be pronounced 'Enn One'.

I would assume that the English version of TTS is global and not Country specific as this is likely handled with the 'nasal twang' for US voices and the occasional 'Keep left, mate' instead of 'Keep left' for Aussie versions ;)

Is there any way we can override this behavior with other naming conventions, or how do we handle this ?
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 4.4.2, v5.11.401.10)
Image
South African Wiki Waze Wiki Map Editing
Kuhlkatz
Localizers
Localizers
 
Posts: 866
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 25 times
Been thanked: 133 times

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

Postby Kuhlkatz » Fri Sep 21, 2012 4:47 pm

AlanOfTheBerg wrote:As is mentioned in this thread and elsewhere, we have no ability to influence TTS pronunciation. We have requested a phonetic field which would help in many cases, but would not likely be able to influence accents.


Alan,

The post reason was twofold. Confirmation that N# produces 'north number' in TTS despite no spacing and I'm interested to know if there is a current 'workaround' for this.

I'm not concerned about the accent, but it would be cool if Waze had this bit customized with voice files like Garmin and other providers.

The TTS override as discussed elsewhere is a good idea, but if the current Livemap does not even indicate reality, this is likely also far off.
It might actually happen in my lifetime still, you never know...
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 4.4.2, v5.11.401.10)
Image
South African Wiki Waze Wiki Map Editing
Kuhlkatz
Localizers
Localizers
 
Posts: 866
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 25 times
Been thanked: 133 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users