similar to: problems with encoding speex

The encoded speex file should, by convention, be given the '.spx' extension rather than '.wav', but that is not the issue. What appears to be happening is that the '.wav' extension on your named output file from speexdec is not being recognised as '.wav' and, consequently, the file is being written as 'raw' data without the wave file header. I am not sure

I suggest that you write the command line as Jean-Marc suggested: speexenc sample.wav - | speexdec - sample_out.wav I have tested this and it works as expected. You need to specify the '-' for stdin and also for stdout. John As an aside, I notice that the wave output from speexdec does not write the wave file header when the output is destined for stdout. I believe this is incorrect

Hello Jean-Marc, I have completed some very basic testing with unexpectedly excellent results. I am posting this to the reflector to encourage others into similar experiments. My experiment consisted of processing a 200-second long sample taken from a ham radio shortwave receiver, with a variety of signals (some strong, some weak - that is, weaker signals have more noise, and the noise is

Can you post the input and output file on the web and specify what options you're using (use speexenc/speexdec, *not* your own code). Jean-Marc Yanxin Cui a ?crit : > Would it help if I scale the input wav data before encoding to spx? > One interesting thing is if I encode the same wav file to spx(or > decode the same spx file to wav ) on Windows platform, then there is > no

> > I had no trouble building the ogg, vorbis and speex libraries. Also, > > speexenc.exe built correctly. However, speexdec.exe will build but does not > > create output (either to soundcard or to pcm/wav) and eventually crashes. > > I'm not sure I understand. In the first part, you say you have trouble > building speexdec and here you say speexdec does build but

It's working fine now... Thanks for your help --- Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> wrote: > OK, that was a stupid error in the le_int prototype. > It's fixed in svn > now. > > Jean-Marc > > Le mercredi 28 septembre 2005 ? 11:53 +1000, > Jean-Marc Valin a ?crit : > > OK, it seems like I screwed up the wav header code > between

OK, it seems like I screwed up the wav header code between 1.1.8 and 1.1.9. Everything seems fine (playing to soundcard also works), except that the length reported for the wav is too short, which is why it stops player. Actually forcing the player to continue past the end gives the whole file. I'll check what went wrong and try to fix it when I have some time. It's likely in speexdec.c or

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

OK, that was a stupid error in the le_int prototype. It's fixed in svn now. Jean-Marc Le mercredi 28 septembre 2005 ? 11:53 +1000, Jean-Marc Valin a ?crit : > OK, it seems like I screwed up the wav header code between 1.1.8 and > 1.1.9. Everything seems fine (playing to soundcard also works), except > that the length reported for the wav is too short, which is why it stops >

Hi, Here's a couple things to look at: 1) Are you using your own encoder and decoder? If so, try with speexenc and speexdec. 2) Is PocketPC big endian? If so, try defining WORDS_BIGENDIAN when compiling Speex. 3) The "This doesn't look like a Speex file" error sounds very suspicious because it only involves looking at the first chars of the first packet and looking for the

(replying to the new list: speex-dev@xiph.org) > I'm having trouble building the 'speexdec' executable in the win32 port of > Speex. I'm using MSVC++ 6.0 on both a Win2000 and a WinXP box (the error > occurs on both machines). The sources are fresh from CVS as of today. Can you check whether or not you have the same problem in beta 2? > I had no trouble building the

Dear Jean-Marc and Peter: Thank you both very much for your time and advice. I did not realize that Lame MP3 code has a -r option (without reading its code). I have tried the suggested command lines verbatim with the added -r option, along with other combination of option settings. I could not figure out how to eliminate the distortion in the result, like voice turning either high or low

Are you using speexenc/speexdec? Which plateform? Jean-Marc Le mardi 27 septembre 2005 ? 17:32 -0700, Christina Saputra a ?crit : > Hi, > > I just started using speex recently and I've been > having problem with Speex ver. 1.1.10 decoder. I used > Speex to encode a wav file to spx then decode it back > to wav file to see the voice quality that results from > different

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:

Hi Bernhard, Can you confirm I'm understanding everything correctly? You encode with the same encoder and then decode with either A) blackfin assembly and fixed-point or B) fixed-point only on Blackfin. Then A) sounds bad and B) sounds good. If you do the same in narrowband, it sounds OK. Is that correct? If that's the case, it's *probably* some kind of bug and/or invalid assumption

> Is it possible for me to encode a sample.wav file to encoded.spx using > sampleenc.c and decode it using sampledec.c and store the output in a > output.wav and play it using aplay? Will I be able to do the above? > Please help me, I am new to speex. If i am wrong please correct me. No, sampleenc/sampledec work on raw (headerless) files. Either you'll need to work on raw files,

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 folks, I'm having trouble building the 'speexdec' executable in the win32 port of Speex. I'm using MSVC++ 6.0 on both a Win2000 and a WinXP box (the error occurs on both machines). The sources are fresh from CVS as of today. I had no trouble building the ogg, vorbis and speex libraries. Also, speexenc.exe built correctly. However, speexdec.exe will build but does not create

Hello all, I'm testing the Speex codec for my diploma thesis on a BF-533 Blackfin under uCLinux (2005R3 RC3 release). I successfully compiled the Speex (1.1.11-svn) and I can encode/decode wav-files on my STAMP-board using the speexenc/speexdec sample apps. But I encountered that the decoded file sounds strange/noisy, when compiling with "--enable-blackfin-asm" +

I test the speex codec effect int the version of 1.2rc1. Encode a wav file which sample rate equal 44100 the command line like this: speexenc.exe --ultra-wideband --bitrate 20000 test.wav test.ogg I play test.ogg in windows media player, it sounds acceptable.( I have install the decoder oggcodecs_0.83.17220-win32.exe.) After that decode test.ogg: speexdec.exe test.ogg test_dec.wav when I