similar to: different output for opt/non-opt on win32 platform

hi, Jean-Marc, thanks for the comments. > > 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. > > What difference in the ogg header? It's

Le mercredi 05 janvier 2005 ? 13:37 +0800, tunkeat a ?crit : > thanks Jean for the codec. My first name's Jean-Marc BTW :-) > I am new to speech coding. Am interested to implement > speex on a TI dsp, say C54. I think I've heard someone was working on that before... > just downloaded speex v 1.1.6. > when I removed optimisation flags for win32 in libspeex.dsp, >

----- Original Message ----- From: "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca> To: "tunkeat" <tunkeat@gmail.com> Cc: "speex" <speex-dev@xiph.org> Sent: Wednesday, January 05, 2005 2:48 PM Subject: Re: [Speex-dev] different output for opt/non-opt on win32 platform >No. Like any other CELP codec, Speex has a memory. The only non-PCM

> without a good understanding of the celp and haven't delved into the > codes, I am surprised that there is no such issue with the encoder. > whether the optimsation flags are included or excluded, the encoded > bits are the same. I assumed the decoder shared quite a number of > functions as the encoder except maybe the perceptual enhancement part. > strange. Depending on

Hello, the voice-communication TeamSpeak (www.teamspeak.org) is currently testing a version that supports speex codecs. The quality for high bitrates is quite good. BUT, the low-bandwidth speex codecs that are currently used arent very good. What I did to find this out: I comprared a speex AVB with 6.3 KBit/sec (total, overhead for packets and stuff included) and the 6.3 Kbit/sec Celp Codec

You're asking the wrong question. The question is not "why does it would bad with Speex?", but "why does it sound good with LPC10 and MELP?". And the answer is that both are vocoders. Try dropping frames/subframes with anything else (Vorbis, MP3, G.729, u-law, ...) and it'll sound terrible as well. The only reason it sounds good with vocoders is because the

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Tuesday, June 19, 2007 6:38 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >> Yes, data footprint in the new version is quite manageable. Still I would >> wish better documentation for speex_alloc_scratch(). >

Hi Jean-Marc I am using speex in my voip app (wideband mode). I have noticed that when VAD kicks in, CPU considerably increases (bitrate decreases to 4 kbps). It takes about 7 ms to encode one frame versus 0.5 ms (for speech). This happens regardless preprocessor is used. Although the issue seems to be driver dependent, it occurs on XP, Vista and Mac OS X. Besides complexity and quality, this

> i was wondering whether speex frames could be made "independent", If you tweak the encoder, you can probably do that... except that you'll multiply the bit-rate by about 3. > as in if some packets are lost, there is no need for re-transmission of > these frames (for VoIP app, i see concealment is provided in speex) to decode > future frames . from the draft RFC for

hi, > > how big is this "Speex's memory"? > > No problem, as long as you decode the stream in order. > > > I am thinking perhaps naively: at > > the encoder side, is it possible to get the states for the decoder > > from the encoder's memory without doing the actual decoding? > > In theory, you could, but I don't see what you'd

Hello Jean-Marc and all, I recently had a talk with somebody about CELP. He said, there is this federal standard 1016 (4.8kbps) with a reference implementation of the Department of Defense (only on Sun, unfortunately, if I got this right). This one is noticed in the manual already. He also said, since there is this implementation of the DoD, nobody would voluntarily re-implement CELP. If I read

hi all, the stacksize required for encoder and decoder are 32Kbytes and 16 Kbyes respectively. i changed it to 20Kbytess and 8Kbytes and it seems to work. but need to trim further. can someone point me in the right direction to further reducing the stack size? thanks! cheers, tk

hi Alfred, >I am currently trying to port speex v1.1.6 to a microcontroller with >very limited memory (<64Kbyte RAM). if forced to the wall, you can try below (need to "rewrite" the code a little): unless i am very much mistaken, you can do "dynamic allocation" for some of the memory. these memories are only required when you are running eg speex_encode for the

Hi, I might have written to this mailing list previously about this but I've been experiencing some mailing problems so I write this again. First of all, thanks Jean-Marc Valin for your continued efforts on speex. I must say that I am very impressed with Speex and further more the innovative features recently added in 1.1. They have worked great for me. Question 1) What is the return value

I am transcoding mp3 to wave using ffmpeg I am then piping it to speexenc for speex encoding but the speex file size is 496 bytes after the command ends https://lists.ubuntu.com/archives/ubuntu-users/2010-March/212927.html https://lists.ubuntu.com/archives/ubuntu-users/2010-March/212949.html https://lists.ubuntu.com/archives/ubuntu-users/2010-March/212954.html what am I doing wrong? bellow is

Hello kind developers, I am planning on creating a steganographic extension for speex/CELP. Since speex/CELP is lossy, there should be quite many bits that one can use for hiding data. I'm familiar with the principles of CELP (two filter loops, one for pitch, the other for formants, let the raw speech frame run through those filter loops, take residue signal, map it on a codebook entry,

Am Dienstag, 13. Mai 2003 03:22 schrieb Allen Drennan: > Hello, > > HawkVoice doesn't have a 6.3kbps codec for CELP, it has a 4.5kbps CELP > codec and I do not believe it is being used by TeamSpeak. The 6.4kbps CELP > being used in TeamSpeak, to which you are referring I believe comes from > Lernout & Hauspie's LHACM.ACM file which it appears you are redistributing

Dear Speex developers, I think I found a typo in libspeex/preprocess.c (that still in the SVN version too). Please correct me if I would be wrong. Patch is attached. (Yours :parenthetically &dezzy) -------------- next part -------------- A non-text attachment was scrubbed... Name: noise_var.patch Type: text/x-patch Size: 518 bytes Desc: not available Url :

Well, I grabbed the tarballs this morning and found that of the three new releases, only libogg1.1 would compile without and issue. I had to recompile my flac1.1.0 for ogg support, and it gave me a new error (or I wasnt paying attention, anyway...) it will finish compiling and install, but I only ran make check on the original compile, not the new one with OggFLAC attached and stuff...

Hi, We would like to announce the first release of the Speex project. Speex (http://speex.sourceforge.net) is an open-source (LGPL), patent-free compression format allowing an alternative to expensive proprietary codecs. Unlike Ogg Vorbis which compresses general audio, Speex is designed especially for speech. For that reason, Speex is meant to be a complement to Vorbis. Since it is specialized