I have sent the visual studio project files that compile the speex client to jean-marc directly (as an attachment), sometime this week, I will also upload the binary builds of static library files to my site www.phonestack.com. I am porting our LTP (lightweight telephony protocol) to some embedded systems. I require to run speex in an environment that doesn't support memory allocations. How difficult is it to convert speex_encoder_init and speex_decoder_init to use preallocated memory buffers (presumably passed by the initilisatio functions themselves)? - farhan - farhan -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Gervase Markham Sent: Wednesday, June 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 _______________________________________________ Speex-dev mailing list Speex-dev@xiph.org http://lists.xiph.org/mailman/listinfo/speex-dev
Jean-Marc Valin
2006-Jun-27 23:16 UTC
[Speex-dev] Re: Windows Mobile build, memory allocation
On Wed, 2006-06-28 at 11:34 +0530, Ashhar Farhan wrote:> I have sent the visual studio project files that compile the speex > client to jean-marc directly (as an attachment), sometime this week, I > will also upload the binary builds of static library files to my site > www.phonestack.com.Actually, Zen (illi on IRC) is the one handling the Windows stuff. I can't do anything with that (I've never even compiled Speex on Windows).> I am porting our LTP (lightweight telephony protocol) to some embedded > systems. I require to run speex in an environment that doesn't support > memory allocations. How difficult is it to convert speex_encoder_init > and speex_decoder_init to use preallocated memory buffers (presumably > passed by the initilisatio functions themselves)?All you need to do is override some of the functions in misc.c. You should need to touch anything else. Jean-Marc> - farhan > > > - farhan > -----Original Message----- > From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On > Behalf Of Gervase Markham > Sent: Wednesday, June 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 > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org http://lists.xiph.org/mailman/listinfo/speex-dev > >
Which version of VS, and which version of Windows Mobile are they for? There are already build configs for Windows Mobile 5 in the repository for all the xiph libraries. If you have configs for the old PPC's, let me know and/or send me the project files and i'll put them in the repository. There's also a directshow(for Windows Media Player on WM5 devices) release just waiting to be tested some more before release for vorbis, speex and theora in case you are interested. Zen. Jean-Marc Valin wrote:> On Wed, 2006-06-28 at 11:34 +0530, Ashhar Farhan wrote: > >> I have sent the visual studio project files that compile the speex >> client to jean-marc directly (as an attachment), sometime this week, I >> will also upload the binary builds of static library files to my site >> www.phonestack.com. >> > > Actually, Zen (illi on IRC) is the one handling the Windows stuff. I > can't do anything with that (I've never even compiled Speex on > Windows). > > >> I am porting our LTP (lightweight telephony protocol) to some embedded >> systems. I require to run speex in an environment that doesn't support >> memory allocations. How difficult is it to convert speex_encoder_init >> and speex_decoder_init to use preallocated memory buffers (presumably >> passed by the initilisatio functions themselves)? >> > > All you need to do is override some of the functions in misc.c. You > should need to touch anything else. > > Jean-Marc > > >> - farhan >> >> >> - farhan >> -----Original Message----- >> From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On >> Behalf Of Gervase Markham >> Sent: Wednesday, June 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 >> _______________________________________________ >> Speex-dev mailing list >> Speex-dev@xiph.org http://lists.xiph.org/mailman/listinfo/speex-dev >> >> >> > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/speex-dev > >
Jim Crichton
2006-Jun-28 10:04 UTC
[Speex-dev] Re: Windows Mobile build, memory allocation
> On Wed, 2006-06-28 at 11:34 +0530, Ashhar Farhan wrote: >> I have sent the visual studio project files that compile the speex >> client to jean-marc directly (as an attachment), sometime this week, I >> will also upload the binary builds of static library files to my site >> www.phonestack.com. > > Actually, Zen (illi on IRC) is the one handling the Windows stuff. I > can't do anything with that (I've never even compiled Speex on > Windows). > >> I am porting our LTP (lightweight telephony protocol) to some embedded >> systems. I require to run speex in an environment that doesn't support >> memory allocations. How difficult is it to convert speex_encoder_init >> and speex_decoder_init to use preallocated memory buffers (presumably >> passed by the initilisatio functions themselves)? > > All you need to do is override some of the functions in misc.c. You > should need to touch anything else.Look at the TI subdirectory for an example of this. You just need to define USER_MISC, and then add a file user_misc.h, which has the actual override code. In the TI example, there two statically allocated blocks of memory which are accessed through global variables. It is not elegant, but it does not break the API. The memory requirements will depend upon what Speex modes you will be supporting. In the TI example the scratch and persistent storage are allocated from separate blocks, which allows the encoder and decoder to share the same scratch space. - Jim