similar to: did I screw up encode?

This is going to take some explaining and I apologize in advance if any of this is found in the manual or sample code but I couldn't find it. I just graduated last may and this is my first experience with vocoders and dissecting a professional's code. I work for a company that is currently using a G729A vocoder from a 3rd party software company and is looking into speex so they no

Mike, Generally "Invalid mode encounterd" == "frames are misaligned" You should be getting 20 bytes from the encoder each time, and passing 20 bytes to the decoder each time. Is it correct that you have modeled your main loop after testenc-TI-c5x.c? If you look at encoded silence with a binary editor, you should be able to see the 20-byte repetition pattern. You can also

Jean-Marc was correct in that the 16bit value was the culprit for my encoding woes. after I changed that to a 32 bit value I believe it encodes correctly, but I really don't have much of any way to know this absolutely. I am using the 1.2beta2. I would use the enctest program, I have looked it over and based a lot of what I am doing on that code but the project I am developing this on is

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 thought I should be getting 20 words because in the windows app the command line repeats "nbBytes = 20" through the entire decode phase. I wonder how the frames got misaligned...right now I get 10 words of data followed by 10 words of 0's which I look at through a memory window in code composer. now I am pretty sure there is a terminator word that gets in there so that would make

Hi, I am using speex 1.2beta2 on a narrowband 16-bit, 8khz system that has a severe program space problem and will not fit speex in its normal operation. In an attempt to shrink speex I placed a breakpoint in every function and ran a decode and encode and removed the breakpoints that I hit. in the functions that had a breakpoint that I didn't hit I commented out those functions (as well as

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 All, I am upgrading my samba server from a workgroup to PDC server. I am doing this to make a Windows 2008 Terminal server happy. Eventually there will be a bank of them (thank you Virtual Box). Anyway, in my test bed, I have a Samba PDC (newly updated to PDC), a Windows 2008 server, and XP-Pro-SP3. Both Windows machines are able to join the domain and log in as users only in the Samba

Hello list, I am using Samba 2.2.5 configured as a Win2k domain member with a Win2k Adv Server box acting as Domain Controller. Samba is running on a Linux 2.4.18 box with the extended attributes and ACL support patches applied. I am using the ext3 filesystem on the filesystems being shared via Samba to the Windows 2000/XP boxen on the network. And I do have the winbindd daemon running and it

Hello, So, I just got through a very stressful couple of hours. I''ve been running a rails application for a few months on a dedicated server. The application isn''t really that intensive and has been serving roughly 50k requests / day. It''s been handling really well, really fast, and all is good. The deployment configuration I am using is apache 2.2.3 with

When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be added to the CFLAGS in libspeex/Makefile. GCC 3.1.1 added a new option "-msse" (see http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New Targets and Target Specific Improvements") to enable SSE instructions within the compiler's output (for appropriate architectures). Compiling speex on

# make make all-recursive make[1]: Entering directory `/tmp/speex-1.1.6' Making all in libspeex make[2]: Entering directory `/tmp/speex-1.1.6/libspeex' source='nb_celp.c' object='nb_celp.lo' libtool=yes \ depfile='.deps/nb_celp.Plo' tmpdepfile='.deps/nb_celp.TPlo' \ depmode=gcc3 /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I.

It's not really documented, but when you compile with --enable-sse, you need to add -march=pentium3 to the compile switches. That's actually a gcc requirement. Jean-Marc Le mer 21/01/2004 à 04:22, war a écrit : > gcc-3.2.2 + slack 9 + p4 2.6ghz (has sse/2) > > ./configure --prefix=/app/speex-1.1.4 --enable-shared --enable-sse > --with-ogg-dir=/app/libogg-1.1 >

# gmake Making all in libspeex gmake[1]: Entering directory `/tmp/speex-1.1.4/libspeex' if /bin/sh ../libtool --mode=compile gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1

Hi All, I'm trying to build speex for the mini2440 board, with this toolchain: http://www.friendlyarm.net/dl.php?file=arm-linux-gcc-4.3.2.tgz because speex is a dependency of the sip softphone 'linphone'. The 'configure' string I'm using is this: ./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm Other

Trying to build today's svn on fc5, gcc-4.1.0,amd64: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I.. -I/usr/include -O2 -fPIC -funswitch-loops -ftree-loop-linear -march=k8 -ftree-vectorize -pipe -mfpmath=sse -frename-registers -O3 -msse -MT nb_celp.lo -MD -MP -MF .deps/nb_celp.Tpo -c nb_celp.c -fPIC -DPIC -o .libs/nb_celp.o nb_celp.c: In function 'nb_encode':

Dear sirs, Speex fails to link with my application on symbian, sdk versions 2nd edition fp2 and fp3 with this errors: ..\..\..\SYMBIAN\8.0A\S60_2ND_FP2\EPOC32\RELEASE\ARMI\UREL\SPEEX.LIB(../../../SYMBIAN/8.0A/S60_2ND_FP2/EPOC32/BUILD/SRC/SPEEX/SYMBIAN/SPEEX/ARMI/UREL/SPEEX.o)(.text+0x158):Speex.c: undefined reference to `floor'

I'm aware of the problem, but I don't know how to get autoconf to handle that properly. If someone knows how to make that work with autoconf even with non-gcc compilers and with default CFLAGS, I'm interested. Jean-Marc Le jeu 01/04/2004 à 17:21, Michael T. Dean a écrit : > When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be > added to the CFLAGS in

for the bits init I am using speex_bits_set_bit_buffer and I don't use the write to or read from because the data is already in the buffer I am reading from and I am writing to the final buffer so I don't need to move arrays around. what part is the vocoder part of the decode? Thanks for your help! -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/06/07

Hi Jim, Thanks a lot for investigating. It definitely makes sense now. I'll fix the problem now. Is there any other place where you see that same (or similar) problem? Jean-Marc Jim Crichton a ?crit : > Jean-Marc, > > I dug into this further, and found that the warning occurred when PSHR32 > had a shift greater than 15. > > in fixed_generic.h, PSHR32 is defined as: >