similar to: Patch : Make speex_bits_read_from and speex_bits_read_whole_bytes const correct

Hi there. I made a couple of noted regarding the speex API. These are not meant be seen as critisism - rather constructive suggestions. I like speex a lot, but I would like it even more if some of the following features were available. ;) Christian <p>Comments about the Speex API - from a developer's perspective ------------------------------------------------------------- ***

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

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

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

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

> It is unusual to require a different sequence of API calls > depending on whether the signal is Mono or Stereo. > This is especially evident in the decoder where you would > register a callback for the SPEEX_INBAND_STEREO message. > The need for explicitly calling the speex_en/decode_stereo() > function in addition to speex_en/decode() is cumbersome. > All these tasks could

Hi all, i've to encode voice from a voicemodem. I choose speex 1.0.5 for its quality in voice encoding. I've tried to implement an encoder but unsuccesfully. Here's my code: /* ============ SPEEX stream ENCODER ============================================ */ int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { /* buffer point to the

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

I'm glad to hear that my data size can be shrunk considerably, however I do not know the minimum values that I would set the static arrays to be. I hate to be a bother but could you tell me the minimum values for these arrays/structures in the state structure? Thanks! encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch

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

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

Hello there, I thought I would contribute to this wonderful project but noting a simple but problematic bug in speex_bits_read_whole_bytes(). SITUATION: I have a large stream of frames with NO breaks or length indicators inbetween each frame. For this reason, I call speex_bits_read_whole_bytes() and fill it to MAXIMUM in a loop while calling speex_decode() until there are no more bytes to read.

Hi everyone, I've recently done some major internal changes in Speex aimed at reducing RAM (by nearly a factor of 2!) and improving quality of the fixed-point. In doing so, I might have accidently broken a few things. I'd like to hear feedback on the current svn code to make sure I fix any regression before the next release. I'm already aware that --enable-vorbis-psy is broken and

Hello, I'm having a problem using Speex - I'm getting white noise/static from the following process: (Load File) -> (Encode) -> (Decode) -> (Play) I know there's no issue with the loading or playing because (Load File)-> (Play) plays the file properly. I believe the problem lies with the speex_bits_write and speex_bits_read_from functions, because if I change my encode

I'm trying to use the speex API, and I think I'm missing something. I'm running on Mac OSX Tiger, and the attached microphone is a iSight. If I call the "speex_encode_int" function, and then immediately call the "speex_decode_int" function, shouldn't I get back the same data? i.e. in my example code, shouldn't the two arrays contain at least similar

When I just copy the microphone input buffer to the output buffer the sound plays OK. But if I encode and decode the buffer through Speex I get a high pitched constant tone in the background. I actually do hear my voice speaking when I talk, but it's faint and much quieter than the tone. Here's what my data looks like: Input is the first 5 floats of each input buffer. Output is

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

[sorry for the loss of proper attributions, this is from two messages]: [Me] >This is something I've encountered in trying to make a particular > asterisk application handle properly IAX2 frames which contain either > 20ms of 40ms of speex data. For a CBR case, where the bitrate is > known, this is fairly easy to do, especially if the frames _do_ always > end on byte

OK, I fixed it but: 1) you shouldn't be using the MAX_BYTES_PER_FRAME constant (just moved it to the .c where it belongs) 2) if you read more than MAX_BYTES_PER_FRAME the buffer will resize automatically, so there's no problem. Just use the size you want. Jean-Marc Le lun 25/08/2003 à 02:27, Thomas S a écrit : > Hello there, > I thought I would contribute to this wonderful

Thank you, I really appreciate the help. -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/07/07 8:34 AM >>> Michael Jacobson a ?crit : > I'm glad to hear that my data size can be shrunk considerably, > however I do not know the minimum values that I would set the static > arrays to be. I hate to be a bother but could you tell me the >