search for: split_cb_search_shape_sign_n1

Displaying 7 results from an estimated 7 matches for "split_cb_search_shape_sign_n1".

2005 May 29
0
cpu utilization across speex versions
....18% open_loop_nbest_pitch 0.12% qmf_decomp No preprocessor: (overall 2.12%) 0.43% split_cb_search_shape_sign 0.23% fir_mem_up 0.22% filter_mem2 0.21% vq_nbest 0.18% open_loop_nbest_pitch 0.11% qmf_decomp Speex 1.0.7: With preprocessor: (overall 2.33%) 0.28% speex_preprocess 0.25% vq_nbest 0.23% split_cb_search_shape_sign_N1 0.21% fir_mem_up 0.18% open_loop_nbest_pitch 0.18% filter_mem2 0.12% split_cb_search_shape_sign 0.11% qmf_decomp No preprocessor: (overall 1.95%) 0.26% vq_nbest 0.23% split_cb_search_shape_sign_N1 0.21% fir_mem_up 0.20% open_loop_nbest_pitch 0.16% filter_mem2 0.13% split_cb_search_shape_sign 0.12%...
2010 Mar 29
2
Speex on TI DSP 5505
Saju Palayur <saju_pa at hotmail.com> writes: > Hi > > > > We have ported the Narrow band 8 Khz Speex encoder and decoder on to TI DSP 5505 > > > > To compress 20ms of 16 bit audio sampled at 8Khz it takes 4.2ms. > > Is there any optimizations I can do to make it run faster. The first thing to do would be to profile the code (I assume you're using
2006 Feb 22
1
Some aditional details about split_cb_search_shape_sign
Hi all. I'm starting to study how speex works because I would like to understand in deep how a CELP coder/decoder works. I have some difficult understanding the vector quantization performed in the split_cb_search_shape_sign function. It's a bit hard to understand. Could you please explain me the algorithm step by step? I'm indagating the 5950 bps narrowband. Thank you. Gio.
2010 Mar 30
0
Speex on TI DSP 5505
Hi When we run the profiler these 3 functions take more than 8500 cycles. split_cb_search_shape_sign_N1() 22782 pitch_search_3tap() 19208 lpc_to_lsp() 16007 So can I configure these in a different way so it takes less cycles. I do not need very high sound quality Thanks for your time Warm Regards Saju > From: yates at ieee.org > To: saju_pa at hotmail.com > CC: speex-dev at xiph.org...
2010 Mar 30
2
Speex on TI DSP 5505
Saju Palayur <saju_pa at hotmail.com> writes: > Hi > > > > When we run the profiler these 3 functions take more than 8500 cycles. > > > > split_cb_search_shape_sign_N1() 22782 > pitch_search_3tap() 19208 > lpc_to_lsp() 16007 > > So can I configure these in a different way so it takes less cycles. I am not familiar with the code, so I can't say. I was trying to teach you how to optimize, not give you an optimization. --Randy > I do not need...
2006 Jan 18
2
TI 6xxx platform performance
...lse_response 200 1800518 1800518 pitch_gain_search_3tap 199 4726604 1744952 open_loop_nbest_pitch 199 4204121 1641016 vq_nbest 800 1626252 1626252 lpc_to_lsp 50 1612650 1558133 nb_encode 50 27412845 1179551 fir_mem2 50 1097300 1097300 inner_prod 27469 1072299 1072299 split_cb_search_shape_sign_N1200 7310588 1007711 normalize16 597 303378 303378, A lower cost option would be to use a floating point 6713. I thought that a 300Mhz floating point would come out even or ahead in an encoding comparison. Instead of the 300M/32=9.3M cycles per channel that I need, I see 71.5M cycles p...
2006 Jan 18
2
Errors in speex lib with Blackfin
Hello! I'v downloaded speex lib 1.1.11.1. I am trying to port speex lib to Blackfin processor. I am using VisualDSP++ 4.0. If I am compiling source codes with using floating point everything ok. When I am compiling with FIXED_POINT defined everything's ok and code works about two times faster. But when I am defining BFIN_ASM I am getting several compiling errors in Blackfin assembler