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.

Moderator: adriansinger

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.
ImageImageImage
State Manager | New Jersey, USA
Kobes1878
Map Raider
Map Raider
 
Posts: 589
Joined: Thu Jun 19, 2014 11:37 pm
Location: South-Central NJ, USA
Has thanked: 168 times
Been thanked: 216 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: 504
Joined: Mon Jul 02, 2012 3:43 am
Location: Central Maryland
Has thanked: 388 times
Been thanked: 96 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: 865
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 26 times
Been thanked: 132 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: 865
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 26 times
Been thanked: 132 times

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

Postby Kuhlkatz » Tue Jan 29, 2013 5:57 pm

davidg666 wrote:I ask because there's an issue that affects TTS here in Ireland - and presumably also in South Africa, where they use similarly-named roads - that could easily be resolved by making the TTS behave slightly differently.


David, I have been following this thread with some new interest, as we indeed have the same problem. I drive on the 'North One South' and 'North One North' daily, so it is a bit of a thorn in my side, especially since I have seen quite a few URs on this and know I can do nothing to fix it.

We can likely live with the 'N'1 N / 'N'1 (N) or 'N'1 S naming convention if Waze 'tweaked' TTS slightly, but I was not happy with resorting to the 'n'1 N or 'n'1 S convention to work around this.

I'm just curious as to how the name actually looks and displays in the client, and how visible the single quotes are.

Instead of just 'tweaking' this every time, Waze devs should possibly just look at using or defining some opening character and closing character that will likely NEVER appear in any actual names, and use that as a 'literal' indicator, where anything that apears inside the literal is not subjected to testing for abbreviations.

Something simple like the square brackets or even the curly braces. Naming it [N]1 N, or even [N1] N, and they simply drop the brackets in the displayed name, and do not pronounce [N] as 'north'. Even something like ~N~1 N, where the single 'tilde' characters are ignored. I presume fixed 'opening and closing' delimiters would be simpler to search. They could even be used as an indicator that this character sequence should be pronounced individually instead of treating it as a word, like [QE]2 or even [NY] being explicitly overridden as 'Queue Eee Two' or 'Enn Why'.

Something like this would be far simpler to implement in code, instead of having to populate an additional DB field to use as a TTS override using phonetics, where 99% of all existing named segments would likely never make use of the phonetic override.
It just requires some simple string manipulation during Back-End parsing which they likely do already.
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: 865
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 26 times
Been thanked: 132 times

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

Postby littlestlou » Fri Nov 09, 2012 4:43 am

So, I already mentioned this to Weezer but I noticed for the very first time today the TTS for CONST ZN was "Kahnst Zee N" and not the intended Construction Zone. I can also confirm this was previously not a problem as I heard it correctly within the last couple of months (not sure exactly when since I don't routinely travel this area). Any thoughts or anyone else noticing this problem all of a sudden?
ImageImage
littlestlou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

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

Postby littlestlou » Sun Nov 11, 2012 6:07 pm

Gizmo,
I already sent you a PM but since this is an issue of potential public interest I will follow up on the forum too. I can confirm that while the TTS for CONST ZN worked previously, it no longer does. I am not sure how to send the TTS file. I will search around the wiki, etc. but if you can point me in the right direction, that would be helpful. I need very basic step-by-step instructions...unfortunately. :oops:
Thanks,
LL (and yes, I have a Droid 4)
ImageImage
littlestlou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

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

Postby littlestlou » Sat Nov 17, 2012 5:18 pm

Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...
ImageImage
littlestlou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users