search for: speexdsp

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

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

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 case before the package split. > I made a patch for alsa-plugins, so that > it...

...oked 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 quality is important, using 44.1/16 stereo. Inserting AEC into the audio chain, it would be similar to: Java (raw audio bits) --> speexdsp AEC --> java --> ffmpeg --> server My questions: 1) Is this po...

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 more platforms planned for later). It follows the philosophy of doing things ri...

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

...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 "http://git.xiph.org/?p=speexdsp.git;a=summary" "http://speex.org/roadmap" maybe just delete it? > splitting the resampler into its own lib, however it's not clear > if it would really be worth it. well ... so split off SpeexDSP docs at least...

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

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

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

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

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 preprocess.lo CC jitter.lo CC mdf.lo CC f...

...of low cost ArmSocs now all approx. Pi3 level and above that really benefit from neon support with FFT. Arm have specific Libs for this https://projectne10.github.io/Ne10/doc/modules.html But since Version 3.3.1 FFTW http://www.fftw.org/ is supported Neon. Probably the biggest applicable use of speexdsp is going to be excluded when many opt for 64bit. Stuart Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/speex-dev/attachments/20200522/04cbb1e7/...

...e test and ran it via adb. Anyone able to help with review/integration? There are 4 functions in resample_neon.h thats just the first/easiest. On Sat, Mar 28, 2015 at 11:28 AM, Evan JIANG <firstfan at gmail.com> wrote: > 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...

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

This patch updates the symbian build files to latest svn trunk, and also adds a new makefile for speexdsp. Signed-off-by: Alfred E. Heggestad <aeh@db.org> --- Index: symbian/speexdsp.mmp =================================================================== --- symbian/speexdsp.mmp (revision 0) +++ symbian/speexdsp.mmp (revision 0) @@ -0,0 +1,42 @@ +/* + Copyright (C) 2003 Commonwealth Scientifi...

...re be a release? Maybe the page should document the Speex codec is deprecated but "Speex DSP" is not? Maybe "Speex DSP" could have a better "home" than in "shadow" of the dead Speex codec? - documentation of "Speex DSP" ... the latest release "speexdsp-1.2rc3.tar.gz" from 2015 still contains "The Speex Codec Manual Version 1.2 Beta 3" from 2007 ... it documents the codec part, not the DSP part ... maybe the documentation should be updated and split off too? - file "resample.c" - - note "This resampler is relatively...

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 /usr/lib/arm-linux-gnueabihf/alsa-lib/libasound_module_pcm_speex.so ((null): /usr/lib/arm-linux-gnueabihf/alsa-lib...

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

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