similar to: Attempting to shrink speex: Are these functions necessary?

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

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

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 >

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'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

The section that establishes the MIME type is stating audio/x-speex. Per the MIME Types and File Extensions it should be audio/ogg. If the change will be made, there's no need to put it as audio/x-ogg as the IETF values MIME types already in use. -Ivo

Oleg Homenko a ?crit : > Hi, > I started to optimize math_approx fixed point functions to ARM CPU. And > found out that approximations are not Taylor series, That's right. for example: > spx_exp2(x) = D0 + D1*x + D2*x^2 +D3*x^3, > where D0 = 1, D1 = log(2), D2 = (log(2))^2 / 2, D3 = (log(2))^3 / 6 for > Taylor serie, > but Speex source code uses different coefficients:

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

First, let me say that I think the speex code is incredible in the way it supports floating and fixed point code from one set of code. The same is true for supporting multiple processors, etc... I've used speex with the PC, TI 64xx and 55xx. Please view the following comments not as an attack on speex (which I think is incredible!) but as my contribution to an open source project. I know

Hi, I'm trying to compile speex1.2-rc1 for Symbian 3th edition. I get some errors: ***Invoking bldmake command perl.exe -S bldmake.pl bldfiles winscw \Users\Maurizio\University\ProgettoInterdisciplinare\speex-1.2rc1\speex-1.2rc1\symbian\BLD.INF FATAL ERROR(S): \Users\Maurizio\University\ProgettoInterdisciplinare\speex-1.2rc1\speex-1.2rc1\symbian\BLD.INF(37) : Exported source file

--- Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > Sorry if this a repost but I want to create the > > smallest Speex library possible to be put in TI's > > TMS320 DSP. I'm only interested in one > configuration: > > 5.97 Kbps narrowband. What part of source code > can I > > remove? Currently, when I compiled the version >

Dear Valin, Please, can you explain me the mean of the routines' parameters: 1. void vq_nbest(); 2. static void compute_weighted_codebook(); 3. static inline void target_update(); 4. void split_cb_search_shape_sign(); 5. void split_cb_shape_sign_unquant(); 6. void noise_codebook_quant(); 7. void noise_codebook_unquant(); and what they do briefly??? It's very difficult understand a