similar to: Problem compiling testenc.c on WinXP(newbie)

Hello, I want to compile testenc.c with Borland C/C++ compiler, but get a lot of errors. What's wrong? Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland testenc.c: Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland Error: Unresolved external '_speex_encoder_init' referenced from D:\SPEEX\TESTENC.OBJ Error: Unresolved external '_speex_decoder_init'

hello, i try to add a speex compression on the TDM Talkthrough on the BF-533 EZ-KIT LITE but when i compile i obtain the following errors: [Error li1021] The following symbols referenced in processor 'p0' could not be resolved: 'speex_bits_destroy [_speex_bits_destroy]' referenced from 'Debug\Process_data.doj' 'speex_bits_init [_speex_bits_init]' referenced from

I submitted a version of testenc.c to this list MONTHS ago that fixed this problem. It uses a reconfigurable group delay. If you had given me cvs access I could've committed the changes myself. Anyway, the file is attached (again). Maybe this time you'll actually notice the email. Sorry if I seem a little short. It's just very annoying to put the time into learning and improving a

Actually, the SNR calculation in testenc has been broken for a while. The reason for taking the last frame was that the codec would introduce a one-frame latency. I changed that to half a frame (10 ms) a while ago and never updated testenc. Jean-Marc Le lun 01/09/2003 à 13:12, Mike Dunn a écrit : > Hi all, > > I'm new to the group. I'm looking at the speex code with an

Hi all, I'm new to the group. I'm looking at the speex code with an eye towards maybe helping out with either codec optimization or fixed-point implementation, The SNR calculation in testenc.c and testenc_uwb.c doesn't make sense to me. The code is { float enoise=0, esig=0, snr; for (i=0;i<FRAME_SIZE;i++) {

DEAR: I SEEM A BUG FOR speex-1.2rc1.tar.gz ON BUILD IN USING IT. PLEASE LOOK: ===================================================================== make all-recursive make[1]: Entering directory `/tmp/speex-1.2rc1' Making all in libspeex make[2]: Entering directory `/tmp/speex-1.2rc1/libspeex' /bin/sh ../libtool --mode=link gcc -g -O2 -fvisibility=hidden -O3 -msse -o testenc

Hi Jim, Actually, I don't see anything wrong with the internal structure having a different type than the interface, as long both types are big enough to hold the possible values (in this case 0 and 1). Though, as you pointed out, testenc needs to be fixed to use spx_int32_t instead of int. I'll change that. Jean-Marc Jim Crichton a ?crit : > st->highpass_enabled is typed

Jean-Marc, The trouble is that one cannot identify the type difference without reading the nb_celp.c source file, and this parameter is treated differently than other, similar parameters. It would seem like the most intuitive approach would be to match the interface to the structure. This is a trivial point, of course. I have attached a patch to the two TI interface files, which adds the

Jean-Marc, Here are the patches, broken out one per file. I did some additional work in the testenc files based on Peter Mlakar's post to make it easier (though still a bit klunky) to try different rates. These changes also incorporate the file window.c into the builds, change the decoder startup delay to account for the change in the algorithm delay from 10ms to 5ms, and change bits.c

For clarity I attached modified testenc.c I used to test my code. On 2/14/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > I also think that having rame_num.c in libspeex, code size could be > > reduced and simplified slightly by using speex_skip_wb_frame() in > > nb_decode() instead of duplicating code. > > Well, the code is a bit different (e.g.

> > Mark, > > I'm in for some work--time permitting. Pick me off a chunk and send it > my way. I've never done float->int conversions, but I do love > code optimizations. I just wish I knew x86 assembly. :) > > Cheers, > David Glad to hear from you. What's your background? I don't think we should use assembly just yet. Let's get a C version

I suspect I am missing something basic but I do not seem to be able to get the sampleenc and sampledec programs to work together. I think I do not have a compile swtich of flag set correctly. Backgound information: 1) 1.0.4 tar package 'make' worked and installed on a mandrake 10.0 linux 2) speexenc and speexdec appear to work fine. 3) testenc and testenc_wb work fine, though I

I suspect I am missing something basic but I do not seem to be able to get the sampleenc and sampledec programs to work together. I suspect the decode operation is failing, but I cannot find out why. Backgound information: 1) 1.0.4 tar package 'make' worked and installed on a mandrake 10.0 linux 2) speexenc and speexdec appear to work fine. 3) testenc and testenc_wb work fine, though

Jim Crichton, I'm trying to run speex on omap 1610 platform and i saw that you have a patch for c55. When i saw your mail about this, i decided to ask you for send me those files above: include\config.h (not automatically generated, sets memory sizes, enables manual alloc) include\speex\speex_config_types.h (match Speex types to compiler types, not generated from types.in

Hello. I want to compile trunk speex. ./configure --prefix=/opt/speex --enable-option-checking --disable-silent-rules --disable-maintainer-mode \ --enable-shared=yes --enable-static=yes --enable-fast-install=yes --enable-dependency-tracking \ --enable-libtool-lock --enable-valgrind --enable-sse --enable-binaries --enable-vbr \ --disable-fixed-point-debug --enable-vorbis-psy --with-pic

Jean-Marc, I have attached a small patch with modifications to arch.h, bits.c, and misc.c. This contains the few mods remaining to support the various fixed point TI DSPs after the work that you did at the end of May (thank you for this). arch.h: Add switch for compilers not supporting "long long" (C55x does, C54x and older C64x does not) bits.c: Allow external definition for max

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

I am wont to decode a speex 11kbps 8kHz 16bit to a raw data 8kHz 16bit LSB on a c5509. Trying to understand the "testenc-TI-C5x.c" exsample, but it looks to me wary complicated. Is there more documentation for the exsample or a decoder exsample available? Can somebody help? Peter -------------- next part -------------- An HTML attachment was scrubbed... URL:

> Ok, here is cleaned up and fixed version. > > * Function is named speex_get_num_frames() now and return > number of frames, as you suggested. > * WB layers sizes are taken from wb_skip_table[], while NB frame > sizes are calculated with speex_mode_query(). Looking better. Just make sure to remove the stuff that isn't C99-compatible (e.g. // comments). > I've

I'm confused about the format of the PCM/WAV data for speex_encode & speex_decode speex_encode(enc_state, input_frame, &bits); In the manual, it says "input_frame is a (float *) pointing to the beginning of a speech frame" (for encode) But I've found that in speexenc.c and testenc.c, short* is used instead of float* So, isn't it signed 16 bit samples(if