Open SHU-red opened 2 years ago
Im not really sure how the "default" setting of the system TTS works, my expectation was that it adapts to the Android settings, but I never really tried. I think there is an option to read all available voices ... it just isn't implement yet. I will have to check if it actually works and how much effort it is to fully implement it.
Thank you very much I just hope to help the project by highlighting such things
Maybe some day i will be able to really contribute to the files / documentation you created
I just realized that the current Cordava TTS plugin needs to be replaced with a new one to enable getVoices
feature. I'll not be able to finish this for the next update, but I'll put in on top of the todo-list together with streamlining of the plugin interface with Web Speech API and some microphone handling for the update after the next release.
Thank you! Awesome!
Just a quick update: I've finally managed to update the whole Android stack (Android SDK, Android Studio, Cordova, plugins) to the latest version(s), fixed a bazillion of bugs, finally built a very early version of the v0.25.0 client and can now confirm that TTS voices selection will indeed work in the next update 🥳 . So far I've only checked my old Samsung A3 but it already had working German male and female offline(!) voices 😎 . It will probably take some time until the update is finished but if you're interested I could share a beta at some point :-)
Is your feature request related to a problem? Please describe. Currently in the sepia app, the Voice Engine (TTS) native can only be set to -system- which provides the female android voice I have changed the setting in my android for my smartphone and google assistant to male Sepia seems to ignore this and TTS is still using female voice, despite the fact that my new -system- setting is changed to male
(Android 12)
Describe the solution you'd like
Describe alternatives you've considered
Additional context Nope