similar to: Size in samples of a Speex packet

Hi Steve, Steve Kann wrote: > Chris Flerackers wrote: >> Hi, >> >> Is there an easy way to get the size in samples of a Speex packet, >> without decoding the packet? >> >> If I receive a "narrowband packet" with >> - Zero or more wideband frames (must be skipped apparently) >> - Zero or more Speex inband requests >> - Zero or

Hi, On http://www.speex.org/docs/manual/speex-manual/node11.html#SECTION001140000000000000000 the bitrate for Speex Wideband mode 9 and 10 is 9 34,400 10 42,400 On http://tools.ietf.org/html/draft-ietf-avt-rtp-speex-03 the bitrate for Speex Wideband mode 9 and 10 is 9 34.2 kbit/s 10 42.2 kbit/s I believe the draft contains the right values: E.g. mode 10 Narrowband mode 7 -> 492

Hi, No, it only happens with speex_wb_mode. But like I said, it is because in wideband mode, the function sb_encoder_init is called and this function initializes the sampling rate using speex_*de*coder_ctl instead of speex_*en*coder_ctl In narrowband mode, the sampling rate is just initialized to 8000 st->sampling_rate=8000; BTW, I saw that my email was added to an existing thread instead of

Hi, I'm using speex 1.1.4 and when I query SPEEX_GET_SAMPLING_RATE as in speex_encoder_ctl ( m_pEncoderState, SPEEX_GET_SAMPLING_RATE, &m_SampleRate ); I get 2 The encoder is initialized with m_pEncoderState = speex_encoder_init ( &speex_wb_mode ); On the decoder side, the correct sampling rate is returned: m_pDecoderState = speex_decoder_init ( &speex_wb_mode );

Dear Speex developers, I am currently experimenting with Speex on Symbian smartphones. I have compiled the Speex library, and I am now using it in the following way: 1. Record 320-byte buffers of data in PCM16 format, 8000 Hz sampling rate. 2. Feed the resulting buffer to an instance of a narrowband Speex encoder. 3. Send the encoded data over RTP. 4. Upon receiving on the other side, feed the

Hi, Sorry if this a repost but I want to create the smallest Speex library possible to be put in TI's TMS320 DSP. I'm only interested in one configuration: 5.97 Kbps narrowband. What part of source code can I remove? Currently, when I compiled the version 1.1.12 libspeex.a library with the TI TMS320 and Fixed-Integer options, I get around 522Kb. I would like to reduce it to as small

Because a wideband signal has both a narrowband part and a wideband part the first part of the wideband decode is to call the narrowband decode. In the fixed point version the signal generated from the narrowband decode is downshifted at the end. In this same version the wideband then upshifts the signal by the same amount. I would like to do away with the downshift on the narrowband side

Hi everyone, I just changed the meaning of the timestamp in the jitter buffer. If you don't know what I'm talking about, then you're not affected. If you do use the jitter buffer, than you will need to change your code accordingly, so instead of bumping the timestamp by 20 (ms) for each frame, you'll have to increase by 160 (samples) for narrowband or 320 for wideband. The new

Hi, I was wondering if anyone has experimented with Speex's wideband (16kHz) mode at lower quality settings. In particular I have been using quality 3, and with wideband input files the resultant frequency spectrum is limited to about an upper end around 3.5kHz (almost telephony quality bandwidth). Has anyone tried increasing the spectral bandwidth at the expense of lowering the

Hi, I found this message concerning VAD and was wondering whether VAD has been ported to fixed-point in the latest version? Thanks, SingHui ---------- Forwarded message ---------- From: Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> Date: Jul 22, 2005 1:02 AM Subject: Re: [Speex-dev] Fixed-point To: gue baja <gue_baja@yahoo.com> Cc: speex-dev@xiph.org Hi Baja, Here's a quick

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

Le mar 18/11/2003 à 17:39, Allen Drennan a écrit : > Speaking of video conferencing in conjunction with Speex, we are > currently beta testing a solution we developed that offers multi-point, > multi-party video and audio using the Speex engine for voice. > > http://www.wiredred.com/downloads/ecsetup.exe > > The fair and good audio settings are Speex narrowband, high quality

--- Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > Sorry if this a repost but I want to create the > > smallest Speex library possible to be put in TI's > > TMS320 DSP. I'm only interested in one > configuration: > > 5.97 Kbps narrowband. What part of source code > can I > > remove? Currently, when I compiled the version >

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

> Another issue is the memory allocations distributed so many places that > it's hard to provide a single memory initial function interface. > > In a VoIP case on ARM, the total memory size for speex codec should be > known at the inital stage since all the memories are allocated > at the initial stage. If you want everything in the same big block, all you need to do is

Peter Saint-Andre a ?crit : > Ivo Emanuel Gon?alves wrote: >> Just a heads-up, I received confirmation that Speex is now the default >> codec for the Jabber's Jingle VoIP protocol. > > Which we hope to finalize soon for broader adoption. :) That's good to hear. Are you supporting wideband or just narrowband? Jean-Marc

Hi Jean-Marc and list, I'm trying to negotiate speex with SIP/SDP and get some trouble understanding the "mode" parameter: mode: Speex encoding mode. Can be {1,2,3,4,5,6,any} defaults to 3 in narrowband, 6 in wide and ultra-wide. Is mode equivalent to the "quality" parameter of speex? In this case, I don't understand why mode is not from 1 to 10... Just

-----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Thorvald Natvig Sent: Monday, March 20, 2006 12:11 PM To: speex-dev@xiph.org Subject: Re: [Speex-dev] Who is using the jitter buffer? But I must say that it really does work well at the moment, at least from the "minimizing latency" point of view :) How do you timestamp the

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

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 -