search for: cel_pitch_xcorr_c

...l encode use case for "restricted-lowdelay 48000 2 96000" for CELT encoding as you suspected as celt_pitch_xcorr function gets used much more. I observed lesser improvement in performance (3.42%) for overall encode use case for "voip 48000 2 24000". This is somewhat expected as cel_pitch_xcorr_c was not the main contributor for performance in this SILK encoder use case. For detailed information on how I measured performance on my Beaglebone Black (Cortex-A8), please see "celt_pitch_xcorr (float) Neon Optimization" section of [1] [1]: https://docs.google.com/document/d/1L6csATjS...

...2 96000" for CELT >> encoding as you suspected as celt_pitch_xcorr function gets used much >> more. >> >> I observed lesser improvement in performance (3.42%) for overall >> encode use case for "voip 48000 2 24000". This is somewhat expected as >> cel_pitch_xcorr_c was not the main contributor for performance in this >> SILK encoder use case. >> >> For detailed information on how I measured performance on my >> Beaglebone Black (Cortex-A8), please see "celt_pitch_xcorr (float) >> Neon Optimization" section of [1] >&g...

...estricted-lowdelay 48000 2 96000" for CELT > encoding as you suspected as celt_pitch_xcorr function gets used much > more. > > I observed lesser improvement in performance (3.42%) for overall > encode use case for "voip 48000 2 24000". This is somewhat expected as > cel_pitch_xcorr_c was not the main contributor for performance in this > SILK encoder use case. > > For detailed information on how I measured performance on my > Beaglebone Black (Cortex-A8), please see "celt_pitch_xcorr (float) > Neon Optimization" section of [1] > > [1]: https://doc...

...>>> encoding as you suspected as celt_pitch_xcorr function gets used much >>> more. >>> >>> I observed lesser improvement in performance (3.42%) for overall >>> encode use case for "voip 48000 2 24000". This is somewhat expected as >>> cel_pitch_xcorr_c was not the main contributor for performance in this >>> SILK encoder use case. >>> >>> For detailed information on how I measured performance on my >>> Beaglebone Black (Cortex-A8), please see "celt_pitch_xcorr (float) >>> Neon Optimization" s...

Hello, I received feedback from engineers working on NE10 [1] that it would be better to use NE10 [1] for FFT optimizations for opus use cases. However, these FFT patches are currently in review and haven't been integrated into NE10 yet. While the FFT functions in NE10 are getting baked, I wanted to optimize the celt_pitch_xcorr (floating point only) and use it to introduce ARM NEON