On Friday 30 March 2018 14:48:18 fredvs wrote:
> > You don't want to publish your changes? Why?
>
> Yes, no problems to publish the changes of Pcaudiolib.
>
> > It is enough if you host your pcaudiolib version on your GitHub account.
>
> Ha, no need to show all the source of the application that
> You don't want to publish your changes? Why?
Yes, no problems to publish the changes of Pcaudiolib.
> It is enough if you host your pcaudiolib version on your GitHub account.
Ha, no need to show all the source of the application that use the "updated"
Pcaudiolib ?
> What other problems?
A
> Which license problems? Please explain.
If you use eSpeakNG as executable (to not have licence problems) but change
code of Pcaudiolib, it will have license problems.
> . I would expect that synthesizer parameters have much more impact than
> the sample format.
I do not talk about sample
On Thursday 29 March 2018 22:13:48 fredvs wrote:
> Are you really sure that original eSpeak is dead ?
>
Yes, see here:
https://sourceforge.net/p/espeak/code/391/log/?path=
> And the creator is still active in his forum.
Last post 2015?
> Sorry, but I will stay with original eSpeak (and his
On Thursday 29 March 2018 20:43:04 fredvs wrote:
> Pf, so much easier to close things...
>
You write:
"
If you compile espeak-ng as executable, espeak-ng will need pcaudiolib as
dependency.
If I do adapt pcaudiolib (for example for better latency or using float 32
resolution), I will have
5 matches
Mail list logo
