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: MapSir

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.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1362
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 529 times
Been thanked: 346 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.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1362
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 529 times
Been thanked: 346 times

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: 2583
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 44 times

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.
ImageImage
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 jasonh300 » Tue Nov 20, 2012 1:49 am

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


How about CR-##?
Image
New Orleans, Louisiana, USA
South-Central Regional Coordinator
(LA/MS/AR...contact karlcr9911 for TX/OK related issues)
U.S. Champ, Global Champ
Waze FAQ ... Best Map Editing Practice
Ask me about Louisiana Editors Chat in Google Hangouts!
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 7546
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 398 times
Been thanked: 965 times

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

Postby GizmoGuy411 » Tue Nov 20, 2012 2:31 am

jasonh300 wrote:
How about CR-##?


Last February it worked. For some reason I had an "Add" notation for it. Guess I should retest it.

Now that the tile turn around time has shortened I need to test the rest of the list. Hopefully before mid January.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1362
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 529 times
Been thanked: 346 times

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

Postby KB_Steveo » Wed Nov 28, 2012 2:56 am

Tlwy says something like "Tl-whY"

(Line 622)
ImageImageImage
WI State Manager
NE Wisconsin Area Manager (Green Bay / Appleton / Sturgeon Bay)
Wisconsin mapping resources curator
KB_Steveo
State Manager
State Manager
 
Posts: 315
Joined: Wed Jan 25, 2012 5:26 pm
Location: Wisconsin
Has thanked: 53 times
Been thanked: 27 times

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

Postby KB_Steveo » Wed Nov 28, 2012 3:01 am

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

+1

Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)
ImageImageImage
WI State Manager
NE Wisconsin Area Manager (Green Bay / Appleton / Sturgeon Bay)
Wisconsin mapping resources curator
KB_Steveo
State Manager
State Manager
 
Posts: 315
Joined: Wed Jan 25, 2012 5:26 pm
Location: Wisconsin
Has thanked: 53 times
Been thanked: 27 times

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

Postby littlestlou » Wed Nov 28, 2012 3:28 am

Regarding the infamous Coe Roads, I am almost positive that up until a couple of months ago, everything was pronounced correctly. Perhaps I am going a little nutty though. Either way, thanks for the tip on CR, etc.
ImageImage
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 GizmoGuy411 » Wed Nov 28, 2012 4:19 am

sbelekevich wrote:...
Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)



Thanks for reconfirming that.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1362
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 529 times
Been thanked: 346 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users