search for: split_cb_shape_sign_unquant

...tic const SpeexSubmode nb_submode4 = { -1, 0, 1, 0, /*LSP quantization*/ lsp_quant_lbr, lsp_unquant_lbr, /*Pitch quantization*/ pitch_search_3tap, pitch_unquant_3tap, &ltp_params_med, /*Innovation quantization*/ split_cb_search_shape_sign, split_cb_shape_sign_unquant, &split_cb_nb_med, QCONST16(.45,15), 220 }; /* Parameters for Long-Term Prediction (LTP)*/ static const ltp_params ltp_params_lbr = { gain_cdbk_lbr, 5, 7 }; /* Split-VQ innovation parameters narrowband */ static const split_cb_params split_cb_nb_med = { 8...

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 code written by another person! I thank you in advance. ---------------------------------------------------------------- This message was sent using IMP, the In...

Hi, So I see in: split_cb_shape_sign_unquant this call is going wrong: ind[i] = speex_bits_unpack_unsigned(bits, params->shape_bits); ind as a way negative number- basically this should return bet. 0-255 or somesuch right? So seems like I need to reset speex at this point if if (ind[i] > 256) like the note says. So I guess my ques...

...*/ > > lsp_quant_lbr, > > lsp_unquant_lbr, > > /*Pitch quantization*/ > > pitch_search_3tap, > > pitch_unquant_3tap, > > &ltp_params_med, > > /*Innovation quantization*/ > > split_cb_search_shape_sign, > > split_cb_shape_sign_unquant, > > &split_cb_nb_med, > > QCONST16(.45,15), > > 220 > > }; > > > > /* Parameters for Long-Term Prediction (LTP)*/ > > static const ltp_params ltp_params_lbr = { > > gain_cdbk_lbr, > > 5, > > 7 > >...

...E45D.4010902@mail.inf.tu-dresden.de> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > Jean-Marc Valin wrote: >> Well, you could change the order in the encoder as long as you reverse >> it in the decoder as well. > > Ok, I see that in the split_cb_shape_sign_unquant function, that each > coefficient is tied to it's position in the nb_subvect exc coefficients. > > Honestly, I have problems understanding what exactly the codebook search > works like. If you have the time to to that, Jean-Marc, I would > appreciate some hints on the following:...

...E45D.4010902@mail.inf.tu-dresden.de> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > Jean-Marc Valin wrote: >> Well, you could change the order in the encoder as long as you reverse >> it in the decoder as well. > > Ok, I see that in the split_cb_shape_sign_unquant function, that each > coefficient is tied to it's position in the nb_subvect exc coefficients. > > Honestly, I have problems understanding what exactly the codebook search > works like. If you have the time to to that, Jean-Marc, I would > appreciate some hints on the following:...

...Cc: speex-dev@xiph.org Message-ID: <450FE45D.4010902@mail.inf.tu-dresden.de> Content-Type: text/plain; charset="iso-8859-1" Hi, Jean-Marc Valin wrote: > Well, you could change the order in the encoder as long as you reverse > it in the decoder as well. Ok, I see that in the split_cb_shape_sign_unquant function, that each coefficient is tied to it's position in the nb_subvect exc coefficients. Honestly, I have problems understanding what exactly the codebook search works like. If you have the time to to that, Jean-Marc, I would appreciate some hints on the following: 1. What is the point in...

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

Hi, Jean-Marc Valin wrote: > Well, you could change the order in the encoder as long as you reverse > it in the decoder as well. Ok, I see that in the split_cb_shape_sign_unquant function, that each coefficient is tied to it's position in the nb_subvect exc coefficients. Honestly, I have problems understanding what exactly the codebook search works like. If you have the time to to that, Jean-Marc, I would appreciate some hints on the following: 1. What is the point in...

...6 @@ T speex_default_user_handler T speex_encode T speex_encode_int -T speex_encode_native T speex_encoder_ctl T speex_encoder_destroy T speex_encoder_init @@ -144,17 +60,6 @@ T speex_stereo_state_destroy T speex_stereo_state_init T speex_stereo_state_reset -T split_cb_search_shape_sign -T split_cb_shape_sign_unquant -T _spx_autocorr -T _spx_lpc -T syn_percep_zero16 -T vbr_analysis -T vbr_destroy -T vbr_init -T vq_nbest -T vq_nbest_sign -T wb_mode_query U acosf U calloc U exit -------------- next part -------------- --- libspeexdsp.old 2008-03-29 03:05:30.000000000 +0100 +++ libspeexdsp.new 2008-03-29 03:00:...

...6 @@ T speex_default_user_handler T speex_encode T speex_encode_int -T speex_encode_native T speex_encoder_ctl T speex_encoder_destroy T speex_encoder_init @@ -144,17 +60,6 @@ T speex_stereo_state_destroy T speex_stereo_state_init T speex_stereo_state_reset -T split_cb_search_shape_sign -T split_cb_shape_sign_unquant -T _spx_autocorr -T _spx_lpc -T syn_percep_zero16 -T vbr_analysis -T vbr_destroy -T vbr_init -T vq_nbest -T vq_nbest_sign -T wb_mode_query U acosf U calloc U exit -------------- next part -------------- --- libspeexdsp.old 2008-03-29 03:05:30.000000000 +0100 +++ libspeexdsp.new 2008-03-29 03:00:...