Design suggestion: The server just for synthesis

[Hynek Hanke]

On 4.11.2010 20:22, Michael Pozhidaev wrote:
>> I can really take this work and try to do it keeping complete approval
>> of speechd community. Of course, the result will not be immediate, but
>> I am convinced it is the real way to merge our effort to create good
>> speech output structure.
>> Do you agree to include support of remote TTS server we are discussing into
>> speechd when some versions be ready?

In principle yes, but I would still like to clear up some details. Is your
proposal different (in technical aspects of course) from the work that
was already done on TTS API/TTS API Provider and why? Do you plan
to work on this API or to create a different API?

Do you propose to have a Speech Dispatcher have plugins for both
the existing modules and the TTS server you propose? As a temporary
measure, that might make sense, but long-term, if there is any service
that takes care just of low-level TTS management and not audio output
and not message dispatching, the existing modules should be moved
from Speech Dispatcher to that server and the complexity of handling
this task in Speech Dispatcher itself should be removed from it.

What do you think?

Best regards,
Hynek Hanke