Text to Speech voice is not changing...

gkld

New member
Hi guys,
I am trying to change the voice model of my announcements but it's not changing. I am trying from last 1 month but I couldn't solve it myself. I am attaching all screenshots with this help request to help you understand my settings.

I tried changing engine, voice model, etc already.

I don't know any hidden settings.

Can someone please help?
 

Attachments

  • Screenshot_20230103_080847_MacroDroid.png
    Screenshot_20230103_080847_MacroDroid.png
    142.8 KB · Views: 8
  • Screenshot_20230103_080853_Settings.png
    Screenshot_20230103_080853_Settings.png
    66.3 KB · Views: 8
  • Screenshot_20230103_080948_Speech Services by Google.png
    Screenshot_20230103_080948_Speech Services by Google.png
    57.4 KB · Views: 8
  • Screenshot_20230103_080959_Speech Services by Google.png
    Screenshot_20230103_080959_Speech Services by Google.png
    113 KB · Views: 8
  • Screenshot_20230103_081007_MacroDroid.png
    Screenshot_20230103_081007_MacroDroid.png
    55.9 KB · Views: 8

MacroDroidDev

Administrator
Staff member
It's not entirely clear at what point it's failing from your message, but I will make an assumption that whatever you change the voice to (voice IV, Voice V etc.) it makes no difference, is that correct?

MacroDroid should be using whatever is set as your phone's default text to speech engine and that in turn should use whatever specific settings are configured for it. When you test the voice via your phone's settings app does it change to reflect your chosen voice?
 

Lupus52

Member
it is making bad sound not the sound i am selecting but some other sound.
Hello, I have the same problem since last updating my app. (always manually)

Until the update my TTS was google with the nice voice of "Miss Google"

Since the update I have another lady talking! :-(

In the system language settings I can set what I will. MD uses some other engine but not my google lady.

Switching the language in MD to english, french, german works. But the wrong voice!

How can I get back the voice from before the Update
 

MacroDroidDev

Administrator
Staff member
I haven't made any changes in the last update related to the speak text functionality so any problem you have is unlikely be due to an update.

Have you tried selecting the Text to Speech engine to use option accessible via the speak text configuration screen?
 

Lupus52

Member
I haven't made any changes in the last update related to the speak text functionality so any problem you have is unlikely be due to an update.

Have you tried selecting the Text to Speech engine to use option accessible via the speak text configuration screen?
The problem startet direct after the last MD-Update some days ago. I tried more than an hour to "repair" it. Changed the TTS-engine and the language in the system some times. And changed in MD-settings. Suddenly I had the correct voice back. With all the same settings like before. This problem I had some times before. Each time, when I installed MD new in the last 2 or 3 years. After new installation MD used always a strange "voice", but not the selected voice from my system settings. And after a lot of tryings with settings suddenly all is ok.
 

MacroDroidDev

Administrator
Staff member
I can't explain that I'm afraid. I have many devices and never seen similar, not can do I have other similar reports.
 

Lupus52

Member
Look in the first posting of this thread! The TE tried to change the wrong voice to the voice of the system! But MD does not change it like he want.

This ist exactly the same problem! There are some more similar threads I have found.

MD is using sometimes the wrong TTS! I had this each time after new installing MD or now after the last update.
 

MacroDroidDev

Administrator
Staff member
As I said I'm not aware of any issues that are exactly the same as yours.

I am aware that a tiny fraction of users have occasional issues with text to speech engine behavior. There are also 100,000s of users who it works for without a problem.

Unfortunately Android is a complex mess of a platform and occasionally things like this can happen and it's hard to know where the fault lies or what can be done to resolve it. Of course us application developers will get the blame regardless of if the app is at fault or there is some underlying issue outside of our control.
 
Top