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

[ img ] 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: MapSir

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

Postby littlestlou » Tue Nov 20, 2012 12:59 am

GizmoGuy411 wrote:Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".


Gizmo, I guess it's possible but I know for sure that CONST ZN and Co Rd happened at the same time. I cannot say for sure about the release prior to 3.5 b/c I had so many GPS issues that I went back to the release before last....

Regardless, I will start using CR. Thanks for the hint.
littlestlou
 
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 floppyrod84 » Mon Nov 19, 2012 6:58 pm

Using Daniel UK. Not tried the female one it sounds rubbish but I think you may be right. Question is, why has someone at Waze again messed around with the TTS settings? No one asked for this change and AFAIK the St at the end being said as Street would apply to the US as well, so if you guys aren't affected, I would surmise that you are indeed correct that voice translations/abbreviations are voice specific and not global, although there will be global settings.

Sent from my GT-I9100 using Tapatalk 2
floppyrod84
 
Posts: 2569
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby GizmoGuy411 » Mon Nov 19, 2012 5:13 pm

xteejx wrote:St at the end is now saying Saint. Will look into this at my end as I didn't name it and it might have a dot.

Sent from my GT-I9100 using Tapatalk 2



What "voice" are you using for Waze? In the US we use Nuance's "Samantha" or "Tom", however I suspect that the voice(s) for the UK, may not use the same TTS databases.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1412
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 666 times
Been thanked: 434 times

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

Postby GizmoGuy411 » Mon Nov 19, 2012 5:10 pm

xteejx wrote:OK its all St are now saying Saint. Wtf guys? The Street Paul's Street I could live with as Saint is only some roads, but now every Street is Saint, seriously sort it out and revert all recent changes to the UK TTS. Or better yet, give one of us access to the rules on Vocalizer and we can do it in a few minutes!

Sent from my GT-I9100 using Tapatalk 2


Send a message about this "Support" and see what happens. They don't read this thread.

On the other hand, I have been in contact recently with Waze about this and a few other issues, and they are looking for a possible solution.

I doubt that giving us direct access to the Vocalizer interface will be a possibility however. They would probably have to build an interface to it.

To make matters worse, the issue may not be something solvable with Vocalizer. There are actually two issues at hand. One is the overall TTS database and customized "mobile app" database from Nunance, and another is the exception rule system that Vocalizer can adjust for individual things.

Since I've never found any public documentation for the Nuance Vocalizer, so I really do not know how it interacts with the databases, nor what exceptions it can handle.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1412
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 666 times
Been thanked: 434 times

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

Postby GizmoGuy411 » Mon Nov 19, 2012 4:58 pm

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



Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1412
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 666 times
Been thanked: 434 times

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

Postby dknight212 » Mon Nov 19, 2012 12:30 pm

Not very clever!
dknight212
 
Posts: 4963
Joined: Sun Apr 24, 2011 9:21 am
Location: London, UK
Has thanked: 473 times
Been thanked: 636 times

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

Postby floppyrod84 » Mon Nov 19, 2012 9:54 am

OK its all St are now saying Saint. Wtf guys? The Street Paul's Street I could live with as Saint is only some roads, but now every Street is Saint, seriously sort it out and revert all recent changes to the UK TTS. Or better yet, give one of us access to the rules on Vocalizer and we can do it in a few minutes!

Sent from my GT-I9100 using Tapatalk 2
floppyrod84
 
Posts: 2569
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby floppyrod84 » Sun Nov 18, 2012 2:13 am

St at the end is now saying Saint. Will look into this at my end as I didn't name it and it might have a dot.

Sent from my GT-I9100 using Tapatalk 2
floppyrod84
 
Posts: 2569
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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...
littlestlou
 
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 Alice2 » Thu Nov 15, 2012 9:52 pm

AndyPoms wrote:
jasonh300 wrote:It's most likely because the word "To" on the ramp is capitalized, which doesn't conform to the standard.

I'm going to send a PM to the editor in question and make sure this is just a typo and not widespread.
Remember there was a period of time when auto-capitalization just started where the word "to" was not exempt & it was automatically changed to "To", so there may be more ramps out there like this...

I just drove this route again today, and the TTS was correct this time! https://www.waze.com/editor/?lon=-98.59 ... s=48129505 The "to" is also now lower case in the editor. However I see that there are several (could be many) instances of upper case "To" all around. My experience must have been a one-time thing if no one else has come across the "stay left on to I XX".
Alice2
 
Posts: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
Been thanked: 0 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: ThatSlowGuy