similar to: RE: Speex-dev Digest, Vol 27, Issue 18

Can we get a response from Verisilicon on this? We spoke at the VoIP developer conference and you seemed to indicate that Speex was too difficult for you guys to implement in your embedded products. Mr. Valin would like to know specifically what your criteria is to run on your silicon. He needs to know the following. What is the maximum code size that you can use? What is the maximum data

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

Is there any place where I can see a summary of what is being done and what is still pending with the fixed point version of the libraries? I have some experience with vocoders and fairly good experience with de-jitters and suchs. I may be able to help. Thanks Baja

Hi, Speex is getting close to beta4, which I'd like to be feature-complete (or as close as possible). That's why I'd like to ask if anyone here has needs for a feature that hasn't been implemented yet. If so, please let me know. For those interested, here's what's going to be in beta4. First, the VBR code has been greatly improved and now works good with wideband too.

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

Hi Jean-Marc and All, Two things need your confirmation/suggestion. 1) First, I think there is a bug in libspeex/lsp.c line 512. /* hard limit ak's to +/- 32767 */ if (a < -32767) a =32767; // This line should be changed to if (a < -32767) a = -32767; if (a > 32767) a = 32767; ak[j-1] = (short)a; 2) About the RTP wrapper for VoIP I'd like to use the

for the bits init I am using speex_bits_set_bit_buffer and I don't use the write to or read from because the data is already in the buffer I am reading from and I am writing to the final buffer so I don't need to move arrays around. what part is the vocoder part of the decode? Thanks for your help! -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/06/07

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

Hi, I am using speex 1.2beta2 on a narrowband 16-bit, 8khz system that has a severe program space problem and will not fit speex in its normal operation. In an attempt to shrink speex I placed a breakpoint in every function and ran a decode and encode and removed the breakpoints that I hit. in the functions that had a breakpoint that I didn't hit I commented out those functions (as well as

if the new draft in the manual is used. I don't find how to tell the decoder which mode(NB/WB/UWB) is used in the encoder. The RTP header don't contain the mode field and I don't find the mode information in the coded frame either. Does this mean we have to use NB decoder in all cases? Lianghu On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > >

In a word, I don't what's the standard of speex payload format. The file doc/rtp.txt is for what? Is it not for rtp payload? I find that rtp.txt is more detail that draft02.txt Which rtp docment should be followed? Anyone else has written the RTP wrapper already? Lianghu On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > > 1) First, I think there is

Hello everyone. I would like to know which are the available bitrate using the ultra-wideband compression. Thank you! Paolo Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A. ================================================ CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you

Hello I just wrote a little application using speex. I am compressing and packing singel frames to transmit them. Now I read in the manual, that it's possible to achieve higher bit rates by packing more than one frames at once. Unfortunately there is no table included at the manual, that shows the "real" bitrates of ultra wide band mode. So my question is: Can someone provide that

Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) compression in the same bitstream What is the meaning of this? can i find more information about this somewhere? And what is packel loss concealment, an you enable this somewhere? thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL:

Kirk, Speex was designed for 8kHz, 16kHz, and 32kHz sample rates. If you don't use one of these sample rates, you'll be messing up important assumptions deep within the codec. Why these sample rates? It's telecommunications tradition, rather than PC audio tradition. If you want an efficient and high quality format for voice chat, try 16kHz with VBR quality 6. You should see

> 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

Hi, I found this list of Speex bitrates in the mail archive. http://www.xiph.org/archives/speex-dev/200306/0004.html Can somebody confirm that this list is correct? I am wondering about the following: - On the Speex website it says: "Speex is based on CELP and is designed to compress voice at bitrates ranging from 2 to 44 kbps." while the bitrates listed here are e.g. 84400 for

Hi all, I have recently added Speex support to my app (http://sbooth.org/Max/) and am in the process of creating a GUI for the user to control the codec parameters. I am new to Speex and as such I am not really sure which parameters are more important than others, and deserve prominent placement, etc. Is there a recommended GUI for people to follow or use as an example? Stephen

Hello to all speex developers, I have question regarding payload length of narrowband speex in RTP. I were watching tcpdump of the xlite softphone and have found that it uses weird payload length namely 75 Bytes I went through various source and without success. To be clear: For 8000Hz sample in 20 ms that is 160 samples per frame. This makes 50 frames per sec. modes bit-rate 8 kbit/s