similar to: draft-herlein-speex-rtp-profile-01

Ok, I figured it out. :) This seems to work: 1) Call speex_bits_read_from() once, specifying the location in memory of the compressed data, and the total length of that data. 2) Keep calling speex_decode() until speex_bits_remaining() returns 0. Then you don't have to keep track of the # of frames per packet, or the size of each compressed frame. It's done magically by the codec.

Hi, I have a question about section 3.4 of the RTP payload draft: > Speex codecs [11] are able to detect the the bitrate from the > payload and are responsible for detecting the 20 msec boundaries > between each frame. This suggests that you can encode some frames with Speex, pass the compressed bits to the decoder, and you'll get the output - without having to do external

All: The latest draft RTP Payload Format for Speex is available via the IETF. See below for details. Greg ---------- Forwarded message ---------- Date: Tue, 09 Mar 2004 15:56:23 -0500 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-herlein-avt-rtp-speex-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. <p>

Hi all, Please find below the -01 update to draft-herlein-speex-rtp-profile, as submitted to the IETF. Regards Phil <p>-------------------8<-----------------------------------8<--------------------- <p><p>Internet Engineering Task Force Greg Herlein Internet Draft Jean-Marc Valin

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

I have (finally) posted my Speex wrapper classes. They are at: http://www.grandgent.com/spx/tgAudioCodec.zip I followed your recommendations and they worked fine with 1.1.0. However, I'm still having the same problem with 1.1.7 that I had the last time I tried to upgrade. I'm using the same code with both versions, except for calling speex_encode_int instead of speex_encode, and

Hello, What's the purpose of the 'sr' sdp parameter ? The sample rate is already given in the a=rtpmap line ? Simon Le dim 29/06/2003 à 12:12, philkerr@elec.gla.ac.uk a écrit : > Hi all, > > Please find below an updated Speex Internet Draft document. > > It would be good if we could book some time for discussion on Speex at the IETF > meeting in Vienna (scheduled

Alfred E. Heggestad wrote: > <...> > > If we don't get any comments in 1 week (by 22. May 2007) we will go ahead > and submit it to the IETF. Of course you can comment on it also after it > has been submitted, but we would like to get the input from the Speex > community first.. > thanks for all the input. please find attached an updated version of the draft. I

Hi Please find an updated version of the Speex I-D attached. The only change is addition of the copyright conditions in Appendix A, as requested by Ivo. Many thanks for your input. I will give you a few more days before submitting to AVT working group /alfred Ivo Emanuel Gon?alves wrote: > Do not forget to add the "Copying conditions" to the RFC. > > Check

Looks good to me. Jean-Marc Alfred E. Heggestad a ?crit : > Hi > > Please find an updated version of the Speex I-D attached. The only > change is addition of the copyright conditions in Appendix A, > as requested by Ivo. > > Many thanks for your input. > > I will give you a few more days before submitting to AVT working group > > > /alfred > > Ivo

Hi, We'd like to announce the first draft for the Speex RTP profile. It was written essentially by Greg Herlein, with some help from Simon Morlat and I. We'd like to get some feedback on it before it is sent to the IETF. Basically this will allow all SIP based VoIP applications using Speex to inter-operate. For those interested, there's already Simon's LinPhone (www.linphone.org)

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

Hi all We are about to send an updated version of the internet draft "RTP Payload Format for the Speex Codec" to the IETF AVT working group. Before submitting we would like your input, if you have any comments or input please send them to the mailing list. If we don't get any comments in 1 week (by 22. May 2007) we will go ahead and submit it to the IETF. Of course you can comment

Hi all, Please find below an updated Speex Internet Draft document. It would be good if we could book some time for discussion on Speex at the IETF meeting in Vienna (scheduled for 14th July). The cutoff for submission is 9:00am EDT, (GMT -04:00), 30th June. Comments and feedback welcomed! Regards Phil

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

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

> 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:

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, 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