similar to: [PATCH speexdsp] Don't rely on HAVE_STDINT_H et al. being defined

FTR, my main concern with this kind of approach is the case where your platform has two compilers, only one of which has stdint.h Jean-Marc On 07/05/2015 11:10 AM, Tanu Kaskinen wrote: > From: Tanu Kaskinen <tanu.kaskinen at linux.intel.com> > > Not everyone who includes speexdsp_config_types.h will have a test > which defines those, and if we've chosen to use the stdint

Hello, alsa-plugins currently includes speex/speex_types.h, but that doesn't work with speexdsp versions >= 1.2rc2, since speex_types.h has been replaced with speexdsp_types.h. I made a patch for alsa-plugins, so that it includes speexdsp_types.h instead. I also bumped the speexdsp version check from "1.2" to "1.2rc2" in configure.ac, since speexdsp_types.h didn't

On Tue, 2015-07-07 at 18:40 +0930, Ron wrote: > On Mon, Jul 06, 2015 at 05:35:51PM +0300, Tanu Kaskinen wrote: > > Hi all, > > > > I'm updating OpenEmbedded-core's speexdsp from 1.2rc1 (when it still was > > a part of the speex source tree) to 1.2rc3. I found out that building > > the new version for aarch64 fails in resample_neon.h (the target machine

Hi all, I'm updating OpenEmbedded-core's speexdsp from 1.2rc1 (when it still was a part of the speex source tree) to 1.2rc3. I found out that building the new version for aarch64 fails in resample_neon.h (the target machine is OE-core's default qemuarm64 target). This is the error message: .../speexdsp-1.2rc3/libspeexdsp/resample_neon.h:148:5: error: impossible constraint in

Hello Tristan, Thank you. But I am using libspeex library. Does the speexdsp library be included in it? Or it needs to be installed separate. Appreciate the help. Thanks, Ankhit On Thu, Aug 20, 2015 at 11:43 AM, Tristan Matthews <tmatth at videolan.org> wrote: > Hi Ankhit, > > On Thu, Aug 20, 2015 at 12:06 PM, Ankhit Vivekananda < > ankhit.vivekananda at biscotti.com>

On Thu, Jul 09, 2015 at 12:23:17PM +0300, Tanu Kaskinen wrote: > Hello, > > alsa-plugins currently includes speex/speex_types.h, but that doesn't > work with speexdsp versions >= 1.2rc2, since speex_types.h has been > replaced with speexdsp_types.h. Strictly speaking it hasn't been "replaced", it's just supplied by speex rather than speexdsp, as was the

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

On Mon, Jul 06, 2015 at 05:35:51PM +0300, Tanu Kaskinen wrote: > Hi all, > > I'm updating OpenEmbedded-core's speexdsp from 1.2rc1 (when it still was > a part of the speex source tree) to 1.2rc3. I found out that building > the new version for aarch64 fails in resample_neon.h (the target machine > is OE-core's default qemuarm64 target). This is the error message:

Hi apols as not really speex dev but really struggling to find this info that sure you will know in an instant. I am trying to compile alsa-plugins so I get the speexdsp as well as the rate conversion and just don’t know how. pi at raspberrypi:~/alsa-plugins-1.2.2 $ arecord -D mic ALSA lib dlmisc.c:287:(snd1_dlobj_cache_get) Cannot open shared library

Processing Conflict: speexdsp-1.2-0.9.rc3.el6.x86_64 conflicts speex <= 1.2-0.21.rc1 I am loath to replace things on my primary workstation as I have far too much to do as it is without dealing with self-inflicted injuries. However, I do use Jitsi as a softphone and the latest version has a dependency on a package in EPEL which replaces something from the base distro. Can someone inform me

I've looked at some partial examples and read in the pdf Manual that the Acoustic Echo Canceller can be used outside of the speex codec as a preprocessor. I currently have a java app that uses the ffmpeg api for live streaming. I'm exploring integrating echo cancellation & I'd like to use the speexdsp AEC by mapping a javacpp library to communicate between java & speex. Audio

Hello everyone, while I've been a user of both Vorbis and Speex since about 2005, this is the first time I write to the dev mailing list. I created ports for both SpeexDSP and Speex for Ravenports and have a question regarding the status of SpeexDSP. Ravenports is a new universal package building system for *nix systems that supports Linux, FreeBSD, DragonflyBSD and Solaris (with

anyone know how to get the aarch64 fork pulled into the mainline speexdsp? The code is provided in the bug report https://github.com/xiph/ speexdsp/issues/7 On Fri, Jul 29, 2016 at 5:21 PM, Frank Barchard <fbarchard at google.com> wrote: > I've filed a bug for aarch64 > https://github.com/xiph/speexdsp/issues/7 > > and provided the port in a fork with a pull request. We

Hi all, (Sorry that may be duplicated that I was not a mail-list member before, so last mail sent failed) I build successfully with speex-1.2rc2. And with speexdsp 1.2rc3, I build with i386, X86_64, armv7 and armv7s all passed. But when I build for ARM64 (for iPhone 6), it failed with: /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive Making all in libspeexdsp CC

Complains about missing Int16 functionality. So for 64bit on Arm you have to compile without –enable-neon and that has a huge effect on the AEC functionality. The Pi3 with neon is just struggling with the AEC routines as its audibly better on a Pi4 but its not the garble that a Pi0 produces. Without the neon on the Pi3 the 1.2 – 1.85 perf boost of neon with FFT is lost and it really effects AEC

Hi, On Sat, Mar 28, 2015 at 2:34 PM, Evan JIANG <firstfan at gmail.com> wrote: > Hi all, > > (Sorry that may be duplicated that I was not a mail-list member before, > so last mail sent failed) > > I build successfully with speex-1.2rc2. And with speexdsp 1.2rc3, I > build with i386, X86_64, armv7 and armv7s all passed. > But when I build for ARM64 (for

Hi I'm new to speex list but joined because I'm needing to port the Neon to ARM64. On that function, saturate_32bit_to_16bit(), I noticed the ifdef's are wrong. The first version is for normal arm 32 bit arm and should be used for arm32 and thumb2 but not thumb1. The second version is 32 bit neon and should be #ifdef __ARM_NEON__ I've done a third version which is 64 bit neon.

Actually its the ccflags I am using with that particular distro. -mcpu=cortex-a72 -mfloat-abi=hard -mfpu=neon-fp-armv8 -mneon-for-64bits Which is optimised for pi4 isn’t liked. Also without ccflag=”” configure: error: No 16 bit type found on this platform! ./configure --enable-neon --libdir=/usr/lib/aarch64-linux-gnu I dropped down to ubuntu 18.04 and the same errors occur. I have a

I have a doubt. This is an excerpt of the raw report I get after running Spec benchmarks through llvm-test.I am trying to calculate the program execution time.Does the output result in bold corresponds to "lli time" in Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the normal bytecode and native code execution times after running my pass over them.I have modified

On Sun, 4 Sep 2005, Tanu Sharma wrote: > > I have a doubt. > > This is an excerpt of the raw report I get after running Spec benchmarks > through llvm-test.I am trying to calculate the program execution > time.Does the output result in bold corresponds to "lli time" in > Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the > normal