similar to: Speex decode memory usage on an Arm processor (wideband)

> > I have tested lowering these values and then running the speexdec > > program and looking for errors. By trial and error it appears that I > > can lower MAX_CHARS_PER_FRAME = 750, SB_DEC_STACK = > > 750*sizeof(spx_sig_t) and NB_DEC_STACK = 250*sizeof(spx_sig_t) > > and not get any memory errors but have no idea if these are safe > > values or not. I

On Mon, 2006-01-02 at 22:37 -0500, tom abcd wrote: > I am hoping to use Speex for a embedded project using Philips Arm > processor (50 mips) 512kb flash 32kb ram. I found in the manual that > decode takes about 0.5 mips so I should have enough processing power > and I compiled the lib and it seems to take less then 64K so the only > issue is memory usage. I have been testing the

Revision 9316 introduced SB_ENC_STACK and friends, but misdefines SB_ENC_STACK to be too small, resulting in quite noticable artifacts in wideband mode as well as memory corruption and a crash (sooner or later). The patch below should return SB_ENC_STACK to be equal to what it replaced. Index: sb_celp.c =================================================================== --- sb_celp.c

>> There is a bit of work remaining to get the memory usage down for a >> multichannel application. There have been some good posts over the >> last couple of months about reducing memory usage. > > I think 1.1.8 incorporates all memory reductions proposed. Let me know > otherwise. For the persistent storage, the only change that I have made is to MAX_CHARS_PER_FRAME,

diffed against http://svn.xiph.org/trunk/speex r9583 Index: libspeex/sb_celp.c =================================================================== --- libspeex/sb_celp.c (revision 9583) +++ libspeex/sb_celp.c (working copy) @@ -272,7 +272,6 @@ st->g0_mem=speex_alloc((QMF_ORDER)*sizeof(spx_word32_t)); st->g1_mem=speex_alloc((QMF_ORDER)*sizeof(spx_word32_t)); -

I need to shrink speex so it will fit on an embedded processor along with some other code. The chip has only 20k of ram. I have done some work with libspeex.dsp by removing references to all modes but narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the structures for the other submodes and the functions that they called.

Hi I am currently trying to port speex v1.1.6 to a microcontroller with very limited memory (<64Kbyte RAM). what I found when initialising the encoder, a chunk of 32Kb was attempted to be alloced, which failed: src/nb_celp.c: void *nb_encoder_init(const SpeexMode *m) { /* snip */ st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(spx_sig_t)); /* snip */ } same goes for the

Hello, Merry Christmas and happy new year for everyone. I've started porting Speex 1.2rc1 on a 32-bit microcontroller, so far everything goes fine for Norrowband modes. But when I'm trying to encode in wideband mode with quality higher than 5 then decode my file back, I get inaudible "thing" (just strong noise). - All frames are decoded with correct result (decoder function

Hi Jean-Marc, will you include these optimizations for minimal ram usage in the main version? Maybe if Peter sends a Patch... Thanks, Alain Jean-Marc Valin escreveu: > Sounds like you did most of what you needed to do. Using a coverage > analysis tool might help you remove bits of code here and there (e.g. > unused _ctl() cases), but the main part is done. About the preprocessor,

Hi, I've been trying to get Speex to compile and run on the DSP of TI's new DaVinci System-On-Chip processor, which has both an ARM (ARM926) and a DSP (C64+, based on the C6400). I used the latest code (1.2beta) and followed the example in the speex- 1.2beta1/ti/speex_C64_test trunk to build the Speex library for the DSP. Basically I have a loopback application on the ARM that samples

On Mon, 2005-02-28 at 19:42 -0500, Jean-Marc Valin wrote: > > jean-marc: i think we can remove spx_sig_t *orig. > > but am not sure about exc2Buf. is it for extension? > > orig is already removed in SVN (which you should probably use). As for > exc2, it can be removed, but I'm not sure if you can just use exc > instead (maybe yes). > when removing "spx_sig_t

The 's' suffix on the cmp instruction is deprecated and superfluous since the cmp instruction always sets conditional flags. This fixes building for iOS with inline assembly enabled. --- libspeex/filters_arm4.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libspeex/filters_arm4.h b/libspeex/filters_arm4.h index 7a74042..2c64625 100644 ---

hi, jean-marc: i think we can remove spx_sig_t *orig. but am not sure about exc2Buf. is it for extension? rgds, tk On Mon, 28 Feb 2005 12:42:38 -0500, Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> wrote: > Hi, > > I looked at the code I think there are still places where you can reduce > memory. For example, I think bufSize can be reduced to around 400 > (instead of

Hi Jean-Marc, I have tested Speex in fixed-point mode on my PC without clicking noise. As I mentioned below, I tested Speex in fixed-point mode running natively on the ARM side of the DaVinci without click noise. I only get the clicking noise when running Speex on the DSP side. For the TI C64+ DSP on the DaVinci processor, the TI-specific switches doesn't do much other than defining the

Hi Jean-Marc, Hi Jim, I have also seen some problems with the 1.1.8 release on the C55x. So far I have boiled down the issues to the following: 1) We need our own "fixed_xx.h" header file. I don't know why, and haven't had time to investigate, but there is a definite improvement when I use the attached fixed_c55x.h file which has turned all the maths into inline functions.

Is there any way to access only the narrowband portion of a wideband stream? I'd like to be able to encode the audio only once, but allow members in a conference to have some rough selection of bandwidth, and allow them to move to a lower-bitrate stream if there is a need to do so. Thanks, Matthias -- Matthias Granberry matthias@utdallas.edu (469) 371-0596 --- >8 ---- List archives:

It looks like I'll need to go further into the guts of speex to do this. I do, however, see some lines in nb_celp.c/nb_decode() that look interesting. I guess I'll play with it. I doubt that it will be terribly clean, though. Jean-Marc: Take a look at line 1195 in nb_celp.c (CVS). It reads "speex_warning ("More than to wideband layers found: corrupted

On Tue, Feb 18, 2003 at 06:09:43PM -0500, Jean-Marc Valin wrote: > Le mar 18/02/2003 ? 17:38, John Hayes a ?crit : > > If I encode something in ultra-wideband, can I decode it in wideband by > > chopping off bytes in every frame? > > All you have to do is use the --force-wb switch with speexdec. It will > decode as if the file were wideband, ignoring the ultra-wideband

I downloaded speex-1.2beta3-win32 binaries, and used the speexenc.exe and speexdec to process the file male.wav download from http://speex.org/samples I used both the narrowband and ultra-wideband mode: >speexenc -n --quality 3 male.wav n3.spx Encoding 8000 Hz audio using narrowband mode (mono) >speexdec n3.spx n3.wav Decoding 8000 Hz audio using narrowband mode (mono) Encoded with Speex

If I encode something in ultra-wideband, can I decode it in wideband by chopping off bytes in every frame? John --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed.