-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSML rendering not working #287
Comments
Note to self.
Then in start synthesis we need to
But needs thought. We should have a flag that works in sapi and nsss too And for ssml in sapi. Remember we need to work on other methods like save to file.
Small snag. I don't think ssml is supported in nsss. Annoying. I could be wrong.
However I think we should migrate all of macOS code to AVSpeechSynth https://gist.github.com/willwade/93e709147d7ce9a5f80a3c3944f8e331 |
nateshmbhat#347 nateshmbhat#336 I think this is passing all the tests. Its far simpler than nsss and we can do thngs like ssml nateshmbhat#121 nateshmbhat#287
I think this is passing all the tests. Its far simpler than nsss and we can do thngs like ssml nateshmbhat#121 nateshmbhat#287
The engine.say method does not render SSML in espeak;; and there is no method to set the equivalent of the CLI espeak "-m" option to tell pyttsx3 that the content of the string is SSML and have it render properly. There is an argument that SSML rendering should be turned on by default - to do this the say function in espeak.py should be altered to OR _espeak.SSML with the other flags currently used.
The text was updated successfully, but these errors were encountered: