similar to: RTP profile draft!

On Wed, 6 Dec 2006, lianghu xu wrote: > Hi Jean-Marc, > > I remember you said that the SDP tells the mode information. Right. But a decoder like speex can always be configured from information contained in the incoming stream. That makes your application more interroperable. Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 -

In a "normal" frame that doesn't have in-band signalling (which nobody seems to use anyway), the frame starts with the narrowband information. If the frame is in wideband, then this will be followed by a bit of wideband information that starts with a bit set to 1 (narrowband starts with a bit set to 0). Have a look at what the Speex decoder does. You may actually want to have similar

Hello, In the internet draft describing the SDP parameters for speex I find this: mode: Speex encoding mode. Can be {1,2,3,4,5,6,any} defaults to 3 in narrowband, 6 in wide and ultra-wide. In the documentation I can only find the following request: SPEEX_SET_MODE There is no description though what this request does. I think the mode somehow maps to the bitrate, but I

Hi Jean-Marc, Alfred and Greg, Are you receiving the mails from IETF about draft-ietf-avt-rtp-speex The mails are not coming from AVT mailing list, but I think we are all 3 part of a minimal list (draft-ietf-avt-rtp-speex at tools.ietf.org) dedicated to latest discussion about the draft. I have answered some questions, but there are small changes and adaptation still required to the ietf

>> Consider a device that only has enough ROM to store one set of >> quantization tables (the limitation could also be about speed, network, >> ...). If you specify MUST be able to decode, then it means that this >> device simply *cannot* implement the spec *at all*. This is bad for >> interoperability. > > For me: device which don't have all mode

Dear Sir/Miss: I'm very sorry to bother you,but I've found a bug in the Speex,Version 1.2beta1,and also I've have some questions. I'm deeply impressed by the work you have done in the coding and decoding of speech signal.But when using speex,I encoutered a bug,that is when in 32K mode,the window size is still 200 samples,but not 400 samples,the bug will bring the problem of

On Tue, 14 Oct 2008, Jean-Marc Valin wrote: > Diana Cionoiu a ?crit : >> Hi Jean-Marc, >> >> 1. Why CELT versus Speex? > > There's nearly no overlap between Speex and CELT. CELT is much higher > quality, very low latency, and of course, higher bit-rate than Speex. So > it really depends on the application. > >> 2. What's the RTP payload for CELT,

On Sat, Nov 1, 2008 at 2:40 PM, Aymeric Moizard <jack at atosc.org> wrote: > The vcproj file provided for 2005 in 1.2rc1 does not include > _USE_SSE when compiling the project for "Release_SSE". This > define is only used when compiling under "Release_Dynamic_SSE". > > Is this just because the vcproj file is wrong or is it because > this #define must not

If you want to test the AEC, I recommend using the svn version of Speex. Jean-Marc Aymeric Moizard a ?crit : > > I finally solved my problem: > > My **static** speex library is compiled with: > -D_LIB > > While I should compile it with: > -D_USRDLL > > I'm not able to understand completely why: anyway, it > now can be compiled without breaking anything.

On Mon, 6 Nov 2006, Jean-Marc Valin wrote: > That's quite a strange problem. Considering that Speex doesn't have any > "init code" (stuff that executes when it's loaded), there's no way this > could be a bug in Speex. True. > I see two likely possibilities (plus lots of > unlikely): > 1) A bug in your code. Linking with Speex pushes your code to a

> Page 3: > > To be compliant with this specification, implementations MUST support > 8 kHz sampling rate (narrowband)" and SHOULD support 8 kbps bitrate. > The sampling rate MUST be 8, 16 or 32 kHz. > > There is a type above after (narrowband), there is a " extra character. > > I don't understand what is the motivation to specify "SHOULD

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, I am looking how to setup speex codec in codecs.conf for 8 Kbps and 6 Kbps. In config file are many parameters for setting. I don't know what is need to change for narrowbad like 8 Kbps and 6 kbps. Any suggestion? [speex] ;0-10 quality => 4 ;0-10 complexity => 4 ; true / false enhancement => true ; true / false vad => false ; true / false vbr => false ; 0 = off, otherwise,

Hi I have just written a small c programm which reads in speex files and outputs them as asci text numbers. This is necessary as for writing a hw testbench for decoding tests, since thy only read ascii files :-(.I can't read the bitrate properly from the header file. It's allways -1. Please see example below and attached c programm. I wan't to check for a fixed bitrate (8000).

I'm getting confused, what's the problem exactly? The AGC doesn't remove the DC or it adds one? Jean-Marc Aymeric Moizard a ?crit : > Hi Jean-Marc & all, > > I'm currently working on a wav file with very low volume. > This wav also contains a DC component. > > Using testdenoise with modification (AGC turned on with > 20000.0 value) I'm able to

On Thu, 16 Oct 2008, Jean-Marc Valin wrote: > Aymeric Moizard a ?crit : >>> None of that is defined yet, though I'm open to suggestions on how to do >>> the mapping. >> >> CELT/44100 and CELT/48000 >> a=fmtp:105 stereo=on >> >> probably a latency value? > > It would definitely need a frame_size value > >> "CELT"

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

On Fri, 27 Feb 2009, Jean-Marc Valin wrote: > Hi Aymeric, > > Yes, I'm receiving the emails but haven't had enough time to look into > the details yet. I've seen you responded to many comments, so what are > the ones for which we still need to respond? Summary is there: https://datatracker.ietf.org/idtracker/ballot/2837/ As I understand: we need to change

Here my comments: Page 3: To be compliant with this specification, implementations MUST support 8 kHz sampling rate (narrowband)" and SHOULD support 8 kbps bitrate. The sampling rate MUST be 8, 16 or 32 kHz. There is a type above after (narrowband), there is a " extra character. I don't understand what is the motivation to specify "SHOULD support 8 kbps

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