similar to: Bitrev for FFT

Hi, We're using Celt 0.7.1 at the moment. We're thinking to update the code to a newer version of it. Is there an appreciable complexity (decoding time) difference among versions (0.7.1 - 0.8.1 - 0.9.1 - 0.10 - 0.11.1)? If so, which one is the fastest? Thanks Regards Riccardo Riccardo Micci Senior DSP Engineer, Wireless Group Cambridge Consultants Science Park, Milton Road

Hi, In order to fit the decoder in memory in our embedded architecture we set the MAX_PERIOD #define equal to the frame size. This doesn't affect the code bit accuracy in normal decoding. The #define it's used celt_decode_lost function though. Is it possible to get celt_decode_lost to work with a value different from the default? Thanks Riccardo Riccardo Micci Senior DSP Engineer,

Hi, I'm using Celt version 0.7.1 in low complexity mode (i.e. no pitch information). In case a packet is lost i was planning to use the celt_decode_lost function. I realised though it uses pitch information inside. Does the celt_decode_lost function still works with no pitch information? Are there some changes to be done? Thanks Regards Riccardo Riccardo Micci Senior DSP Engineer,

Hi, I'm testing CELT 0.7.1 speed performance and I'm focusing now on the complexity switch. I've dug in the archive and i found some information. Is it still true that there are two ranges? - 0-2 low complexity mode - 3-10 high complexity mode If no input is given is 2 hence low complexity mode the default setting? Does the complexity mode affect decoding as well? Thank you Best

Hi, My name is Riccardo Micci i downloaded the CELT source code and I compiled it under Windows. This is meant to be a preliminary study for my company's project. When i run CELT it encodes and decodes the file back saying "Encoder matches decoder!!". When i try to play the output though the result is just noise and clicks. The only changes I've applied are some #defines to

Hi, I was checking complexity modes of CELT 07.1 encoder. If i got it correctly everything is driven by pitch_available variable set in celt_encoder_create function. By default it's set to 1 hence high complexity mode is used all the time. I tried to disable it and although i couldn't hear any particular difference in the decoded audio quality, the cycle count of the encoder dropped

Hi, I've recently successful built and run CELT under Windows using "testcelt.c" example file. Since I'm about to port it on a embedded platform i activated the FIXED_POINT #define. I included fixed_generic.h and without other changes to the code i tried to encode and decode the same file i previously used. The output though is completely saturated i.e. it jumps from -32768 to

Hello, I'm porting CELT 0.7.1 to an embedded platform and unfortunately (at least for me) CHAR is defined as 16 bits. I now got the vocoder compiling but when i compare the encoded output with a windows build, they don't match. Among the other problems i think that the char definition is one of the biggest players. I've seen in arch.h the following definitions: /* 2 on TI C5x DSP */

Hi, We're testing CELT (version 0.7.1) error resilience capability. We've used already celtdec packet-loss options. Hence we know what to expect in case of whole packet loss. How does Celt respond to a broken encoded packet? Is it always better to discard it and decode the missing frame through decode_lost? We have the hardware capability of protecting the frame with multiple CRCs.

Hi, I'm using Celt 0.7.1 in fixed math mode. In the celt_encode function, if the variable has_pitch is true, the function pitch_search is called. Within this function the find_best_pitch subfunction is called. Here the variable "float score;" is defined. Is this right? I was expecting not to see any float declaration in the fixed math code. Is it possible to redefine it as

eds to drag in the source and header files from the libcelt directory into = the project and define HAVE_CONFIG_H is the project's pre-processor definit= ion. The tricky part is to build a config.h file. To get it to work on VS some = of the important settings include. =20 #define CELT_BUILD #define USE_ALLOCA #undef VAR_ARRAYS #undef restrict #undef HAVE_STDINT_H #undef inline #define

Hi, Fiddling with Celt i found a possible bug. I'm using CELT 0.7.1, frame size 256, sample rate 32k and bitrate 64k. Here is the scenario: decoding side, celt_decode function. The "dec" structure is created at each function call and it's initialized with ec_dec_init function. The attribute "end_byte" is not initialized though. Decoding a file the behaviour is the

Hi, Does Celt (in particular version 0.7.1) exploits correlation between the two channels in stereo mode? In practice, is it possible to use the two channels as two mono signals without affecting quality? Thanks Best Regards Riccardo Riccardo Micci Senior DSP Engineer, Wireless Group Cambridge Consultants Science Park, Milton Road Cambridge, CB4 0DW, England Switchboard: +44 (0)1223

Uses NEON optimized fixed point fft routines in NE10 library Signed-off-by: Viswanath Puttagunta <viswanath.puttagunta at linaro.org> Signed-off-by: Jonathan Lennox <jonathan at vidyo.com> --- Makefile.am | 12 +- celt/arm/arm_celt_map.c | 46 ++-- celt/arm/celt_ne10_fft.c | 98 +++++---- celt/arm/fft_arm.h |

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics

Hello opus-dev, I've been cooking up this patchset to integrate NE10 library into opus. Current patchset focuses on encode use case mainly effecting performance of clt_mdct_forward() and opus_fft() (for float only) Glad to report the following on Encode use case: (Measured on my Beaglebone Black Cortex-A8 board) - Performance improvement for encode use case ~= 12.34% (Based on time -p

Viswanath Puttagunta wrote: > if OPUS_ARM_NEON_INTR > CELT_ARM_NEON_INTR_OBJ = $(CELT_SOURCES_ARM_NEON_INTR:.c=.lo) \ > - %test_unit_rotation.o %test_unit_mathops.o > -$(CELT_ARM_NEON_INTR_OBJ): CFLAGS += $(OPUS_ARM_NEON_INTR_CPPFLAGS) > + $(CELT_SOURCES_ARM_NE10:.c=.lo) \ > + %test_unit_rotation.o %test_unit_mathops.o \ > +

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics