similar to: 1.2beta1 speex_bits_pack realloc issue?

another optimization you can do for packing bits together... the original one is : ------------------------------------------------------------------------------------------------------------- void speex_bits_pack(SpeexBits *bits, int data, int nbBits) { int i; unsigned int d=data; if (bits->bytePtr+((nbBits+bits->bitPtr)>>3) >= bits->buf_size) { //remain

Hi, Sorry! Marc Gimpel. I wrote it in a false thread before. It was my first time. :-) I have to write a small programm which should be able to record speeches and in addition synchronize the recorded speeches with measuring data. My idea is to record the speech in the normal way with speex and without ogg. If a sync message was received, i write a custom in-band messages using mode 13

Hi, Jean-Marc Valin wrote: > Not sure I understand your question. Change the order of what within what? In cb_search, we iterate nb_subvect times over a codebook, finding nb_subvect codebook entries to quantize the excitation signal. After finding these nb_subvect codebook entries, they're written into the stream: /*save indices*/ for (i=0;i<nb_subvect;i++) {

This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def

Hi, i have some code that gives me a "warning: Buffer too small to pack bits" mesage. looking at the libspeex source/bits.c i see the warning in a a function named speex_bits_pack. i'm not using this function. can someone tell me where this may be coming from since i've had a similiar problem before and had that fixed. i can't seem to pinpoint this one. thanks Greg

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

i don't think so. this is my current code: for(i=0; i<samples;i++){ /*only get max 320 bytes at a time so bits can handle*/ Client->raw_audio[i] = *input++; Client->temp_audio[i] = Client->raw_audio[i]; Client->session_File[ndx] = Client->temp_audio[i]; ndx+=1; } speex_bits_reset(&ebits);

> -----Message d'origine----- > De : Jean-Marc Valin [mailto:jean-marc.valin at usherbrooke.ca] > Envoy? : dimanche, 14. juin 2009 20:46 > ? : Stephane Lesage > Cc : speex-dev at xiph.org > Objet : Re: [Speex-dev] Resampler saturation > > Just to make sure I understand, the two patches you sent are > two different ways to fix the problem, with the only >

Hi everyone Firstly, apologies for the cross post, I am not sure which list is most appropriate for this question. I should also point out, that I did not install OCFS2 and I am not the person that normally looks after these kind of things, so please can you bear that in mind when you make any suggestions (I will need a lot of detail!) The problem: accessing certain directories within the

Hi everyone Firstly, apologies for the cross post, I am not sure which list is most appropriate for this question. I should also point out, that I did not install OCFS2 and I am not the person that normally looks after these kind of things, so please can you bear that in mind when you make any suggestions (I will need a lot of detail!) The problem: accessing certain directories within the

Can I somehow configure Linux so that it automatically detects win32 binaries and executes them using Wine? Thanks, David

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Jean-Marc wrote: >I think what happened is that you did not write the "message" length. >With user-callbacks, you also need to say how large the message. The >size is in bytes and encoded in 4 bits. I wonder what is correct. Inside speex the documentation was written that the size in byte is encoded within 5 bit. I changed the code in both ways, but it doesn't work

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

When encoding many frames, I get a write access exception. It appears the "bits" structure has a fixed-size buffer (allocated in speex_bits_init()), and speex-encode() pukes when it overruns it. I understand I could just initialize bits with a bigger buffer, or watch the buffer and stop encoding when it gets full. But I don't want to care about compressed frame sizes, nor *can* I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having a bit of trouble with cut and paste in Wine. I'm running a propiatary application, and when I try and use the middle click cut and paste from the program to another application it doesn't work. Is there a way to cut and paste from a Wine application or could it just be the program I'm using? Thanks, David P.S. Please

Hello, just to make sure I haven't gotten anything wrong: In cb_search.c (function split_cb_search_shape_sign) after all that searching nb_subvect CB entries are being written into the stream. These are all taken from the same codebook. If I wanted to, I could just change their order, couldn't I? Because important is only the linear combination of them all together, which I keep

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

Hi, I think what happened is that you did not write the "message" length. With user-callbacks, you also need to say how large the message. The size is in bytes and encoded in 4 bits. Besides, you're probably the first one to use user-callbacks. BTW, why didn't you want to use Ogg. It's much simpler to use and overhead can be made minimal anyway. Jean-Marc Le ven

Hi, I'm moving my "metadata" which accompanies some of the speech packets into the speex bits. However, as usual, I'm a bit confused. The manual (PDF from current SVN), section 5.10 (bottom of page 21) states that: "Finally, applications may define custom in-band messages using mode 13. The size of the message in bytes is encoded with 5 bits, so that the decoder can