search for: libspeech

Displaying 5 results from an estimated 5 matches for "libspeech".

2006 Jun 27
7
Library split (poll)
Hi everyone, In the 1.1.x branch, I've kept adding more stuff to libspeex: preprocessor, AEC, etc. I'm now considering moving all those to a separate library (libvoip, libspeech, whatever). Anyone on this list has good reasons I should consider for either splitting or not splitting libspeex? Cheers, Jean-Marc
2007 Oct 11
2
Library split to be merged -- looking for a name
...e lack of complaints about the split, I think I can go safely forward with that. The only thing to decide is the name of the new library that will contain the preprocessor, the AEC, jitter buffer, and resampler. So far, I've got a few potential names: - libspeaks - libspeexproc - libspeexvoip - libspeech - libspoke Let me know (in private so as to not flood the list) which of those you like and dislike. I'm also open to other names. I'll wait a few days and then decide on the name and commit the split to the master/trunk branch. Cheers, Jean-Marc
2006 Jun 27
3
Windows Mobile build, memory allocation
...e 28, 2006 2:55 AM To: Jean-Marc Valin Cc: speex Subject: Re: [Speex-dev] Library split (poll) Jean-Marc Valin wrote: > In the 1.1.x branch, I've kept adding more stuff to libspeex: > preprocessor, AEC, etc. I'm now considering moving all those to a > separate library (libvoip, libspeech, whatever). Anyone on this list > has good reasons I should consider for either splitting or not > splitting libspeex? I'd argue for a separate library; in space-constrained environments, it would be good to be able to easily not include these additional features. Gerv _______________...
2006 Jun 27
0
Re: Windows Mobile build, memory allocation
...gt; Cc: speex > Subject: Re: [Speex-dev] Library split (poll) > > > Jean-Marc Valin wrote: > > In the 1.1.x branch, I've kept adding more stuff to libspeex: > > preprocessor, AEC, etc. I'm now considering moving all those to a > > separate library (libvoip, libspeech, whatever). Anyone on this list > > has good reasons I should consider for either splitting or not > > splitting libspeex? > > I'd argue for a separate library; in space-constrained environments, it > would be good to be able to easily not include these additional > f...
2006 Jun 29
0
Re: Library Split Poll
....62.0606291652150.30841@mix.hive.no> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > Hi everyone, > > In the 1.1.x branch, I've kept adding more stuff to libspeex: > preprocessor, AEC, etc. I'm now considering moving all those to a > separate library (libvoip, libspeech, whatever). Anyone on this > list has > good reasons I should consider for either splitting or not splitting > libspeex? I'd much prefer it if it was still just one library. At the moment, I bundle the library with my Win32 applications (and one file is better than 3), and for Lin...