search for: fir_mem16

-----Original Message----- From: Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> To: ??????? ??????? <altersoft at mail.ru> Date: Sat, 02 Aug 2008 07:54:34 -0400 Subject: Re: [Speex-dev] fir_mem16,iir_mem16 and filter_mem16 optimisations > > ??????? ??????? a ?crit : > > I have some questions about that functions: fir_mem16, iir_mem16 and filter_mem16. > > Filtering is very slow on TI DSP, and i want to optimise it. > > Can somebody give me formulas which discribe...

Hi! I have some questions about that functions: fir_mem16, iir_mem16 and filter_mem16. Filtering is very slow on TI DSP, and i want to optimise it. Can somebody give me formulas which discribe work of this filters? Or any suggestions about how to transform code for better performance. I going to implement this functions in assembler, but it is hard to d...

...; 2) Have you enabled the current ARM4 assembly bits? > 3) There are a couple functions that could definitely benefit from > assembly optimisations. They used to be optimised for AMR4, but I had to > remove that when I optimised the C version. Those are filter_mem16(), > iir_mem16() and fir_mem16(). Let me know if you're going to do that > because the best way to do it is not to start from the current C code. > Yes, I have enabled the the current ARM4 assembly bits. I have tried to optimize these functions(filter_mem16(),iir_mem16() and fir_mem16()) in C code, but the effect is v...

Hi, all, I am porting speex on ARM7TDMI, I have done some optimization, the result is that the encoder and decoder need about 60 MCPS for 5.96kbps bitrate and complexity 0. Can someone give me informtion about Speex optimization on ARM7? Another question, my ADC and DAC are 12 bits, but Speex codec is 16bits, Did someone try to modify speex to 12 bits? I think if I modify speex to 12 bits, the

...cpu. Am I correct to assume that there are massive floating point calculations happening? I did a quick profile with CodeAnalyst and identified the most expensive functions as (in order): CPU Clocks, Function 4657, kiss_fft_stride 4456, speex_echo_cancellation 2494, split_cb_search_shape_sign 1490, fir_mem16 1419, speex_preprocess_run I'm looking for advise on how to boost the performance with as little code rewrite as possible. The architecture for release build will be SSE/SSE2 capable. 1) Compiler optimizations: Recommended options? 2) SIMD. Is Speex written to take advantage of SIMD architectur...

...omething else? I replaced the interpolated lpc (variable "interp_lpc") with the original lpc (variable lpc) for residual generation. This makes the situation worse, so lpc interpolation seems to "smooth" the error and reduces it. I will check the computation of the lpc and the fir_mem16 routine now. cheers, Frank Jean-Marc Valin <Jean-Marc.Valin at USherbrooke.ca> hat am 2. Februar 2010 um 17:57 geschrieben: > Just had a look and the fixed-point residual *does* look odd. That's worth > investigating (though I don't think it's related to LPC stability). &...

...gt; > happening? > > I did a quick profile with CodeAnalyst and identified the most expensive > > functions as (in order): > > CPU Clocks, Function > > 4657, kiss_fft_stride > > 4456, speex_echo_cancellation > > 2494, split_cb_search_shape_sign > > 1490, fir_mem16 > > 1419, speex_preprocess_run > > I'm looking for advise on how to boost the performance with as little > code > > rewrite as possible. The architecture for release build will be SSE/SSE2 > > capable. > > 1) Compiler optimizations: Recommended options? > &gt...

...2% filter_mem16 4.14% inner_prod 4.07% iir_mem16 2.75% qmf_synth 2.32% lsp_to_lpc 2.32% open_loop_nbest_pitch 1.41% compute_impulse_response 1.37% qmf_decomp 1.28% lpc_to_lsp 1.26% fir_mem16 1.16% speex_bits_pack 1.07% speex_bits_unpack_unsigned 0.86% compute_rms16 0.79% 4. I'm using the echo-canceller + preprocessor, I'd really like to improve performance here: - I would like to use ADI's FFT, but it's limited to powers of 2, i...

...;s a cost in quality) 2) Have you enabled the current ARM4 assembly bits? 3) There are a couple functions that could definitely benefit from assembly optimisations. They used to be optimised for AMR4, but I had to remove that when I optimised the C version. Those are filter_mem16(), iir_mem16() and fir_mem16(). Let me know if you're going to do that because the best way to do it is not to start from the current C code. > Another question, my ADC and DAC are 12 bits, but Speex codec is > 16bits, Did someone try to modify speex to 12 bits? I think if I > modify speex to 12 bits, the computa...

> Yes, I have enabled the the current ARM4 assembly bits. I have tried > to optimize these functions(filter_mem16(),iir_mem16() and > fir_mem16()) in C code, but the effect is very small, and I am going > to do assembly optimization for these functions. Do you have another C > code about these functions for assembly optimisations? Can you give me > some information and suggestions? Basically, if either of these apply to your CPU:...

...re massive floating point calculations > happening? > I did a quick profile with CodeAnalyst and identified the most expensive > functions as (in order): > CPU Clocks, Function > 4657, kiss_fft_stride > 4456, speex_echo_cancellation > 2494, split_cb_search_shape_sign > 1490, fir_mem16 > 1419, speex_preprocess_run > I'm looking for advise on how to boost the performance with as little code > rewrite as possible. The architecture for release build will be SSE/SSE2 > capable. > 1) Compiler optimizations: Recommended options? > 2) SIMD. Is Speex written to take...

...I did a quick profile with CodeAnalyst and identified the most expensive > > > functions as (in order): > > > CPU Clocks, Function > > > 4657, kiss_fft_stride > > > 4456, speex_echo_cancellation > > > 2494, split_cb_search_shape_sign > > > 1490, fir_mem16 > > > 1419, speex_preprocess_run > > > I'm looking for advise on how to boost the performance with as little > > code > > > rewrite as possible. The architecture for release build will be SSE/SSE2 > > > capable. > > > 1) Compiler optimizations:...

...bound -R gain_cdbk_lbr -R gain_cdbk_nb -R hexc_10_32_table -R hexc_table -R high_lsp_cdbk -R high_lsp_cdbk2 -R lag_window -R lpc_window -R shift_filt -R vbr_hb_thresh -R vbr_nb_thresh -R vbr_uhb_thresh -T bw_lpc -T compute_impulse_response -T compute_rms -T compute_rms16 -T filter_mem16 T _fini -T fir_mem16 -T forced_pitch_quant -T forced_pitch_unquant -T highpass -T iir_mem16 T _init -T inner_prod -T interp_pitch -T lpc_to_lsp -T lsp_enforce_margin -T lsp_interpolate -T lsp_quant_high -T lsp_quant_lbr -T lsp_quant_nb -T lsp_to_lpc -T lsp_unquant_high -T lsp_unquant_lbr -T lsp_unquant_nb -T multicomb...

...bound -R gain_cdbk_lbr -R gain_cdbk_nb -R hexc_10_32_table -R hexc_table -R high_lsp_cdbk -R high_lsp_cdbk2 -R lag_window -R lpc_window -R shift_filt -R vbr_hb_thresh -R vbr_nb_thresh -R vbr_uhb_thresh -T bw_lpc -T compute_impulse_response -T compute_rms -T compute_rms16 -T filter_mem16 T _fini -T fir_mem16 -T forced_pitch_quant -T forced_pitch_unquant -T highpass -T iir_mem16 T _init -T inner_prod -T interp_pitch -T lpc_to_lsp -T lsp_enforce_margin -T lsp_interpolate -T lsp_quant_high -T lsp_quant_lbr -T lsp_quant_nb -T lsp_to_lpc -T lsp_unquant_high -T lsp_unquant_lbr -T lsp_unquant_nb -T multicomb...