On Wed Jun 14 19:37:08 2023 +0000, Bernhard Kölbl wrote:
I find this name to be really confusing. Hbu static_voice_information_provider ?
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)