similar to: Need some help about speex settings

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

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

hi, I have a small and quick question. When speex divide the UWB speech signal into High and low bands, JMV said to me in HA that : "For ultra-wideband (0-16 kHz, 32 kHz sampling), I first split the band into wideband (0-8 kHz) and "very high band" (8-16 kHz). Then, the wideband itself is split into low (0-4 kHz) and high (4-8 kHz) band. So there's a total of 3 bands

When built with --with-fft=gpl-fftw3, libspeexdsp is not linked with libfftw3, while it uses symbols from it. This means every object linked with libspeexdsp should also be linked with libfftw3, but it is not something reflected in the pkgconfig file. Instead, link libspeexdsp with libfftw3 when --with-fft=gpl-fftw3, and remove explicit link with libfftw3 in objects build by the speex Makefile.

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

On Fri, Nov 14, 2008 at 3:57 AM, Vincent Burel <vincent.burel at vb-audio.com>wrote: > > Speech compression algorithms always are tunned to particular freq, > > else they would take tons of time. That's because they use knowledge > > that speech pitch (and other params) lies in well specified regions. > > Thus if you feed algorithm with wrong freq, you'll

Ronald, Although you can give Speex data at any sampling rate with any mode, it's a good idea to use the right mode for whatever rate you have. Speex is built for speech (not just any audio in general) and is sensitive to what kind of stuff is going on in certain frequency ranges. If you tell it your data is at one sampling rate and give it data with another sampling rate, its idea of

Hi there. I am having a little trouble understanding the frame sizes chosen by the codec. testenc_uwb.c from the speex-1.0 source distribution has a framesize of 640 hardcoded and makes use of this value exclusively. However, a mode query on the actual codec returns 320 as a framesize for this mode. int tmp; speex_mode_query(&speex_uwb_mode, SPEEX_MODE_FRAME_SIZE, &tmp);

I'm using Speex in Windows VoIP application and trying to implement echo cancellationI'm using waveInXXXX and waveOutXXXX API. I'm doing quite simple thing: After buffer is played (I get MM_WOM_DONE message) I'm just copying it's content to temporary playback buffer After buffer is recorded (I get MM_WIM_DONE message) I call speex_echo_cancellation(state, recorded_buf,

Hi all, I've built Speex 1.03 on Mac OS X. I encoded a raw PCM file successfully using: /usr/local/bin/speexenc raw_samples.raw --rate 44100 --be --16bit raw_enc.spx Warning: Speex is only optimized for 8, 16 and 32 kHz. It will still work at 44100 Hz but your mileage may vary Encoding 44100 Hz audio using ultra-wideband (sub-band CELP) mode (mono) If I decode to .wav, it works fine.

Hi, I have replaced most (but not all) of the float operations by integer operations, but it seems like the remaining ones take a long long time when emulated in kernel space (hence high system time). The other problem is that I don't have access to an ARM-based device (anyone wants to send me one?), so I'm doing all this blind... If you'd like to help, it can also accelerate things.

Oops... You've just found a bug. Seems like you're the first one to use that call. Anyway, it's now fixed in CVS (both trunk and 1.0.x branch). Thanks for the bug report. Jean-Marc Le mar 03/06/2003 à 01:16, Christian Buchner a écrit : > Hi there. > > I am having a little trouble understanding the frame sizes chosen > by the codec. > > testenc_uwb.c from

> I was wondering if anyone has experimented with Speex's wideband (16kHz) > mode at lower quality settings. In particular I have been using quality 3, > and with wideband input files the resultant frequency spectrum is limited to > about an upper end around 3.5kHz (almost telephony quality bandwidth). Has > anyone tried increasing the spectral bandwidth at the expense of

Hi Jean-Marc, I thought at quality 3 (wideband) - wb_submode1 that the 4-8k band was not using a codebook table. From the code I can see that some sort of "lsp" encoding is performed. What exactly does this encode? (I assume lsp means line-spectral pairs) The reason I am asking is I'm comparing the "effective" spectral bandwidth of Speex against the

Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) compression in the same bitstream What is the meaning of this? can i find more information about this somewhere? And what is packel loss concealment, an you enable this somewhere? thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, > 2. I don't have a good source of wav data for testing. I've noticed that > introducing bugs into speex (even gross ones like returning completely > incorrect codebook entries) tends to, sometimes subtly, degrade quality > instead of blowing up. Is there an existing set of source data - and > maybe even a test harness that will do binary comparison, so I can avoid

Alfred E. Heggestad wrote: > <...> > > If we don't get any comments in 1 week (by 22. May 2007) we will go ahead > and submit it to the IETF. Of course you can comment on it also after it > has been submitted, but we would like to get the input from the Speex > community first.. > thanks for all the input. please find attached an updated version of the draft. I

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'

Hi Please find an updated version of the Speex I-D attached. The only change is addition of the copyright conditions in Appendix A, as requested by Ivo. Many thanks for your input. I will give you a few more days before submitting to AVT working group /alfred Ivo Emanuel Gon?alves wrote: > Do not forget to add the "Copying conditions" to the RFC. > > Check