On Thu Jun 15 07:47:04 2023 +0000, eric pouech wrote:
the actual idea is to be able to support several voice providers:
- the current code as the "dummy" one, which provides an empty and
unique voice, so that most applications expecting TSS available won't fail (that should be the fallback when all the other providers fail to be instanciated)
- using sapi and expose sapi results
- some other platforms (macos, android) may also require their own provider
so your proposal doesn't really fit the above (perhaps synth_voices_provider would match better)
Sure synth_voices_provider sounds good.