Voice preview
Play a preview of how the voice will sound when selected so that we will know what it will sound like before setting the voice.
-
Rose Rose commented
Get this done, please.
-
Beth commented
I thought I was doing something wrong bc I couldn’t hear the voice choices when clicking on them. OMG! I’m a “sweet southern bell”, but I’m about to lose my s#+% over this. IT’S 2024!! Let’s fix this! (Please….🤦🏼♀️). Thank you - IN ADVANCE!!
-
Vodka commented
Yay! Welcome to 10 years of people asking for this option and nothing being done about it. Just have a voice sample button that says the same phrase like turn right or left. It shouldn't take 10 years in your backlog.
-
Oreo commented
You've done this with Dashie who is a voice I don't want to use, so I feel it could be implemented with the other voices rather than me selecting one I don't understand and having to wait until I'm driving to realise I don't understand it!
-
ShelliG commented
Trying to troubleshoot whether the voice is working with my parents when they call me to use Waze for the first time and can't figure out how to make sure it will give them directions through Bluetooth!!! Seriously.
-
S. R. Darstein commented
please update this item. I am hoping this will be implemented in 2024
-
Jakub Ouda commented
Let user hear sample of selected voice for better choice!
-
Calvin Bast commented
This is crazy it does not do this.
-
Nathaniel Bose commented
you can read this to know that this needs to be in the app to Safety No1 Priority https://www.johnfitch.com/blog/ohio-driving-safety-laws/
-
Ashley Schiefer commented
How is this not a thing!?
-
Gilbert Murillo commented
+1
-
TJ Smith commented
Since there seems to be a problem with Waze changing the voice you selected arbitrarily, having a test feature on the voice choice is important. I have had Waze change my voice choice at least three times. When I go in to change the voice choice back to my choice, my choice is still the voice selected. So how do I make sure my voice choice is my voice choice now? Having a test feature is necessary now.
-
Chris Stamate commented
Wow, such a natural thing to have when choosing/setting Waze and this doesn't exist already.
Not only it doesn't exist but it's set to Not Planned OR Not right now. Just Wow....
-
Ky Fisher commented
Waze comment about changing the status of this to "not right now" is there way of saying 'we don't care'.
It's a joke this feture has to even be requested. -
Jim SCHNEIDER commented
That's simply a pity. Also that the loudness of the voice can't be boosted. Google Maps does this for years.
-
Mac Reiter commented
Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
-
Mac Reiter commented
Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
-
Mac Reiter commented
Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
-
Mac Reiter commented
Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...
-
Mac Reiter commented
Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...