This Thor Street in Victoria is pronounced by the app (English UK Kate) as “Thor Street”, but the app pronounces rbrdly’s one in WA as “Thoroughfare Street”.
What I did was to use the “Set as start point” feature you get in the menu when previewing a street. Hold down on a street, open the detailed info screen, tap the three dots then “Set as start point”. Then hit the search button in the popup that appears.
You basically need to try and form a short route that starts on a street before Thor St, and ends on a street after it, so that the route Waze comes up with includes Thor St. The app will then say “Let’s take Thor Street” when starting navigation. In the case of the street in WA, it said “Let’s take Thoroughfare Street”.
that looks awfully complicated. Have we confirmed that Kate (the voice used for English UK in the editor) pronounces things in the editor the same as she does in the app?
I’m not sure about the inconsistency. I just tested the Thor St from earlier in this thread that was meant to work on my phone and it doesn’t work. Instead it just says “Thoroughfare St”, which is what it says in the editor. Would it be too much work for you if I started to go through streets in the editor and let you know which ones aren’t being pronounced properly through this topic?
Does the change from s to b change it from the name always starting with MR? So MR2 - Riawena Rd would be announced as Metroad 2 - Riawena Rd, but something like Exit to MR2 - Riawena Rd wouldn’t work if it the s was used?
Is it possible you could make ALTNR1 pronounce as Alternate National Route 1 or something like that? WME TTS just reads out all the letters for it, which might be confusing for drivers not familiar with the abbreviation. It’s used on Princes Highway in Victoria from Melbourne to Berwick.
At risk of sliding past educated hypothesis into the realms of wild-arse guessing, I think there might be another factor/dimension at play - time. I think Waze client caches some TTS phrases and then reuses the one in the cache rather than re-downloading the sound instructions every time they’re needed. It might be that you’ve got pronunciations that were generated at different times, maybe one that is “turn left into Thor St” and another that is “turn right into Thor St”. For a long time (>1 year) I used to get two different pronunciations of “roundabout” - sometimes it would be normal pronunciation with a slight emphasis on the first syllable, and sometimes it would be like three distinct words with equal emphasis “round a bout”. It was only after 2000km trip (which presumably cleared out some old cache entries) that the pronunciation went back to normal.
That’s what I was worried about as well, which is why I suggested “something like that”. All the signs read as in your image, “ALT” with the number 1 underneath. Maybe “Alternate Route 1” or “Alternate 1”, perhaps?
According to this VicRoads document (Manual of uniform traffic control devices
Part 15: Direction signs, information signs and route numbering), the sign is for an Alternative Route. The following is from page 157 of the document:
I doubt there’s such thing as a TTS cache in WME, as unlike the Waze map, you don’t have to consider users trying to use the WME offline - it’s not possible. If there is, the best option would be to try cleaning your whole browser’s cache and then reloading the editor.
UK Kate is pronouncing “Murchison” as “Murkison.” Youtube
On a related note there has been some discussion on whether to put spaces before and after the hyphen in names such as ‘From-To Rd.’ I have found that UK Kate says it correctly when there are no spaces. It sounds like she is starting a new sentence if there are spaces in there like, “Turn right onto Melbourne. Sydney road.”