similar to: RE: [Speex-devel] Subject: Problems with win32 port of Speex

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

(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

hi, i am using AVTransmit3.java for transmitting audio, how can i implement JSpeex or speex for compression and encoding. please give me some idea about this. shankar.s speex-dev-request@xiph.org wrote: Send Speex-dev mailing list submissions to speex-dev@xiph.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xiph.org/mailman/listinfo/speex-dev or, via email, send a

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 downloaded speex-1.2beta3-win32 binaries, and used the speexenc.exe and speexdec to process the file male.wav download from http://speex.org/samples I used both the narrowband and ultra-wideband mode: >speexenc -n --quality 3 male.wav n3.spx Encoding 8000 Hz audio using narrowband mode (mono) >speexdec n3.spx n3.wav Decoding 8000 Hz audio using narrowband mode (mono) Encoded with Speex

Juha Heinanen writes: > any idea why size of wav file doubles when it is encoded to speex and > back to wav: > > $ ls -ls testi.wav > 40 -rw-r--r-- 1 foo foo 40674 May 4 14:38 testi.wav > > $ speexenc --denoise --agc --quality 10 testi.wav testi.spx > Encoding 8000 Hz audio using narrowband mode (mono) > > $ ls -ls testi.spx > 20 -rw-r--r-- 1 foo foo 16405

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

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

Hi all, i'm going to try to create an app using libspeex (Speex 1.1.10) and Visual Studio and just have a few questions. First, what's the difference between libspeex and libspeex_dynamic? Do I need to include both projects in my new workspace? Next, how do I enable fixed_point using libspeex? Am I correct in assuming that an ARM processor would be able to record speech as speex files

this is not really a development question, but i didn't find another mailing list to ask it. any idea why size of wav file doubles when it is encoded to speex and back to wav: $ ls -ls testi.wav 40 -rw-r--r-- 1 foo foo 40674 May 4 14:38 testi.wav $ speexenc --denoise --agc --quality 10 testi.wav testi.spx Encoding 8000 Hz audio using narrowband mode (mono) $ ls -ls testi.spx 20

Hi all, I've another trivial request: Is there any particular reason why speexenc and speexdec return 1 on successful completion? It would be preferable if they returned 0 unless there were errors, to be consistent with other *nix utilities and to allow for easier scripting (eg speexdec sample.spx && cp sample.spx somewhere) Would anyone be against this? TIA, Bernard. --

Dear Speex codec community: I am working on conversion of voice files. I could not figure out how to use speexdec.exe 1.2.3 in piped mode in order to avoid the creation of the potentially large intermediate *.wav or *.pcm files. Any pointer to web or file of instruction is appreciated. Attempt (one long command line, failed): type d:\test.spx | "d:\speex 1.2.3\bin\speexdec.exe" - -

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 -- I'm looking at adding Speex decoder and encoder support to the Miles Sound System, a commercial library used by game developers on various platforms including PCs, the Mac, and game consoles. As part of my initial evaluation, I've gone ahead and downloaded the 1.0.4 and 1.1.1 Win32 binary distributions and played around encoding and decoding various files with the speexenc.exe and

Hi Please acknowledge this message as I am not sure if your organizations still exist. On trying to integrate your 3 formats into an app I find that the position of the start of each format ID differs. Both "vorbis" and "fLaC" start at char 29 (the 30th char in the file) and "speex " starts at char 28 (the 29th char in the file). Speex appears to correlate with

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

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 here is something I couldn't see on the description page. We need to convert to 8 bit audio right? I'm assuming narrow band is 8 KHz 8 bit. Wide band is 16 KHz 8 bit. UW band is 32 KHz 8 bit audio? George -----Original Message----- From: Tom Grandgent [mailto:tgrand@canvaslink.com] Sent: Tuesday, October 03, 2006 11:42 AM To: Bertie Coopersmith; George Ou Cc: speex-dev@xiph.org

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 all, thanks Jean for the codec. I am new to speech coding. Am interested to implement speex on a TI dsp, say C54. just downloaded speex v 1.1.6. when I removed optimisation flags for win32 in libspeex.dsp, I get a slightly different output for decoding using speexdec.exe (debug version). no prob for speexenc.exe except for some differences in the ogg header. for anyone interested, i