search for: speex_set_user_handl

...ame_size, > int > synccount){ > > ... > > if (synccount > 0){ > callback.callback_id = 0; > callback.func = SpeexUserCallback; > callback.data = this; > speex_decoder_ctl(state, SPEEX_SET_USER_HANDLER, > &callback); > } > ... > > speex_bits_init_buffer_ex(&bits, pcData, dwLength); > > while (1 == 1){ > > ... > > retval = speex_decode(state, &bits, output); > >...

>I guess you'll need to somehow trace what's happening. > >> >Besides, you're probably the first one to use user-callbacks. >> >> Oh, I feel honoured. :-) >> >> Why does it contain this feature if nobody uses it? I think it's a good >> and very flexible feature (if it works :-)). > >I thought it could be useful in some cases,

Le ven 07/11/2003 à 13:37, Norman Biehl a écrit : > 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

...char* pcData, DWORD dwLength, int nchannels, int frame_size, int ynccount){ ... if (synccount > 0){ callback.callback_id = 0; callback.func = SpeexUserCallback; callback.data = this; speex_decoder_ctl(state, SPEEX_SET_USER_HANDLER, &callback); } ... speex_bits_init_buffer_ex(&bits, pcData, dwLength); while (1 == 1){ ... retval = speex_decode(state, &bits, output); if (retval == -1){ return -...

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

...5 bits, so that the decoder can skip it if it doesn?t know how to interpret it." Ok, so I prepend my data as such: speex_bits_pack(&sbBits, 13, 5); speex_bits_pack(&sbBits, length, 5); // bla bla insert my stuff then encode the packet. And this works :) My custom handler, set with SPEEX_SET_USER_HANDLER is called and everything is good. However, I kinda wondered what would happen if that handler WASN'T installed... And things aren't so good then. Looking at the code in speex_callbacks.c, it seems the speex_default_user_handler first unpacks 4 bits as size, then advances 8*size + 5...

hello, i switched to use the encoder.processData() and encoder.getProcessedData() of jspeex. however it looks to me like a memory leak ... memory usage is increasing very fast and there is no visible stop ... after about five minutes java.lang.OutOfMemory occurs. I think it must be the jspeex component, because before i added jspeex to my app usage was constant at about 5mb. is it possible

...{ SpeexCallback *c = (SpeexCallback*)ptr; st->speex_callbacks[c->callback_id].func=c->func; st->speex_callbacks[c->callback_id].data=c->data; st->speex_callbacks[c->callback_id].callback_id=c->callback_id; } break; case SPEEX_SET_USER_HANDLER: { SpeexCallback *c = (SpeexCallback*)ptr; st->user_callback.func=c->func; st->user_callback.data=c->data; st->user_callback.callback_id=c->callback_id; } break; case SPEEX_RESET_STATE: { int i; for...