similar to: Processing Conflict: speexdsp-1.2-0.9.rc3.el6.x86_64

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, 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

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 need someone to review/merge in the pull request? It provides the source code, but my testing was under Android builds, so there would be some configure changes needed to build it stand alone. On Tue, Apr 19, 2016 at 4:32 PM, Frank Barchard <fbarchard at

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 types at configure time then we know exactly which header(s) are available, so just choose the best one then and generate the header to use it. This patch, including the above text, is copied from a commit

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 all, 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 preprocess.lo CC jitter.lo CC mdf.lo CC fftwrap.lo CC

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

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

Thanks ... > Those links seem to work here. 2 links "http://rarewares.hydrogenaudio.org" redirect to "https://hydrogenaud.io" ... no "rarewares" subdomain "http://git.xiph.org/speex.git" maybe better "http://git.xiph.org/?p=speex.git;a=summary" "http://git.xiph.org/speexdsp.git" maybe better

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

On Wed, August 3, 2016 22:53, Alice Wonder wrote: > > I didn't realize ldd was recursive. I may have known that at one > point (been using linux since MK Linux DR3 and building RPMs since > 1999), but have a head injury results in memory problems with > pieces of knowledge I don't frequently use. Most of us have that problem; head injuries or not. -- *** e-Mail

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 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.

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

Le 03/05/2020 ? 08:44, Benson Muite a ?crit?: > They have rpms: > > https://download.jitsi.org/jitsi/rpm/ That's the Jitsi desktop application. > > and also a scalable installation: > > https://github.com/jitsi/jitsi-meet/blob/master/doc/scalable-installation.md That's Debian-specific. > > Which one do you need? None. I need a comprehensive

Benson, no SELINUX was not enabled. The instance was selected without it just to make things easier. I do not have a pull request for the installation manual yet. On Tue, May 5, 2020 at 1:21 AM Benson Muite <benson_muite at emailplus.org> wrote: > > On Mon, May 4, 2020, at 10:38 PM, Erick Perez - Quadrian Enterprises wrote: > > Hi Centos friends. > > I had some time to

Hi Centos friends. I had some time to write a spartan tutorial on running the latest stable Jitsi Video Bridge and Jitsi Meet and Centos 7.7. I wrote it while testing it so this WORKS and I am currently using it for fun with the kids. I do have the server currently running but blocked by my firewall. I am willing to allow a few of the people such a Kovacs and others to connect to my Jitsi server

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>