similar to: hmm, howabout a typedef instead of void *

My arrangement for a Speex format tag was actually accidental. I was asking what would be involved and instead of an answer, I got a format tag. Since there is only one functional Speex ACM codec available as far as I know, it should use the official format tag. I will be glad to modify our applications to conform to this de-facto standard. Others who may develop ACM codecs in the future

I am glad to announce the BETA release of the Speex ACM codec. It is based on the Speex 1.0.1 codec release. An ACM codec enables Windows to create and play back WAVE files containing Speex content. It might also be useful for use with Netmeeting (after some registry hacking. Not tested yet.). I also provide a portable playback tool (speexdec_wav) that handles both the Ogg and WAVE containers.

> While on the subject of plug-ins, has anyone written a Speex plug-in > for the Goldwave audio editor? There is an ACM codec for I/O of WAVE files encoded in Speex. ( www.openacm.org ) But there is no plugin to load or save Vorbis Speex files natively, as far as I know. Christian <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

Hi, As a potential user of the Speex ACMs and DirectShow filters to come I am also curious about how many ACM codecs for Speex there are under development right now. Also, the WAVEFORMATEX structure must be planned so that it is extensible, with backward-compatibility, without having to ring back Microsoft for further WAVE_FORMAT tags. For instance, it is a good idea to put a flexible sub-format

The Speex ACM codec has been released as version 1.0.1.1. Enjoy! Here is a list of changes: * A setup application has been added to the release. Just click SETUP.EXE and follow the instructions. * The crash under Windows 95/98/ME was fixed. * A reported crash in VirtualDub, CDEx and possibly other applications was fixed * The codec's Format Tag was changed to an official Microsoft

It looks like I'll need to go further into the guts of speex to do this. I do, however, see some lines in nb_celp.c/nb_decode() that look interesting. I guess I'll play with it. I doubt that it will be terribly clean, though. Jean-Marc: Take a look at line 1195 in nb_celp.c (CVS). It reads "speex_warning ("More than to wideband layers found: corrupted

Hi all, I'm new to the group. I'm looking at the speex code with an eye towards maybe helping out with either codec optimization or fixed-point implementation, The SNR calculation in testenc.c and testenc_uwb.c doesn't make sense to me. The code is { float enoise=0, esig=0, snr; for (i=0;i<FRAME_SIZE;i++) {

I tried feeding in the 3 encoded frame in ONE BLOCK, and calling speex_decode() 3 times in a roll. Only the 1st frames came out perfectly. For the other 2, I got "corrupt" frame warning. I was supposed to get 38 bytes consumed each frame (narrow-band, VBR off). I tried speex_bits_remaining() to peek on the # of bits consumed, and got variable (clearly wrong)#s returned. But if I

Actually, the SNR calculation in testenc has been broken for a while. The reason for taking the last frame was that the codec would introduce a one-frame latency. I changed that to half a frame (10 ms) a while ago and never updated testenc. Jean-Marc Le lun 01/09/2003 à 13:12, Mike Dunn a écrit : > Hi all, > > I'm new to the group. I'm looking at the speex code with an

> You said, it's unstable, yes, I got compiling errors with MsVC6 and MsVC.net > And I modified it a bit to get it compiled. Should I post the errors > here? YES, kindly post the errors that you encountered. - Abhishek <p><p><p>---------- Original Message ----------- From: "Kenji Chan" <adslbqmr@tpg.com.au> To: <speex-dev@xiph.org> Sent:

The main difference is not that much in the bit-stream but in the API. In earlier versions you had to append the terminator manually, whereas I modifed later versions to do it automatically in case programmers forgot (there was no reason not to do so). Jean-Marc On 2010-04-11 05:23, Tobias wrote: > On Saturday 10 April 2010 21.51.55 Jean-Marc Valin wrote: >> All version after 1.0

David, Here's the trick ... do this just before your speex_bits_write(): speex_bits_insert_terminator(&bits); Then, when decoding, keep calling speex_decode() until it returns -1 or speex_bits_remaining(&bits) returns 0. Works for me, anyway. Tom David Barrett (dbarrett@quinthar.com) wrote: > > Hi, I'm using Speex and I want to pack multiple frames into a single >

On Saturday 10 April 2010 21.51.55 Jean-Marc Valin wrote: > All version after 1.0 are compatible with each other and with 1.0. Hi Jean-Marc and thanks for the quick reply. I have now looked at this further and got the idea to hard code the number of frames in the decoder temporarily as a test and voil?, it works! The problem seem to be some incompatibility in the termination handling. After

Hi list, I'm trying to figure out how to do the most compatible implementation that will work with as many versions of Speex as possible. I am streaming multi frame Speex blocks over a TCP connection which works fine as long as the version of Speex is the same on both sides. When using a newer Speex (1.1.?) to encode and an older version to decode (1.0.5), it does not work. The encoder

Hi, I'm using Speex and I want to pack multiple frames into a single packet. The manual (section 4.5) says to call "speex_encode()" multiple times before calling "speex_bits_write()", and then call "speex_decode()" until it returns -1. However, when I try that "speex_decode()" never returns -1, and it enters an infinite loop. I'm using 1.0.4. Any

Figures. I knew I should've just pasted my code: .. while (ret != -1 && speex_bits_remaining(&bits) > 0); I am using a newer version of Speex, so I guess the terminator is a relatively new thing. I'm not even sure if it's necessary, but I think Jean-Marc recommended using it back when I asked this question awhile ago..? Anyway, glad it's working for you. Tom

All version after 1.0 are compatible with each other and with 1.0. Jean-Marc On 2010-04-10 15:44, Tobias wrote: > Hi list, > > I'm trying to figure out how to do the most compatible implementation that will > work with as many versions of Speex as possible. I am streaming multi frame > Speex blocks over a TCP connection which works fine as long as the version of > Speex is

On 15 April 2010 17:55, Daniele Barzotti <daniele.barzotti at eurocomtel.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Il 15/04/2010 01:30, Conrad Parker wrote: >> >>> But how can I know the size of each speex frame into a multiframe payload? >> >> use speex_bit_read_from() just once on the packet, then call >> speex_decode()

I've just started testing Speex, and it seems very good so far. In testing the Speex decoder and simulating packet loss, I noticed that simply not calling speex_decode(st, NULL, output) when a packet is dropped doesn't appear to degrade the quality of the audio later on. The reason for this test is that in a real-time situation, you may not know right away when a packet is dropped

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 15/04/2010 01:30, Conrad Parker wrote: > >> But how can I know the size of each speex frame into a multiframe payload? > > use speex_bit_read_from() just once on the packet, then call > speex_decode() once for each frame. > > Conrad. Thanks for the reply, Conrad. What is not clear for me (and I didn't found it on the