similar to: New function for manipulating SpeexBits

It would be nice to have the following function added to the speex bits... void speex_bits_read_from_buffer( SpeexBits * const bits, void * const buff, const int buf_size) { bits->bytes = (char*)buff; bits->buf_size = buf_size; bits->nbBits = buf_size << 3; bits->bytePtr = 0; bits->bitPtr = 0; bits->owner = 0;

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

i'm optimizing some features....for exemple why not doing this : ------------------------------------------------------------------------------- void speex_bits_advance(SpeexBits *bits, int n) { if (((bits->bytePtr<<3)+bits->bitPtr+n>bits->nbBits) || bits->overflow){ bits->overflow=1; return; } bits->bytePtr += (bits->bitPtr+nbBits) >>

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

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

Hi SAITAMA Taro, I have been using speex-1.2beta1 dll in our voice application written with C#. In order to use Speex correctly firstly I advice to you examination speexenc and speexdec projects. I have used unsafe code and fixed statements in C#. I have added following method to library and I used that instead of speex_encoder_init simply. void *speex_encoder_init_new(int modeID) { const

Hi, I have read the message below, http://lists.xiph.org/pipermail/speex-dev/2006-October/004924.html and try to use P/Invoke to use speex in C#. This is a part of my code. [StructLayout(LayoutKind.Sequential)] public struct SpeexBits { IntPtr chars; // "raw" data int nbBits; // Total number of bits stored in the stream int charPtr; // Position of the byte

hello guys this is my code for the C# wrapper. ================================= using System; using System.Runtime.InteropServices; using System.IO; namespace Speex { ///<summary> ///the following class is the win32 SPEEX API that retrieve ///methods and structures from the libspeex file ///</summary> public unsafe class Speex_win32 { #region Speex Constants //global speex

Hi there, I have searched what seems like everywhere and was unable to find a .NET wrapper so that I can use speex in VB. I did find a speex.NET.dll but this didn't seem to work on what I needed. I therefore decided I could just use DllImport within VB .NET and create my own unmanaged links to libspeex.dll. With the help of this partial c# code

I'm trying to use speex on OMAP's DSP using dsp gateway, and have some questions. The code almost works (within few next days I'll post a some kind tutorial and patches), but it seems to be a little bug in bits.c. The code looks like this void speex_bits_read_from(SpeexBits *bits, char *chars, int len) { ////////////////// bla-bla-bla /////////////////// for (i=0;i<len;i++)

Hi All, I am trying to cross compile speex-1.1.12 to powerpc-405, i get a error after the make, speexec.lo error, please help me how to get rid of this error. On 2/9/07, speex-dev-request@xiph.org <speex-dev-request@xiph.org> wrote: > Send Speex-dev mailing list submissions to > speex-dev@xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit >

Le mer 12/03/2003 à 23:46, Daniel Vogel a écrit : > >From the sample encoder/ decoder demo in the documentation it seems that I > only have to call speex_bits_reset before encoding a new frame. Is this > still the case if I reuse the SpeexBits to both encode and decode different > streams? I'm not sure I fully understand you question... what speex_bits_reset is to make the

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

Tom Grandgent a ?crit : > You might not be doing anything wrong. Speex is stateful and can > get into a bad state sometimes. It's happened to me too, but not > recently. And I've seen such bugs reported on this list and fixed. > I suggest several approaches to solving the problem: Tom, can you give an example of how Speex can enter a "bad state"? I don't

Thanks, it makes more sense to me now. Does speex_bit_read_from also append in that manner? Jean-Marc Valin wrote: > speex_bits_reset is before encoding, not decoding. If you don't call it, > then everything you encode will be appended so it will grow without end. > As for the point of the SpeexBits struct, it's there as a sort of "array > of bits" to it's easy

Jean-Marc, I hate to say such things about Speex, especially when I've been unable to make such problems consistently reproducible. It takes a great deal of patience and effort to track down a rarely occurring problem like this in a production VOIP system. I ended up solving my problems by being more careful with the input to the encoder and switching to an SVN version of Speex. This

You're doing something wrong. Read the documentation and check speechenc/dec just one more time. If that wouldn't help I'd suggest posting samples of your source code and describe what platform/compiler/os you're using. //JT -----Ursprungligt meddelande----- Fr?n: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] F?r jesus Skickat: den 22 januari 2007 19:43 Till:

>From the sample encoder/ decoder demo in the documentation it seems that I only have to call speex_bits_reset before encoding a new frame. Is this still the case if I reuse the SpeexBits to both encode and decode different streams? Thanks, -- Daniel, Epic Games Inc. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

The example in the documentation demonstrates using speex_bits_reset before encoding and decoding each frame. " speex_bits_reset(&bits); speex_encode(enc_state, input_frame, &bits); nbBytes = speex_bits_write(&bits, byte_ptr, MAX_NB_BYTES); " What happens if this is not done? I think I'm missing the point of having a SpeexBits object.

> both at the same time. Basically, you can see SpeexBits as just a string > of bits that can be accessed using a set of functions. Does that answer > your question? Yes, thanks! -- Daniel, Epic Games Inc. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to