similar to: Quality degradation on new versions

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

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:

Hi, I have been using speex version 1.0.5 on a text-to-speech program. Recently I upgraded to version 1.2beta1 and noticed that the waveform the I got after encoding and decoding on the new versions (beta1,beta2) is much more different than the original than on version 1.0.5. I also ran a PESQ comparison test on 700 voice samples and got better results in the older version (I used quality 9, and

Hello, I have this rare and weird problem in the encoder : when I encode and decode this specific speech sample (Attached) the first frame comes out wrong. I found that the error is in the encoder. My settings are : Version 1.2beta2, on linux, in floating point. Wideband. The highpass filter turned off. Perceptual enhancment is turned off. Quality is 9. The weird thing about it is that if I use

On Mon, Apr 19, 2004 at 02:46:44AM -0400, Jean-Marc Valin wrote: > OK, I'll try to do *something* about it. It'll be either "support the > 1.0 ABI" or "make sure the link will break". While the former would be > nice, I'm not sure I want to really want to force 1.2 to have the same > ABI as 1.0.x. More on this when I have some time to think about it.

The way I do this is to compute the number of frames (by dividing the size of my input by the number of bytes per frame and then calling speex_encode_int() that many times. Something like speex_bits_reset( &bits ); for( n = 0; n < num_frames; ++n ) { speex_encode_int( enc_state, (int16_t*)input_tail,

Hello, I intend to make a speex port for freescale DSP56F800/E. I downloaded the source code, but I not realize which function are called in which order for encode after calling speex_encode (or speex_encode_int) and speex_decode (or speex_decode_int). Could anybody help me on this? Thanks in advance Alexandre Penna

I'm only doing one frame using speex_encode_int greatly simplifies my code I'm not sure why the sample I was working off of was converting the shorts to floats then calling the other encode/decode methods. Based off of your suggestions I tried the following but I get the same result. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) {

Hi Tom, Thanks for your reply, I'm having a few difficulty's following you advise. You mention that I should be calling 'speex_encoder_int' & 'speex_decoder_int', I'm having problems finding these functions in the speex header. I am currenlty calling speex_encoder_init & speex_decoder_init in my test code, I have repeated the relevent bits of the example

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Assuming one prefers to use the speex_encode_int() and speex_decode_int() when available, but fallback to speex_encode() and speex_decode() if an older version if the lib is installed, how does one best make the determination? The only thing I can see to do is call speex_init_header() and look at the result. Even at compile time it seems one must compile a test app that outputs that data and then

> When I was going from Char to float and back looked very wrong to me it not only *looked* wrong! > as well, but I was just not sure (and still am) how to translate the > Char* audio stream generated by WaveIn to a format that can be > understood by Speex. Would using speex_decode_int and > speex_encode_int instead of speex_decode and speex_encode be the > answer? Using

This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

In short try calling speex_encode_int and speex_decode_int. The calls to speex_encode and speex_decode expects the data to be a floating point values. The data is passed by pointer and the compiler does not do the conversion. This is why you are getting the segfault on decode as the short is 16-bits and a standard float is 32-bits. Tom -----Original Message----- From:

Thank you for such a quick response. The only reason I started with Char buffers is because WaveIn and WaveOut on Windows XP accept/emit WAVEHDR structures, which store audio data in LPSTR, which is Char*. typedef struct { LPSTR lpData; DWORD dwBufferLength; ... } WAVEHDR; When I was going from Char to float and back looked very wrong to me as well, but I was just not

Begin forwarded message: Date: Mon, 5 Nov 2007 07:27:21 -0500 From: "Evgueni Tsygankov" <eugenet@rusmex.com> To: "Jean-Marc Valin" <jean-marc.valin@usherbrooke.ca> Cc: speex-dev@xiph.org Subject: RE: [Speex-dev] WaveIn/WaveOut and Speex Again, thank you for helping me. I know this might seem like a trivial matter to you and other experts in the field, but believe

Hi there, I have searched what seems like everywhere and was unable to find a .NET wrapper so that I can use speex in VB. I did find a speex.NET.dll but this didn't seem to work on what I needed. I therefore decided I could just use DllImport within VB .NET and create my own unmanaged links to libspeex.dll. With the help of this partial c# code

> Assuming one prefers to use the speex_encode_int() and > speex_decode_int() when available, but fallback to speex_encode() > and speex_decode() if an older version if the lib is installed, > how does one best make the determination? Well, for compile-time, I'd think that an #ifdef would do the trick. The only way you could do it at RUNTIME is if you perform a dlopen() on the

On Sun, May 16, 2004 at 06:03:47PM -0400, Jean-Marc Valin wrote: > Right now, I'm thinking of adding a speex_lib_ctl() call that would > support SPEEX_GET_VERSION (and return a string) or > SPEEX_GET_MAJOR_VERSION and SPEEX_GET_MINOR_VERSION (and return ints). > I'm open to other suggestions though. If there's anything you'd like to > see in the API for 1.2, say it