similar to: re: decoder issue in sb_celp

Jean Marc- Thanks for looking into this- I think I needed to give you a bit more info! Sorry for such a vague initial report. So most of these problems seem to be coming from the lsp_to_lpc function. In particular the following: xout1 = xin1 - 2.f*x_freq[i2] * *n1 + *n2; xout2 = xin2 - 2.f*x_freq[i2+1] * *n3 + *n4; ... in the floating point version this code can

> Thanks for looking into this- I think I needed to give you a > bit more info! Sorry for such a vague initial report. > > So most of these problems seem to be coming > from the lsp_to_lpc function. In particular the following: > xout1 = xin1 - 2.f*x_freq[i2] * *n1 + *n2; > xout2 = xin2 - 2.f*x_freq[i2+1] * *n3 + *n4; > > ... in the floating

hi, am trying speex on TI c54x dsp. does anyone has any idea whether we can make both the coder AND decoder run in about 10ms for a 20ms frame for this dsp, looking at narrowband, no VAD/CNG/VBR, using a low complexity, say 1, for a midrange bitrate, say 15kbps? was the c55 dsp able to run real-time on speex for the above configuration? can someone share their timings? tia! oh yes, just

Tom Harper a ?crit : > A little more info on this: > > I backtracked deeper into this and it looks like excBuf > is corrupted, which is corrupted by low_innov_alias > being invalid. However it is not entirely clear where > that gets initialized (in sb_celp it is set to out+st->frame_size) While looking for the problem, I ended up fixing two other things that could be

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'm glad to hear that my data size can be shrunk considerably, however I do not know the minimum values that I would set the static arrays to be. I hate to be a bother but could you tell me the minimum values for these arrays/structures in the state structure? Thanks! encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch

I noticed that in the narrow band and wide band destroy functions only the main pointer is being freed. I think that it should be: void nb_decoder_destroy(void *state) { DecState *st; st=(DecState*)state; speex_free (st->inBuf); speex_free (st->excBuf); speex_free (st->innov); speex_free (st->interp_qlpc); speex_free (st->qlsp); speex_free

When updating the speex sources from svn tree, I found that the following revision has corrupted the deallocation (segmentation fault): ------------------------------------------------------------------------ r9320 | jm | 2005-05-27 15:05:05 -0300 (Fri, 27 May 2005) | 2 lines Proper de-allocation When compiling with the 9316, everything works fine. but when I update with later

Hello Jean-Marc. First of all, thank you for your awesome work on speex! In the current version in SVN the wideband encoder/decoder doesn't correctly pass the parameter of SPEEX_SET_SUBMODE_ENCODING to the underlying narrowband codec. My patch fixes this. Then I have a question regarding the EPIC_48K mode. Should the perceptual enhancer work with this mode? At the moment it is enabled by

> In the current version in SVN the wideband encoder/decoder doesn't > correctly pass the parameter of SPEEX_SET_SUBMODE_ENCODING to the > underlying narrowband codec. My patch fixes this. Thanks. Strange that this didn't cause problems before. > Then I have a question regarding the EPIC_48K mode. Should the > perceptual enhancer work with this mode? At the moment it is

> I don't think that the stack is getting corrupted- but I can't > rule it out- so what I will do is try to record some > samples to a file to reproduce this outside of the app. > Is there a standard place to post test files? It would indeed be much easier to deal with a stand-alone file. If possible, please upload it to a website and send the URL. Otherwise, just send it to

Hi again JM, I hate to nit-pick, but it seems that the memory pointed to by the member "h1_mem" in the SBEncState structure is allocated, freed and initialized but never actually used. Perhaps it's a leftover from some previous incarnation of the QMF code? Hope I'm not wasting your time here. John Ridges

Jean Marc, I don't think that the stack is getting corrupted- but I can't rule it out- so what I will do is try to record some samples to a file to reproduce this outside of the app. Is there a standard place to post test files? Note also I am intentionally stressing out speex here in part to figure out what the issue is- 99.9% of the time this issue never happens but right now it is not

Thank you, I really appreciate the help. -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/07/07 8:34 AM >>> Michael Jacobson a ?crit : > I'm glad to hear that my data size can be shrunk considerably, > however I do not know the minimum values that I would set the static > arrays to be. I hate to be a bother but could you tell me 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.

I am trying to implement a relatively high number of encoders (24/32) on a single DSP and would like to minimize the memory requirements. Has anyone optimized the persistent EncState memory allocation for multiple channels. The default C64x fixed point implementation allocates 5280 bytes of persistent memory per encoder. I'm willing to restrict my settings to complexity 1, quality 3. It

Hi, So 9316 works and 9320 doesn't? How about latest SVN. I just ran everything in valgrind and saw no error at all. Can you give more info on how to reproduce (with speexenc)? Jean-Marc Le mercredi 22 juin 2005 ? 21:19 -0300, Dario Andrade a ?crit : > > > When updating the speex sources from svn tree, I found that the > following revision has corrupted the deallocation

Hi, all. I have two questions about wideband encoding. >From "testenc_wb.c"... 1) tmp=8; speex_encoder_ctl(st, SPEEX_SET_QUALITY, &tmp); tmp=3; speex_encoder_ctl(st, SPEEX_SET_HIGH_MODE, &tmp); tmp=6; speex_encoder_ctl(st, SPEEX_SET_LOW_MODE, &tmp); How to set high_mode and low_mode, if quality is set to '9'? When I set quality '9'

> Another issue is the memory allocations distributed so many places that > it's hard to provide a single memory initial function interface. > > In a VoIP case on ARM, the total memory size for speex codec should be > known at the inital stage since all the memories are allocated > at the initial stage. If you want everything in the same big block, all you need to do is

Hi everyone, As you may have guess, Speex 1.2 is slowly approaching, though there's still a lot left to do so I can't say how long it'll take. I thought this was the right time to ask if there's anything missing or that can be improved to make 1.2 better. At this point, it can't be anything major, but there are still some changes that are possible, e.g: - Improving some