search for: _neon

Hi, Thank you for a great work. Opus codec works great under many platforms. I have found a small performance issue under iOS platform. If the macro OPUS_HAVE_RTCD is not set, then encoder doesn't use some _neon functions at low bitrates (up to 64k). If the macro is set, then the compiler hits the error at opus/celt/arm/armcpu.c:153 (a function for detection missed). Being compared to Android version performance degradation is ~30%. Detection NEON under iOS is a bit tricky, because there is no API for it....

...ll optimized functions are called directly under iOS. Regards, Victor -----Original Message----- From: Jonathan Lennox Sent: Thursday, August 30, 2018 11:59 AM To: Victor Cherepanov Cc: opus at xiph.org Subject: Re: [opus] NEON detection under iOs On iOS, configure should define OPUS_ARM_PRESUME_NEON and OPUS_ARM_PRESUME_NEON_INTR if you’re building for armv7, and OPUS_ARM_PRESUME_NEON_INTR for arm64 (since every Apple armv7 CPU has supported Neon, and of course arm64 supports it though the assembler syntax is different). This should be slightly faster than using RTCD, since the Neon funct...

Thank Jean-Mark and Jonathan! I tested current OPUS encoder in floating-point with Complexity 8. Hacking using the attached patch (which will generate "#define OPUS_ARM_MAY_HAVE_NEON 1" in config.h) will speed up about 14.7% on my Chromebook. Probably it's because many NEON intrinsics optimizations can benefit both fixed-point and floating-point encoder. So if it's safe enough to enable MAY_HAVE_NEON in floating-point by default, it could speed up floating-point N...

On iOS, configure should define OPUS_ARM_PRESUME_NEON and OPUS_ARM_PRESUME_NEON_INTR if you’re building for armv7, and OPUS_ARM_PRESUME_NEON_INTR for arm64 (since every Apple armv7 CPU has supported Neon, and of course arm64 supports it though the assembler syntax is different). This should be slightly faster than using RTCD, since the Neon functions...

...m/projectNe10/Ne10 Regards, Vish On 9 November 2014 15:34, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > > Hello, > > This patch introduces ARM NEON Intrinsics to optimize > kf_bfly4 routine in celt part of libopus. > > Using NEON optimized kf_bfly4(_neon) routine helped improve > performance of opus_fft_impl function by about 21.4%. The > end use case was decoding a music opus ogg file. The end > use case saw performance improvement of about 4.47%. > > This patch has 2 components > i. Actual neon code to improve kf_bfly4 > ii....

Semantically, OPUS_ARM_MAY_HAVE_NEON is supposed to mean the compiler supports, and the CPU may support, Neon assembly code, which isn’t necessarily the same thing as the compiler supporting Neon intrinsics. (The Visual Studio ARM compiler, for instance, supports intrinsics but not assembly.) So I don’t think this patch is the right...

Thank Jonathan! I'll fix the MAY_HAVE_NEON() in silk/arm/arm_silk_map.c Linfeng On Thu, Jun 1, 2017 at 3:34 PM, Jonathan Lennox <jonathan at vidyo.com> wrote: > Semantically, OPUS_ARM_MAY_HAVE_NEON is supposed to mean the compiler > supports, and the CPU may support, Neon assembly code, which isn’t > necessarily the same t...

Hello, This patch introduces ARM NEON Intrinsics to optimize kf_bfly4 routine in celt part of libopus. Using NEON optimized kf_bfly4(_neon) routine helped improve performance of opus_fft_impl function by about 21.4%. The end use case was decoding a music opus ogg file. The end use case saw performance improvement of about 4.47%. This patch has 2 components i. Actual neon code to improve kf_bfly4 ii. Infrastructure to include neon int...

...Neon intrinsics for Silk noise shape feedback loop. Add Neon fixed-point implementation of xcorr_kernel. Makefile.am | 5 +- celt/arm/arm_celt_map.c | 17 ++++++ celt/arm/armcpu.c | 35 +++++++---- celt/arm/armcpu.h | 6 ++ celt/arm/celt_neon_intr.c | 61 ++++++++++++++++++- celt/arm/pitch_arm.h | 31 +++++++++- silk/NSQ.c | 57 ++++++----------- silk/NSQ.h | 97 +++++++++++++++++++++++++++++ silk/NSQ_del_dec.c | 40 +++++------- silk/arm/NSQ_neon.c | 135...