similar to: Re: SDP usage

All: Attached please find yet another RTP profile revision (v5). You can also find the document at: http://www.herlein.com/downloads/speex/docs/ Changes: - added vbr, cng, ebw, sr optional parameters to MIME - added vbr, cng, ebw a=fmtp options for SDP use - added required document attributes for submission to IETF and IANA (format and author contact information). Note that we

The latest revision of the draft profile for use of Speex in RTP is attached. We plan on submitting this - or a modified version of this, based on immediate feedback - to the IETF on Monday for consideration at the next meeting. Major differences in this revision are: - removed the discussion in the MIME section. It's a duplicate of the SDP discussion anyway, and may or may not match the

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

> Otherwise Greg, can you send the latest version of the RTP draft so I > can put it on the site (the current one is getting old)? Attached for all to see. Greg -------------- next part -------------- Internet Engineering Task Force Greg Herlein Internet Draft Jean-Marc Valin draft-herlein-speex-rtp-profile-06

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

Hi, I'm trying to cover all Speex configuration options to set quality/mode/bitrate in my application and I was wondering if the following all makes sense: - abr_bitrate - use average bitrate and set it using bitrate parameter - SPEEX_SET_ABR - cbr_bitrate - use constant bitrate and set it using bitrate parameter - SPEEX_SET_BITRATE - cbr_mode - use constant bitrate and

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

Hi Maitland, I think your solution is probably the best implementation you could do for SPEEX_GET_QUALITY. However, unless you have something against that, I think removing it would be better, as in many cases (e.g. VBR), the call just doesn't make sense). This would of course break the API (not the ABI), but given the fact that it was never implemented, any app that uses it is already broken

The latest revision of the draft RTP Profile is attached for review. This will be submitted to the IETF Audio-Video Transport Working Group for consideration immediately, so if you have any more comments, let us know. In addition, we will be applying for an official MIME type. Note that the AVP code and the MIME type in this latest revision have been changed from "SPX" to

Looks good. Two things though: - I think the draft should be names -02 since the last one was -01 (I'm pretty sure). - The header in the current document should be changed (they say -01) Jean-Marc Le lun 01/03/2004 à 20:17, Greg Herlein a écrit : > > > > Is this the latest draft? > > > >

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

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)

Thanks! Btw, have you tried using SBR-technology or similar with speech codecs? That might be a good idea I thought.. But I don't know if it produces as good quality with speech codecs as it does for music codecs. Do you know if there is any open source variant of SBR? /Pontus -----Ursprungligt meddelande----- Från: owner-speex-dev@xiph.org [mailto:owner-speex-dev@xiph.org]För Jean-Marc

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, jean-marc: i think we can remove spx_sig_t *orig. but am not sure about exc2Buf. is it for extension? rgds, tk On Mon, 28 Feb 2005 12:42:38 -0500, Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> wrote: > Hi, > > I looked at the code I think there are still places where you can reduce > memory. For example, I think bufSize can be reduced to around 400 > (instead of

Why not use gcc? You can get either mingw or cygwin. Otherwise I don't know. Speex should compile with a C++ compiler with only minor tweaks (forcing the compiler to accept the C casts). Jean-Marc Le lundi 18 juillet 2005 ? 17:55 +0000, Wolfgang Frotten a ?crit : > I am a delphi coder and i have successfully compiled version 1.0.5 to use the > resulting dll in John Villars

> I'm about finished developing a QuickTime component that supports Speex > (on > MacOS X and Windows).. As it is now the user can set complexity > (SPEEX_SET_COMPLEXITY) and quality (SPEEX_SET_QUALITY / > SPEEX_SET_VBR_QUALITY) and to wether to use VBR or not. Will these > options > make it possible to produce all combinations of bitrates/qualities? Or > should I

Le jeudi 03 mars 2005 ? 20:29 +0100, Kleijn, J.S. de a ?crit : > I use the Intel compiler 7.0 , and it doesn't like it Does it have an option to enable C99? Otherwise, if you're aware of another mechanism that allows it to allocate temporary stuff on the stack, I might be able to support it. Jean-Marc > -----Oorspronkelijk bericht----- > Van: Jean-Marc Valin