speechd-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Design suggestion: The server just for synthesis


From: William Hubbs
Subject: Design suggestion: The server just for synthesis
Date: Sat, 13 Nov 2010 21:50:27 -0600

Hi all,

On Sat, Nov 13, 2010 at 09:43:21AM +0600, Michael Pozhidaev wrote:
> Hello, Hynek!
> 
> > Actually it's implementation as a text protocol has also been
> > defined already in a draft:
> >
> >     
> > http://cvs.freebsoft.org/doc/tts-api-provider/tts-api-provider.html#Text-Protocol-TTS-API
> 
> OK, we can easily consider it.
> 
> > Yes, both the API and its implementations are still in draft stage,
> > so improvements are very welcome.
> 
> Hynek, can you give me some resources on freebsoft.org where I can do
> this work? First of all - git repository. It seems to me the best way is
> to save drafts into text files and edit them with discussing. Then this
> git repo can be used and for source code control too. When text
> documents are ready we can publicate them on the web. OK? If using
> freebsoft.org is not convenient for you I can easily register new
> project on sourceforge.net . What about 'ttsbunch' as name for new
> package?

Michael, I'm not Hynek, lol, but I will comment here on what I think
should happen.

I don't think it would be a good idea for you to open a new project for
this on sourceforge.

What I would suggest to start with is this:

Hynek, can you move the ttsapi code and documents to git repositories
that the reviewers can commit to?

Once that's done, Michael, you can post patches to the list here like we
do the code so that they can be reviewed and we can decide whether or
not to make the changes.

> > I don't actually think we are talking about some entirely new
> > server. It's much more about refactoring the existing Speech
> > Dispatcher technology into three pieces, re-using its knowledge,
> > its design etc.
> 
> Yes, we must use already created code so much as it possible. Also :
> I have some ideas, what do you think about following:
> I would like to use the minimum configuration data for TTS server. For
> example the set of available TTS the server instance is serving must be
> defined only by list of so-files installed in some special directory. No
> registering in configuration files is permitted. It allows activating
> new TTS only by installing corresponding package. I say 'apt-get install
> foobartts-plugin' and it is everything required to use it. 

I'm not following what you mean here, unless you are talking about
automatic module discovery, which is something that is in the plans for
the project, we just haven't discussed implementing it in detail yet.

But, I'm also against a new server; I don't think that's needed at all.

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/20101113/36e5f64d/attachment.pgp>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]