Let user hear sample of selected voice for better choice!

I can see this has been suggested several times so I’m not very hopeful! But you notified me of some new voices yesterday which I was able to hear a sample of. So why can’t you do this with all the voices? Every other satnav system I’ve used has this option, it seems to me to be a very basic and necessary function, so I don’t understand why you can’t include it.

Near future? It’s now April 2024, and I can’t test voices on my phone without being in my car!

This is crazy it does not do this.

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/

How is this not a thing!?

+1

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.

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....

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.

That's simply a pity. Also that the loudness of the voice can't be boosted. Google Maps does this for years.

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.

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.

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.

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...

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...

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...

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.

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...

Please for the love of God don't give us 50 voice choices but no way to hear them without selecting everyone and then wait for waze to talk. So all the voice options are great but terribly unsafe to be driving in order to sample a voice.

Samples of audio files goes back to windows 3.1!!!!!

Google/waze get your **** together already