search for: var_array

Guys, Program stack is getting overflowed when I create and destroy encoder instance continuously for around 30 times. How can I ensure stack is completely freed when I destroy the encoder instance? I tried with VAR_ARRAYS. But Its giving me errors while I try to compile. I suppose VAR_ARRAYS allocates local variables as arrays so that they could go on to stack and finally when we leave the function, the stack is freed. when I use VAR_ARRAYS, I get this error " declarations may not appear after an executable s...

Did you try replacing the create() with separate malloc() and init() steps. If so, which of the two was causing the problems? BTW, you need a C99 compiler for VAR_ARRAYS to work, although you may be able to use USE_ALLOCA. Jean-Marc On 05/27/2013 08:36 AM, Fezin E T wrote: > Guys, > > Program stack is getting overflowed when I create and destroy encoder > instance continuously for around 30 times. How can I ensure stack is > completely freed whe...

...the bug is most > likely *not* around line 414. It's probably some sort of memory > corruption somewhere else (quite possibly outside of Speex). Do you have > any more information? What CPU? What's the value of best_ntarget[j]? Is > SSE enabled? What's the allocation method (VAR_ARRAYS/USE_ALLOCA)? What > compiler. > gcc: Reading specs from c:/MinGW/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=c,c++,f77,...

Jean-Marc, Thanks for the response and the helpful info. I am trying to get the library to build without using the pseudostack define, and use either VAR_ARRAYS or ALLOC, but it seems the global stack is not defined. Where do can I define this in my example? VR -----Original Message----- From: Jean-Marc Valin [mailto:jmvalin at jmvalin.ca] Sent: Tuesday, February 20, 2018 5:40 PM To: Rodriguez, Vince; opus at xiph.org Subject: [EXTERNAL] Re: [opus] De...

...(--> 5ms)? ?- rate = 128 kbit/s (stereo) ?- vbr_rate = 0 ?- prediction = 2 ?- complexity = 10 ? Why do we need additionally a GLOBAL_STACK_SIZE ? Could these allocations also be redirected to a common method, like celt_alloc() ? It is not really clear to me what is the idea behind the switches VAR_ARRAYS, USE_ALLOCA, GLOBAL_STACK_SIZE and how much RAM must be allocated (how/where?) for any (or at least for our) configuration ? ? thanks a lot for your answers, Marko. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/201...

Ok, I got a strange case.. I got a bugreport from a user about my application crashing on him. After a bit of trouble, I got him to report back the module and offset it crashed at (win32). I always retain a copy of my symbol files for my release builds, so tracking down the crash address leads to: (gdb) list *0x6d5c2213 0x6d5c2213 is in split_cb_search_shape_sign (cb_search.c:414). 409

...onfig.h`): * `WORDS_BIGENDIAN` * `FLOATING_POINT` * `FIXED_POINT` * `FIXED_POINT_DEBUG` * `DISABLE_FLOAT_API` * `_USE_SSE` * `ARM4_ASM` * `ARM5E_ASM` * `BFIN_ASM` * `TI_C55X` * `DISABLE_VBR` * `USE_SPEEXDSP` * `VORBIS_PSYCHO` * `HAVE_GETOPT_H` * `HAVE_GETOPT_LONG` * `VAR_ARRAYS` * `USE_ALLOCA` * `HAVE_ALLOCA_H` * `USE_SMALLFT` * `USE_KISS_FFT` * `USE_GPL_FFTW3` * `EXPORT` * Installation supported * Package config mode supported How to use ========== Required tools and libraries: * CMake >= 3.1 * Ogg, SpeexDSP packages (headers and import libraries), rec...

Hi, Here's an updated resampler patch against current SVN. It includes SSE and SSE2 optimizations (the latter if included by _USE_SSE2). Best regards, Thorvald -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: speex-resampler-update.diff Url: http://lists.xiph.org/pipermail/speex-dev/attachments/20080426/e055077f/attachment-0001.txt

...limited, I cannot trace this any further now. ?Could you please check the figure given in celt_alloc() and/or the folling loop, which is populating the allocated memory.? ?The other allocations seem ok. thanks a lot, Marko. ? ? our config: ?- version = 0.9.1 ?- ARM9, FIXED_POINT, DOUBLE_PRECISION, VAR_ARRAYS ?- f<s> = 48kHz ?- frame_size = 240 (p.ch.) (--> 5ms)? ?- rate = 128 kbit/s (stereo) ?- vbr_rate = 0 ?- prediction = 2 ?- complexity = 10 ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20101203/7085b16a/...

...ortex M7 device running at 400MHz. Con you please suggest the best configuration directives that I have to set in the config.h file in order to obtain the best perfromances on the cortex M7 architecture? Actually I have compiled libopus 1.2.1 with the following cnfiguration parameters: #define VAR_ARRAYS  1 #define FIXED_POINT  1 #define OPUS_BUILD  1 #define OPUS_ARM_INLINE_EDSP  1 Con I define something else to further improve the performances? Thank you in advance for the support Best regards. -- Logo Ing. *Daniele Guidi * HW/FW PROJECT ENGINEER tel: +393338256799 *EmEl Systems* Via Cesare B...

On 02/20/2018 06:48 PM, Rodriguez, Vince wrote: > I am trying to get the library to build without using the pseudostack > define, and use either VAR_ARRAYS or ALLOC, but it seems the global > stack is not defined. Not sure what you mean here. If your compiler supports C99 VLAs, then by all means just define VAR_ARRAYS and you're good to go. If not, the second best option is alloca(), which you can use by defining USE_ALLOCA. If your compiler...

...oks are stored as tables of char, so you're probably wasting a lot of space from the fact that chars on C5x are 16-bit long. You might be able to pack the values in one 16-bit value and unpack in the code. As for the memory allocation in the encoder, the best is to use C99 variable-size arrays (VAR_ARRAYS) or alloca (USE_ALLOCA). Otherwise, you can make the static array much smaller. For 8 kbps, the total RAM requirement (not counting code or static tables) should be around 4 kB (2 kWords). Jean-Marc Michael Jacobson a ?crit : > Hi, > > I am using speex 1.2beta2 on a narrowband 16-...

...nks! > > encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp > mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch > > decode: stack excBuf interp_qlpc old_qlsp mem_sp pi_gain What I meant is that you can reduce the stack part (assuming you're not already using VAR_ARRAYS or USE_ALLOCA). The other variables above still require the same size they are currently using. For the stack, the easiest way to measure (it's platform-dependent to some extent), the easiest is to fill the memory with 0xdeadbeef and see how far gets written. The amount of stack used is exactl...

...le-fixed-point --enable-arm5e-asm" options. If I use just "--enable-fixed-point", then it runs fine, but once I add "--enable-arm5e-asm" it start crashing (I use testenc to test it). Further investigation showed, that it does not crash, if I enable arm asm but disable both VAR_ARRAYS and USE_ALLOCA in config.h. This tested with speex svn rev13928 and with 1.2beta3 (svn rev14298). gcc version is 4.2.0 I guess it may be some alignment problem or so, like with MS compilers? Did anyone had same problems? Any good ideas and directions where to look and debug are welcome. -- Re...

...gcc for win32) doesn't officially support using gcc 4.0 and 4.1 yet (apparantly there have been some issues), so there are no binary packages. But if you think it helps, I can compile gcc 4.1 and give it a shot. >> Compile flags: >> DEFINES += NDEBUG WIN32 _WINDOWS HAVE_CONFIG_H VAR_ARRAYS VORBIS_PSYCHO > > VORBIS_PSYCHO is an *experimental* feature and should not be enabled > unless you want to do research with it. A while back you asked for testers of this and I volunteered :) So far, my testers seem positive, but I have no idea if that is because I told them to expec...

The opus code default compiles on -o2 optimization level. I would like to change it to -o3. I have tried doing the changes in makefile.unix . The change is not getting reflected. I am building the code in Code composer studio for TI processor C6000. Could anybody help me with this -------------- next part -------------- An HTML attachment was scrubbed... URL:

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: maleout12may.wav Type: audio/wav Size: 95884 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20050524/57112d0c/maleout12may-0001.bin

Hi,I have been trying some different sample rate and bitrate combinations to get a feel for how CELT behaves,too, like Andrew Lentvorski. But I want to use VBR option.I want to ask a question about VBR in CELT codec.Can we use VBR option in CELT ??? "byte_per_packet" variable in code means constant bit rate, does not it ?In this code : bytes_per_packet is constant.len =

Hi, I'm using the Speex codec on my Blackfin-based board, and plain-C performance is pretty poor. Decoder is OK (something 25 MIPS for wide-band). But Encoder is not (wide-band quality 8, complexity 1): - 162 MIPS with Analog-Devices lib - 128 MIPS with 1.2beta2 (faster but not working) I don't worry that much, as it's not the optimized version, and everything is running in SDRAM.

...nt: Wednesday, October 17, 2007 1:56 AM > To: St?phane Lesage > Cc: speex-dev@xiph.org > Subject: Re: [Speex-dev] Blackfin port on Visual DSP, Michael Shatz ? Salut Jean-Marc, After 1 month busy on other projects, I can finally answer you: > Some things to check. Do you compile with VAR_ARRAYS? If not, > you can probably reduce the size of the managed stack. In > terms of data RAM, everything should fit into SRAM easily. No I didn't know this macro. According to the sources, I understand it's destined to compilers supporting run-time size for local arrays on the stack....