xteejx wrote:Can't see from phone if it's there, but Cr gives County Road. Annoying here as it's our convention for Crescent.
Sent from my Telenor_OneTouch using Tapatalk
Yes you are correct. The TTS result for "Cr" is "County Road". Also as an example, "CR-123" would say "County Road One Two Three".
For "Crescent" the USPS and Canada Post both use "Cres" for their official abbreviation. Waze also recognizes "Cres" with the TTS output of "Crescent". So, it looks like "Cres" is our best option on this side of the pond. There are also some longer, less optimal abbreviations that are commonly used for "Crescent" that are in our test list, but have not been tested yet. Of course all this is for North America, and not for across the pond. Hopefully someday you will have your own TTS server.
YouTube Video of the hilarious British Daniel talking for Waze!
xteejx wrote:Is there no way Waze would be willing to allow direct access to the TTS API so this could all be tested easily? Or at least give us a list of the exceptions they have in place. From that, we can conclude that everything else will be said the same as on the Nuance Vocalizer Demo online.
As far as direct access to the TTS exceptions, I have a feeling that Waze has made changes on their end and they have not necessarily documented them. From what I have read, Nuance provides a tool to make such changes, however Waze has not found a way to provide the tool to us. Plus there are two issues. Exceptions should be just that. Such a tool could provide us with a way to change the TTS on a per segment basis, but not with the global TTS result.
The global (as in country TTS server wide) TTS results for abbreviations would still need to be handled by Waze and or Nuance. From our communications with Waze at the Palo Alto meet-up, they do NOT have a list of the known TTS results. That is one reason why we are doing it ourselves.
And using the Demo at Nuance is not much help either. The Demo is not for their custom "Automotive" package, which I assume it what Waze is using for TTS. So anything we test in the Demo, could be different from the Nuance Automotive solution, and further different as a result of the exceptions added by Waze.
On Sat 2012-Feb-18, 01:02:55, GizmoGuy411 wrote:For those who would like to hear Samatha or Tom (plus others) convert text to speech, here is link to Nuance's interactive demo of their "Vocalizer for Netrork 5" product. Note that although the database is similar, it is not customized with their automotive product, or with Waze customizations.
Interactive TTS Demo: http://www.nuance.com/vocalizer5/flash/index.html
The sister product that Waze appears to use, is Nuance's "Vocalizer for Automotive" (no demo found), that has a preconfigured database customized for automotive use, and includes their Vocalizer Studio, which allows for a customization like several people in the various threads here about TTS have talked about; "it also allows customized text processing and the creation of user dictionaries for exception pronunciations."
The Nuance Language Portfolio for their Automotive Services, for the US English in the Americas, shows Samantha and Tom which Waze uses and Lisa who is not available in Waze. Check it out for other voices.
Edited 2012-05-09 to include additional relevant links to Nuance.