similar to: opus-tools resampler

How much latency are we talking about? It seems that this issue cannot be easily pinpointed, but if it turns out to be related to the Speex Resampler let me know and I will put it on my task list. - Sherief -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Colin Guthrie Sent: Monday, December 06, 2010 9:47 AM To: speex-dev at

If you can produce a simple minimal repro that exhibits this issue on some procedural signal (sine wave, etc) I'd love to look into it some more - I'm maintaining a hardened version of the Speex Resampler and would be very concerned if this bug made it into production. - Sherief -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On

From: Sherief Farouk [mailto:sherief.farouk at twisted-works.com] Sent: Tuesday, November 03, 2009 5:34 PM To: 'speex-dev at xiph.org' Subject: Handling allocation failure in resampler init - patch Hi, Here's a patch that stops allocation failures during resampler init from segfaulting, now they fail gracefully and report the error through the error code parameter

Colin, If you're using stereo audio with the resampler, there is a bug that can occur under certain situations (and maybe that's what's been happening to you). Check out: http://lists.xiph.org/pipermail/speex-dev/2009-August/007406.html With that patch, I've used the resampler extensively in many situations without any problems. John Ridges On 12/3/2010 1:00 PM,

Hi, I just built a sample application with speex resampler in linux and I tried to resample 8K sine wave tone mono to 48k using speex_resample_process_int. I am using a tool called EAQUAL for audio quality. I find the quality of Speex resampler to be decreasing when I increase the quality q of the resampler init function. Can some one give me pointers regarding this?? As per the API, if the

Hi, *"That's in general not very reliable. You can get PEAQ to say all sorts of silly things." Can you provide me links for any more effective tools other than PEAQ? Which is more reliable for Speex resampler? * *"strongly suspect that it's just not compensating for the delay introduced by the resampler. Because higher quality means higher delay, you'd find that PEAQ

'Twas brillig, and Sherief N. Farouk at 06/12/10 14:29 did gyre and gimble: > If you can produce a simple minimal repro that exhibits this issue on some > procedural signal (sine wave, etc) I'd love to look into it some more - I'm > maintaining a hardened version of the Speex Resampler and would be very > concerned if this bug made it into production. Well at present,

Alexander Chemeris wrote: > Hi, > > Here are some questions from user point of view. :) > > On 5/29/08, Thorvald Natvig <thorvald at natvig.com> wrote: > >> I've done listening tests when converting wb_male.wav to 44.1, 48 and 8khz, >> and there aren't any obvious artifacts. I also did a 16=>16 test, and the >> results are delayed by 10ms

Attached is a snapshot of work-in-progress of a FFT based resampler. At the moment it works in floating point only, and only basic quality inspection has been done. Some benchmarks comparing the filter-based resampler at Q3 with the FFT resampler with overlap = in_len / 2, using 20ms chunks of data. (-O3 -ffast-math, FFTW3, gcc 4.3.0 on x86_64) 16=>48: 59us vs 19us 16=>44.1: 204us vs

Hi, I just started to examine the DIV32_16 function (Blackfin ASM version), and wondered why the return value of the function inside 'fixed_bfin.h' is of type 'spx_word16_t', but the local variable 'res' which is returned by this function is of type 'spx_word32_t'. Is this a trick of optimization or a bug? (Same question for PDIV32_16 and MAX16, too!) best

Hi, I tried to figure out what the problem is -- but it seems to be totally different from what I expected. My status at the moment is: - computing results for "generic" and "Blackfin ASM" versions of the DIV32_16 function are the same, there is no "algorithmic bug" - Instead, there seems some sort of memory corruption: When I comment out the DIV32_16 function

Hi Jean-Marc, Thanks for taking a look. I've added an example program in the patches that changes the rate frequently. You can run test-resample2 >test.raw and open in audacity or so to look at the spectrum etc. I've attached a before/after screenshot. In theory, depending on the current phase and the rate changes that are applied, the error can be audible as a pop when changing

Hi all, I have a couple of questions about the speex resampler: 1. Can a resampler state be used to process frames belonging to several audio streams? I would guess that there is information about the audio streams stored in the state so the answer is no, but it would be good to have some confirmation. 2. What is the best way to reset a resampler state? speex_resampler_reset_mem appears

Dear Nikos, thank you very much for your advice! I am not a little bit new to C++, and experiments (like using another third party library) always turn out to be days of work for me. That is why I would first like to try Speex's new internal resampling function. I am currently still using the old 1.0.4 version. I have now downloaded the new 1.2rc1 version. Unfortunately it does not want

Dear Nikos, thanks! But you use Opus only for resampling, not for entirely replacing Speex, don't you? Greetings! Hermie Am 07.05.2013 22:53, schrieb Nikos Chantziaras: > The Opus resampler is actually a bugfixed version of the Speex one. Same > interface/API, but with the bugs removed. It's why I recommended it :-) > Otherwise I would have recommended something entirely

Ok. I did some quality tests. First off; never do quality tests with ints. I had serious problems interpreting my results until it dawned on me that the signal differences were just 0 or 1. So, after a lot of scratching my head, these are done comparing the result from the _float versions (which is how both resamplers work internally anyway). What I did was this: Load speex_wb.wav as one

Hi Jean-Marc, didn't get a reply to my last post (see below) -- do you have no idea what happens here? After some more tests, I disabled the DIV32_16 Blackfin optimizations and now get good quality on the Blackfin. But when I have overdrive on the input, things become very bad -- I'm not sure if this is really a filter stability issue like I wrote some weeks ago. I use the speex

Hi, Here's an updated resampler patch against current SVN. It includes SSE and SSE2 optimizations (the latter if included by _USE_SSE2). Best regards, Thorvald -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: speex-resampler-update.diff Url: http://lists.xiph.org/pipermail/speex-dev/attachments/20080426/e055077f/attachment-0001.txt

Hi, These patches improve the resampler set_rate function. The first 2 patches do some cleanups in the GCD calculation and avoid an overflow when calculating the new phase. This patch could probably be simplified if we allowed 64bits operations in speexdsp. The 3rd patch avoid rounding errors in the phase calculation. The problem is that the new rate is calculated with the reduced rate, which

First of all, bufout_len = 320 is correct since that value is the number of stereo samples. Using 640 would be wrong (and no wonder that it crashes). Secondly, "speex_resampler_process_interleaved_float" has a bug that keeps it from working when it is output limited, so if you ever set "buf_len" to any value greater than 1764 the resampler will stop functioning properly