Can we also have api points for the server to return available model names and speaker ids (for multi speakers) as well as load and unload downloaded model?
Seems sensible, at least listing models/languages/speakers should be straightforward. I won't implement this myself since we don't use this server, but would merge a PR.
Right now, you can request server to return audio by fetching
http://localhost:5002/api/tts?text={text}&speaker_id={speaker}
Can we also have api points for the server to return available model names and speaker ids (for multi speakers) as well as load and unload downloaded model?
Thanks for your consideration!