I’ve been the maintainer of AwesomeTTS for around two years. I grew frustrated with the old codebase and the difficulty of maintaining it. Around 3 months ago, I set out to write AwesomeTTS 2.0, which I’m calling HyperTTS.
Technically here is what is changing compared to AwesomeTTS:
Voices from all services are shown together in the voice selection screen and can be filtered by language.
You can listen to a sound preview before loading audio and experiment with voices / settings.
Text replacement rules are much more transparent and you can try them in realtime.
You’ll be able to add audio with a single click from the editor once you’ve saved a preset.
It’ll be much easier to create new services, just create a single file which respects the conventions.
the codebase is close to 100% regression-tested with pytest-qt. This will allow me to fix bugs, develop new features with much more confidence. I am hoping this becomes a model in the add-on world. My previous addon, Language Tools, already had a similar level of regression test coverage.
That feature doesn’t exist in HyperTTS. It’s assumed that you want audio and the most it’ll allow you is replace the sound tag. I can add a “remove audio” feature but can you tell me more about your use case ? When do you want to remove audio and not add it back ?