similar to: Automated Batch Tests

I realize that hearing tests are far superior for calibrating codec internals, particularly the perceptual enhancement. The tester is for finding gross mistakes like overflows. The test program includes code to subsample the 32Khz source down to 8 and 18 Khz. I've broadend the tests to try all the possibilities like VBR, perceptual enhancement, complexity and quality. The results are

The results are at www.rational.co.za/speex.csv Each of the 11 quality settings is tested 3 times (narrow, wide and ultra wide band). Strangely narrow band quality 11 outperforms all wide band tests, but it can be due to my subsampling or some other inaudible effect like delaying. You can import it into Excel and sort it by SNR or other value. Divide the bits by 24 to get the bps. The

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

Hmm, the delay caused by the filters in the speex UWB mode seems to be 509 samples. I used the GoldWave editor to determine the offset. I have always been confused by the SNR output in the testenc source code. It did not make sense because it uses a 640 (=FRAME_SIZE) offset for its SNR calculations. After changing the calculation method, the SNR readings are much better. I may decide to adjust my

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

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++) {

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

> > 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

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, First of all - thanks, turning the highpass filter off was what I needed, and the waveforms match now. But, when i did the PESQ tests again I found an interesting result : version 1.0.5 still got a slightly better average score, but the standard deviation on version 1.2 beta1 was much smaller. The cause for that is this - on some samples versions 1.0.5 and 1.2beta2 produced a single

This is a really good point, and definitely a recurring theme on this mailing list. :) I wonder, what are some better options for handling this issue, other than to keep saying "just use 8/16/32kHz"? - Extend Speex to support other sample rates (seems unlikely..?) - Integrate a resampling algorithm into libspeex - Maintain a list of recommended resampling libraries that work well

Hi Aviv, Does the audio sound bad? You can try turning off the highpass filter (which was not in 1.0.5). This code is from ti/testenc-TI-C5x.c in the source tree: /* Turn this off if you want to measure SNR (on by default) */ tmp=0; speex_encoder_ctl(st, SPEEX_SET_HIGHPASS, &tmp); speex_decoder_ctl(dec, SPEEX_SET_HIGHPASS, &tmp); - Jim ----- Original Message ----- From:

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

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

Actually, it looks like this is already done in Speex as of revision 7150 in SVN (7/15/2004). As long as HAVE_CONFIG_H is defined in the project settings (which it is in all of the project files in SVN), win32\config.h should be included, and this has #define inline __inline in it. Oleg - you should make sure HAVE_CONFIG_H is defined in your project settings. And, you didn't say which

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.

Since two people have asked me to open the source code on my work-in-progress Integer Speex project, I have put it up onto my site www.openacm.org as a download in the project tree. the suggested directory structure is as follows, i.e. the speex source folder should be on the same directory level as the sphinx filder. peex-1.0.1 (ideally the folder from within the SpeexACM source archive)

Ok, I figured it out. :) This seems to work: 1) Call speex_bits_read_from() once, specifying the location in memory of the compressed data, and the total length of that data. 2) Keep calling speex_decode() until speex_bits_remaining() returns 0. Then you don't have to keep track of the # of frames per packet, or the size of each compressed frame. It's done magically by the codec.

Hi, Ref the disucussion on IRC yesterday; here's a patch which makes a bit more data from the analysis of the preprocessor and the echo canceller available. For the preprocessor: - Size of power spectrum. - Power spectrum and noise estimate of the previous frame. These are given as squared values, so sqrt() to get values in the 0->32767 range. - Current amplification level

I have no problems compiling with Borland compiler (in fact it helped uncover a couple of math issues during run-time). I use BDS 2006. What's happening in your case is that the Speex itself is not linked in. I suggest you create a library out of the C sources and link it in with your test app. HTH, .a -----Original Message----- From: speex-dev-bounces@xiph.org