search for: speex_bit

...es bytes 8bit - 8Khz PCM from the modem num_samples is, commonly, 16000 */ int ret,c,d; short int PCM_F[160]; for(c=0;c<num_samples;c++) { /* tempbuf 0<-127->256 */ /* pcmbuff -32786 <- 0 -> +32786 */ PCM_F[d] = (PCM[c] << 8)^0x8000; d++; if(d > 160) { speex_bits_reset(&IDA->speex_bits); speex_encode_int(IDA->speex_state,PCM_F,&IDA->speex_bits); speex_bits_insert_terminator(&IDA->speex_bits); d = speex_bits_write(&IDA->speex_bits, buffer, 200); *buffer += d; ret += d; d = 0; } } return r...

Jean-Marc, The following patch makes the above two read functions const correct. Cheers, Erik diff --git a/include/speex/speex_bits.h b/include/speex/speex_bits.h index a26fb4c..234ec53 100644 --- a/include/speex/speex_bits.h +++ b/include/speex/speex_bits.h @@ -77,7 +77,7 @@ void speex_bits_reset(SpeexBits *bits); void speex_bits_rewind(SpeexBits *bits); /** Initializes the bit-stream from the data in an area of memory */...

...g encoder example in the manual.pdf of speex documentation. Here's my portion of code: int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { int ret,c,d=0,nbBytes,ttBytes=0; float PCM_F[160]; char cBits[200]; #ifndef DISABLESPEEX speex_bits_reset(&IDA->speex_bits); for(c=0;c<num_samples;c++) { PCM_F[d] = (float)((int)PCM[c] << 8) - 32640; if(d >= 159) { speex_encode(IDA->speex_state,PCM_F,&IDA->speex_bits); nbBytes = speex_bits_write(&IDA->speex_bits, cBits, 200); memcpy(buffe...

...g encoder example in the manual.pdf of speex documentation. Here's my portion of code: int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { int ret,c,d=0,nbBytes,ttBytes=0; float PCM_F[160]; char cBits[200]; #ifndef DISABLESPEEX speex_bits_reset(&IDA->speex_bits); for(c=0;c<num_samples;c++) { PCM_F[d] = (float)((int)PCM[c] << 8) - 32640; if(d >= 159) { speex_encode(IDA->speex_state,PCM_F,&IDA->speex_bits); nbBytes = speex_bits_write(&IDA->speex_bits, cBits, 200); memcpy(buffe...

...to speex_en/decode() is cumbersome. All these tasks could be done by the API automatically, once it knows that it is dealing with a Stereo source. A unified API not requiring separate code paths would be helpful. <p>*** Filling the "bit bucket". An additional function similar to speex_bits_read_from() would come in handy. This should append the bytes passed into it to the bytes already in the buffer instead of replacing the buffer contents. The intended use would be for streaming sources that bring in data in small portions (smaller than an encoded frame). This way the speex_bits c...

An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: tmezo.vcf Type: text/x-vcard Size: 345 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.vcf

hi, this patch should fix the symbian build. /alfred -------------- next part -------------- A non-text attachment was scrubbed... Name: speex-symbian2.patch Type: text/x-patch Size: 2669 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20061115/5ac4915e/speex-symbian2.bin

...======================= >> --- symbian/bld.inf (revision 12114) >> +++ symbian/bld.inf (working copy) >> @@ -30,6 +30,20 @@ >> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. >> */ >> >> +PRJ_EXPORTS >> + >> +..\include\speex\speex_bits.h \epoc32\include\speex\speex_bits.h >> +..\include\speex\speex_callbacks.h \epoc32\include\speex\speex_callbacks.h >> +..\include\speex\speex_config_types.h \epoc32\include\speex\speex_config_types.h >> +..\include\speex\speex_echo.h \epoc32\include\speex\...

...y, > once it knows that it is dealing with a Stereo source. I'll need to think about that one. Stereo support is really some "extra" information that the decoder can decide to use or ignore. > *** Filling the "bit bucket". > > An additional function similar to speex_bits_read_from() > would come in handy. This should append the bytes passed > into it to the bytes already in the buffer instead of > replacing the buffer contents. > > The intended use would be for streaming sources that bring > in data in small portions (smaller than an encoded fra...

Hi jere, thanks for this link, i'll see if i can do something good with that. speex.dll : ----------- I have a speex.dll which work, and i can encode and decode a wav file. (i used male.wav on speex.org for my test). But my dll is specific to my softphone. In fact i just include speex.h and i call speex functions for [en;de]coding. My code is based on speex website's sample :

Hi Marian, I took a brief look at RFC 5574 and as far as I understand, you can simply do it like this: SpeexBits b; speex_encode(state, some320bytePCM1, &b); speex_encode(state, some320bytePCM2, &b); After that, get the encoded data with speex_bits_write and put it in your packet. Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Marian Kechlibar Subject: Re: [Speex-dev] SpeexBits ... Hello, is here anyone who could help me with that? Best regards Marian Kechlibar Ma...

...) or speex_lib_ctl() request? I have > no idea about the best way here, and would appreciate your > advices. I don't think it should be a _ctl() call because there's too much potential for confusion. I would just keep it as a separate API call like you have. I'd tend to put it in speex_bits.h, so I guess it should be called speex_bits_get_number_of_frames() or something like that. >>> Sure. But in SDP you specify mode and not bitrate. ;) So I want >>> to operate with the same things as in SDP. >> I see. BTW, you can ask the full bit-rate to the encoder or dec...

...ith speex. I have built and installed speex on the computer and can compile and link with no problems. I have the sample programs (sampleenc.c and sampledec.c) which I am following. The only difference is my raw data is in a char array and not written to a file. Everytime I call speex_encode and speex_bits_write I get a return value of 38. I found the max byte size bit stream of 2000 in the speex_bits.h but no matter if I pass it 200 or 2000 I always get 38 bytes back. Any clues ?? Jerry R Craft Titan Systems 7436 Mission Valley Road San Diego, Ca. 92108 wk 619.278.2012 cel 760.855.3329

...=========================================================== > --- symbian/bld.inf (revision 12114) > +++ symbian/bld.inf (working copy) > @@ -30,6 +30,20 @@ > SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > */ > > +PRJ_EXPORTS > + > +..\include\speex\speex_bits.h \epoc32\include\speex\speex_bits.h > +..\include\speex\speex_callbacks.h \epoc32\include\speex\speex_callbacks.h > +..\include\speex\speex_config_types.h \epoc32\include\speex\speex_config_types.h > +..\include\speex\speex_echo.h \epoc32\include\speex\speex_echo.h...

I saw a thread in the list archives about a speex port to TI 55x DSP. Wondering how that worked out (is working out)? Also wondering if there is a source archive for it, or if the patch in the email archives is still current, or if there's been updates. Any info appreciated. Thanks Paul

This portion of the RFC is gramatically incorrect and confusing: The RTP payload MUST be padded to provide an integer number of octets as the payload length. These padding bits MUST be all zero. This padding is only required for the last frame in the packet, and only to ensure the packet contents ends on an octet boundary. <p> -- Ben Greear <greearb@candelatech.com>

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

...1.1.6-jeh2.patch The issue with codebooks that Jean-Marc mentioned is that the TI 55xx C compiler uses two bytes per char, so codebooks take more memory than they need to. The whole compress/decompress fit in SRAM, though, so it probably runs faster this way and consumes less power. I did update speex_bits to use all the bits in 2 byte chars. If I remember correctly, that patch also enables Speex fixed-point on Analog Devices Blackfin DSP. Hope this is helpful. Let me know if you find any issues with the patch. I've been working on things lower in the food chain lately so I have not had a ch...

.... The broken behavior happens in this simple scenario: 1) I check out latest git version to ./src/speex 2) My system has an older "release" version installed to regular install location. 3) I want to use the version I just checked out, I include filed this way: "...whatever/src/speex/speex_bits.h" Broken behavior: instead of using files from check out version, speex includes will include system installed versions of old speex! That's just bad, I've never seen anything like that I'll attempt to answer the "why" question... speex also has Symbian port, and just...

Hello I've looked into SPEEX SDK and source codes provided on site www.speex.org , and I'm trying to include in my Visual Studio 2005 - Visual C++ SmartDevice WM 5.0 the facilities provided by SPEEX (both encoding/decoding).I've downloaded the header files (i.e. Speex.h Speex_bits.h etc) and also the libspeex.lib.After creating my encoding/decoding functions following the examples sampleenc.c and sampledec.c and including the *.h files and the libspeex.lib in my project , i've got some linker problems concerning the functions imported from that lib , and after some days...