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 DwarfLord » Mon Apr 14, 2014 9:27 pm

AlanOfTheBerg wrote:Already, MT = "mountain" according to the big list.
Does this mean "Mt St Helens Dr" would TTS as "Mountain Saint Helens Drive"? In that case street names beginning with "Mount" should probably continue to spell it out.

I am curious about this topic but as I do not quite know where the "big list" is officially documented and how TTS chooses from the "big list" as opposed to the list published in the Abbreviations and acronyms wiki -- I assume it involves the position of the abbreviation within the sequence but am not completely clear -- I should probably go back to lurking...!
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Wed Jul 09, 2014 9:11 pm

While perusing the "big list" I came upon a misspelling. It should be "crescent" with a c after the s. This is so minor it hardly seems worth mentioning, but it is a reference...
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Wed Apr 08, 2015 3:05 am

In a test this evening, TTS (iPhone, v3.9.4, Samantha) pronounced "Cañada" as "Canada". Which sounds wrong -- shouldn't it say Canyada? -- until one remembers that until quite recently TTS pronounced it "Ca-plus-minus-ada". :? :? :?

I don't know if this is in any way associated with the new version of the app. But it suggests we should finally be able to use ñ in street names without fear of egregiously weird pronunciation. Yay!
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Wed Apr 08, 2015 5:08 am

PesachZ wrote:Can you tell me the full exact street name you tested?
When I tested it sounded like caada street, which is still better then ca ± ada Street.

Odd! I used "Cañada Rd" for the test. It was on a PR type road, and the announcement was for a right turn from a PS onto the PR. Pretty clearly sounded like Canada to me, but admittedly I've only run the test once in that one location.
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Thu Apr 09, 2015 4:07 am

TTS said it again twice for me today, and the intonation and stress were exactly how one would say Canada (the country). The n may have been a bit less nasal, almost a 'd', but no different really from how one usually hears it spoken. Hope this helps!


Sent from my iPhone using Tapatalk
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Thu Apr 09, 2015 2:03 pm

PesachZ wrote:What voice are you using?
Have you cleared your TTS cache recently?
Are you able to share the actual TTS file from your device?

Samantha, no, and I've never attempted that.

I'll research how to accomplish the latter (if it involves jailbreaking I will probably give it a miss).
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby DwarfLord » Fri Apr 10, 2015 3:50 am

Tried iFunBox, it crashed; found another one, iMazingforMac, but it won't run on OS X 10.6.8 (I have to run it for legacy code support). I think I'll give up getting the sound file for now.

I don't plan to change road names en masse anytime soon, but there is a real Cañada Rd that got a UR for lacking the tilde, so I think I'll redo that one. At least the ñ will show on the app display. Hopefully users will be forgiving if it pronounces Cañada even vaguely like the real thing, now that the horrible "plus minus" TTS of ñ seems to be gone!
DwarfLord
Wiki Master
Wiki Master
 
Posts: 1244
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 667 times
Been thanked: 650 times

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

Postby e-sarge » Fri Nov 07, 2014 6:16 pm

Here's another example. It's in Canada, but this is the best thread I found for drive being mis-pronounced doctor.

https://www.waze.com/editor/?env=usa&lon=-78.91376&lat=43.88275&layers=933&zoom=8&segments=80654014

    Segment is named "Glen Hill Dr S".
    Should be pronounced "Glen Hill Drive South".
    TTS said "Glen Hill Doctor South".

Please add this to the list.
ImageImage
Area Manager for Municipal Region of Durham
e-sarge
Area Manager
Area Manager
 
Posts: 227
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 132 times
Been thanked: 33 times

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

Postby e-sarge » Tue Mar 03, 2015 3:12 pm

I think beej666 is on to something here, and it could be used to off-load some of the organization and research tasks from those who interface with the staffers.

If we had a public list (wiki page, google doc/google form, etc) where editors could report problems (with Permalinks), then we could unleash a small team of volunteer Waze editor geeks to do the research (possibly including estimated number of Wazers impacted based on the trip count of the affected segment, if we can get access to that), associate like problems together (all the mispronounced 'Bueno' together, Glen Hill 'doctor' South with Patriot 'doctor' East (same pattern for abbreviation problem), etc.).

Then we could all see the status of our requests, and enable the key players to strategize what to lobby the staffers for (most difficult, longest outstanding, largest group of impacted Wazers, some quick and easy fixes, etc.).

I'd be willing to help with the construction of something like this, if there's support from the senior editor community -- PM me!
ImageImage
Area Manager for Municipal Region of Durham
e-sarge
Area Manager
Area Manager
 
Posts: 227
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 132 times
Been thanked: 33 times

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

Postby e-sarge » Tue Mar 03, 2015 7:50 pm

voludu2 wrote:Rather than a difficult-to-maintain spreadsheet:

Why not a bugzilla (or other bug/issue/feature ) tracking software. One which allows users to vote for the most important feature requests.

And anyone can see the summary report of all or "all open" or "by oldest" or "most popular" and moderators would have the power to merge duplicate requests with a click of the button.

This would be easier to share with the team, too.

Waze editors frequently use space on different unofficial waze-related servers in different parts of the world. I bet it would be possible to find a little space for this.

(And while we are at it, to set up useful issue tracking for other things like road closures, for which the sheet is very cumbersome)


A couple of counter-points:

    TTS errors are bugs, and you don't 'vote' on bugs. All bugs, once confirmed as bugs, need to be fixed (eventually, given the restrictions of resources). Priority should be based on importance and capabilities, not popularity. New features we can vote on, but that's not what this thread is really about.

    And, a second TTS error that has a similar pattern as an existing is not a duplicate, in the same way that a typo might appear on two different Wiki pages -- not a duplicate, just two bugs to be fixed. A duplicate would be two users reporting the same TTS error on the same segment.

FYI, I'm not hung up on any particular tool. I personally don't find spreadsheets 'cumbersome', I find them 'useful' -- the closure spreadsheet works just fine for me. But we don't have to use a hammer if a screwdriver is more appropriate. In this case, we have a rather large list of TTS problems, so something tabular in nature is going to be the best fit.
ImageImage
Area Manager for Municipal Region of Durham
e-sarge
Area Manager
Area Manager
 
Posts: 227
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 132 times
Been thanked: 33 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users