Design suggestion: The server just for synthesis

[William Hubbs]

On Fri, Nov 12, 2010 at 11:27:10PM +0100, Andrei Kholodnyi wrote:
> > Hynek, can you elaborate more on what needs to be factored out of sd,
> > and what TTSAPI does? Couldn't we just add the functionality in TTSAPI
> > to speech dispatcher some how?
> >
> > William
> 
> well, I'm not Hynek, but I'll try my best :D
> 
> since TTS synthesis and audio are glued together now, it would be good
> to separate them
> and give people the possibility to retrieve TTS only if they want.

I'm not sure how this would be done since the way we process this is
synthesizer specific. What I mean is, espeak, for example, does all of
the TTS and audio generating and allows us to play the audio. But,
festival and cicero on the other hand do not give us any access to the
tts processing or audio data.  I'm not sure whether Ivona gives us
access to the audio or not; honestly I haven't looked at that code in a
while.

> besides that at the moment one instance of particular TTS engine is
> used per multiple clients
> which makes impossible to produce a separate audio stream per client.

Being able to switch synthesizers on the fly is definitely something we
should look into.

> And finally there was a TTS API developed some time ago and we could
> try to use it instead of libspeechd API
> and also between server and modules.
 
 I'm not sure I follow what you mean here.  That code is written in
 python, so are we talking about rewriting everything in python?

William

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20101112/3ffc719e/attachment.pgp>