AlanOfTheBerg wrote:Jr. B St. Dr. = "junior bee saint doctor"
sketch wrote:taddison1 wrote:jasonh300 wrote:What was the exact name of the expressway, as named on the Waze map? It's working fine at the expressway near me.
It's "N Central Expy".
Whatever this TTS problem is, it doesn't seem to be consistent. Most streets announce fine, there seem to be just a few that don't.
I haven't figured out if it's always the same streets that fail to announce the abbreviations correctly, or if it's just a random failure that can occur on any street. Unfortunately, the streets that I've heard fail are far from my house so I can't easily go and drive them again.
All the examples I saw with the "N" problem seem to be where Waze doesn't expect a "north", that is, wherever the N is not preceded by a street abbreviation or a numerical highway designation. So it didn't work on "Cesar Chavez N" or "I-35W N", while I assume it would work on "Cesar Chavez Dr N" or "I-35 N".
GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!
jasonh300 wrote:kentsmith9 wrote:Cord is what I will be wrapping around my neck if we go a second month with no map updates in NA.
A second month??? We're almost 3/4 of the way through the second month!
bgodette wrote:WeeeZer14 wrote:There have been situations were Waze has cached the TTS audio files for frequently used streets/ramps. Users had to manually delete these files to get the effects of new TTS rules. I don't remember the details, but just wanted to point that out if you see slightly different pronunciation in different cases. It could be the case or it could be cached data.
Entering cc@tts into waze's search will clear the tts cache.
It's all my phone's fault for using Tapatalk.
kentsmith9 wrote:I thought I have recently heard some directions not be spelled out.
Users browsing this forum: No registered users