Displaying 20 results from an estimated 9000 matches similar to: "Compiling opus for fixed point code"
2013 Jul 18
2
Help building OPUS library using FIXED_POINT option
Hi,
We are rebasing our audio compression subsystem using OPUS rather than SPEEX. The platform is Android but this piece is written in C code: we need to support armv5/armv7/x86 architectures.... and we use the released opus-1.1beta package from here<http://downloads.xiph.org/releases/opus/opus-1.1-beta.tar.gz>.
A lot of our OPUS build system + code to drive the audio compression has been
2014 Oct 15
1
Opus 1.1.1 beta breaks floating point integrity?
HI
trying to build libopus beta compiler complains about more fixed point
specific names referenced in common unconditional code
Particularly:
./celt/x86/celt_lpc_sse.c(100): error: identifier "SIG_SHIFT" is undefined
noA = EXTEND32(1) << SIG_SHIFT >> 1;
^
SIG_SHIFT is defined in arch.h provided FIXED_POINT is used (not on
floating point
2016 Jul 14
0
[PATCH 2/5] Optimize fixed-point celt_fir_c() for ARM NEON
Create the fixed-point intrinsics optimization celt_fir_neon() for ARM NEON.
Create test tests/test_unit_optimization to unit test the optimization.
---
.gitignore | 1 +
Makefile.am | 39 ++++-
celt/arm/arm_celt_map.c | 17 +++
celt/arm/celt_lpc_arm.h | 65 ++++++++
celt/arm/celt_lpc_neon_intr.c
2018 Mar 22
1
Opus configuration for ARM cortex M7
Hi, I'm planning to use Opus codec on a ARM cortex M7 device running at
400MHz.
Con you please suggest the best configuration directives that I have to
set in the config.h file in order to obtain the best perfromances on the
cortex M7 architecture?
Actually I have compiled libopus 1.2.1 with the following cnfiguration
parameters:
#define VAR_ARRAYS 1
#define FIXED_POINT 1
#define
2014 Sep 04
2
Opus decoding performance on ARM devices
Hi everyone,
I have lately been evaluating the performance of various audio decoders,
particularly for ARM devices (Cortex A8 / A9). The context is audio
playback in a game engine, and thus decoding performance is of particular
interest.
Looking at Opus versus Vorbis on a Cortex A9 smartphone, the numbers look
approximately like this:
Vorbis (tremolo decoder)
9.3 Mb PCM/s
Opus (libopus 1.1)
2014 Sep 05
2
Opus decoding performance on ARM devices
Hi,
Thank you for your response. I pulled yesterday to commit
da97db1ca1f92592af3534c9a2596da0e9a009ca, added a bunch of more defines to
my compile options, and assembled & linked in
armopts.s,celt_pitch_xcorr_arm.s.
Performance jumped up from about 4.8 Mb/s to 5.3 Mb/s on the same device,
so it is improvement. Not sure what other tweaks there would be to try,
but if it could match the
2014 Sep 04
0
Opus decoding performance on ARM devices
Hi Dan,
I suggest you try the code in git master, which has further ARM
optimizations compared to 1.1.
Cheers,
Jean-Marc
On 04/09/14 08:00 AM, Dan Nilsson wrote:
> Hi everyone,
>
> I have lately been evaluating the performance of various audio decoders,
> particularly for ARM devices (Cortex A8 / A9). The context is audio
> playback in a game engine, and thus decoding
2014 Nov 21
0
[RFC PATCHv1] armv7: celt_pitch_xcorr: Introduce ARM neon intrinsics
Optimize celt_pitch_xcorr function (for floating point)
using ARM NEON intrinsics for SoCs that have NEON VFP unit.
As initial step, targeting ARMv7 NEON (VFP3+) based SoCs.
To enable this optimization, use --enable-arm-neon-intrinsics
configure option. This flag is not enabled by default.
Compile time and runtime checks are also supported to make sure
this optimization is only enabled when the
2015 May 08
0
[[RFC PATCH v2]: Ne10 fft fixed and previous 1/8] armv7(float): Optimize encode usecase using NE10 library
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
2015 Nov 21
0
[Aarch64 v2 08/18] Add Neon fixed-point implementation of xcorr_kernel.
Used for celt_pitch_xcorr on aarch64, and celt_fir and celt_iir on both armv7 and aarch64.
---
celt/arm/arm_celt_map.c | 17 +++++++++++++
celt/arm/celt_neon_intr.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++-
celt/arm/pitch_arm.h | 31 +++++++++++++++++++++++-
3 files changed, 107 insertions(+), 2 deletions(-)
diff --git a/celt/arm/arm_celt_map.c b/celt/arm/arm_celt_map.c
index
2013 Jul 18
0
Help building OPUS library using FIXED_POINT option
On 13-07-18 8:12 AM, Dubois-Rande, Antoine wrote:
> C:/android/android-ndk-r8e/toolchains/arm-linux-androideabi-4.6/prebuilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld.exe: ./obj/local/armeabi/lib0.a(analysis.o): in function
> run_analysis:jni/src/libopus/src/analysis.c:636: error: undefined reference to
> 'optimize_framesize'
2015 Jan 20
0
[RFC PATCH v1 2/2] armv7(float): Optimize encode usecase using NE10 library
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
2004 Sep 29
3
Fixed point bug in 1.1.6
Please compare samples:
http://www.ivo.pl/ivo2/sound/krwawa_org.wav
http://www.ivo.pl/ivo2/sound/krwawa_fixed.wav
http://www.ivo.pl/ivo2/sound/krwawa_float.wav
krwawa_org.wav is original file.
Both output files was created using same program by compressing from wav
to speex, then decompressing from speex to wav (using speex_encode_int
and speex_decode_int).
Only difference was used speex
2015 Feb 04
0
[RFC PATCH v2] armv7(float): Optimize encode usecase using NE10 library
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
2015 Mar 03
0
[RFC PATCHv3] armv7(float): Optimize encode usecase using NE10 library
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
2013 Sep 24
0
Problem compiling opus-tools-0.1.7
Hi,
Seems like it's not linking with libm. I suspect it has to do with
linking statically with libopus.a (is that intended?). Maybe opus-tools
relies on the fact that libopus is linked with libm and doesn't
explicitly add it? Greg?
Jean-Marc
On 09/24/2013 06:09 AM, bat guano wrote:
> Hi
> I'm having a problem compiling opus-tools-0.1.7.
> Version opus-tools-0.1.6 seems to
2015 May 15
0
[RFC V3 7/8] armv7, armv8: Optimize fixed point fft using NE10 library
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 |
2007 May 02
0
Fixed point port status, 2 May 2007?
Could you please explain what features has been already ported to FIXED_POINT
and which others aren't yet?
Please add some details on how to understand by looking inside code if a feature
is alredy ported or not.
For example, where i see float declaration or wherever i see you're using FPU
doing float multiplications/divisions etc, this without any alternative code with FIXED_POINT
2019 Apr 10
0
Opus cmake build
Hi Mark,
Thanks for the feedback.
By default CMake is building the static library in debug, to get other things one has to explicit turn it on.
To build in release mode for CMake you use the following flag:
-DCMAKE_BUILD_TYPE=Release
https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html
CMAKE_BUILD_TYPE — CMake 3.14.1
2013 Nov 13
0
Compiling FFmpeg with libopencore-amrnb and opus-git.
It appears that both Opus and amrnb have a function called
preemphasis(). In the short term, your options are:
1) Not building statically
2) Renaming that function in the Opus code
3) Renaming that function in the amrnb code
I can do the rename for the next version of libopus.
Cheers,
Jean-Marc
On 11/13/2013 05:51 PM, batguano999 wrote:
>
> Hi
> Any idea what's causing these