similar to: Delays estimation in Speex algorithms

First patch fixes two typos in manual. Second patch adds few notes about latency, as promised. Hopefully I haven't added any typos and grammar errors :) On Wed, Jul 1, 2009 at 8:02 PM, Alexander Chemeris<Alexander.Chemeris at sipez.com> wrote: > Thank you for clarification. I attached a patch which (IMHO) > makes it more clear for everyone who just read Doxygen > docs.

JM, I also need to know the precise delays from Speex but I used the SPEEX_GET_LOOKAHEAD control requests to determine them (plus the "speex_resampler_get_output_latency" function from the resampler). The returned values from the Speex lookahead request don't seem to match with the values you gave Alexander. Am I doing this wrong? Thanks, John Ridges speex-dev-request at

Speex tells me that the decoder is always 5 ms, but it says that the encoder is 5 ms for NB, 8.9375 ms for WB, and 10.90625 ms for UWB. Is there an extra frame of delay in the encoder that isn't otherwise accounted for? John Ridges Jean-Marc Valin wrote: > Quoting John Ridges <jridges at masque.com>: > >> I also need to know the precise delays from Speex but I used

Thank you for clarification. I attached a patch which (IMHO) makes it more clear for everyone who just read Doxygen docs. Resampler latency docs wording was just ambiguous IMO, so I made it more robust to fast reading. On Wed, Jul 1, 2009 at 5:16 PM, Jean-Marc Valin<jean-marc.valin at usherbrooke.ca> wrote: > Alexander Chemeris a ?crit : >> On Tue, Jun 30, 2009 at 4:38 AM,

----- Original Message ----- From: "Alexander Chemeris" <Alexander.Chemeris at sipez.com> To: "Vincent Burel" <vincent.burel at vb-audio.com> Cc: "Conrad Parker" <conrad at metadecks.org>; <speex-dev at xiph.org>; "Jean-Marc Valin" <jean-marc.valin at usherbrooke.ca> Sent: Thursday, November 13, 2008 11:31 PM Subject: Re:

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

Quoting John Ridges <jridges at masque.com>: > Speex tells me that the decoder is always 5 ms, but it says that the > encoder is 5 ms for NB, 8.9375 ms for WB, and 10.90625 ms for UWB. Is > there an extra frame of delay in the encoder that isn't otherwise > accounted for? Oh, delay = frame_size + lookahead If you have a frame size of 20 ms, then there's no choice but

> Oh, you're right, inband handling is different, but it's a matter of one > flag, passed to functioin. Probably not that much to keep code DRY. Well, let's first merge your code and then we'll see about possible simplifications. >> frame: 20 ms encoding >> sub-frame: 5 ms encoding (internal) >> layer: one frame of nb or sb >> sb: sub-band >>

Quoting John Ridges <jridges at masque.com>: > I also need to know the precise delays from Speex but I used the > SPEEX_GET_LOOKAHEAD control requests to determine them (plus the > "speex_resampler_get_output_latency" function from the resampler). The > returned values from the Speex lookahead request don't seem to match > with the values you gave Alexander. Am I

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

> Ok, here is cleaned up and fixed version. > > * Function is named speex_get_num_frames() now and return > number of frames, as you suggested. > * WB layers sizes are taken from wb_skip_table[], while NB frame > sizes are calculated with speex_mode_query(). Looking better. Just make sure to remove the stuff that isn't C99-compatible (e.g. // comments). > I've

Hi all, I am a newbie here and just started using speex in our lab. During compiling my voice application with windows-compiled version provided today, I am getting "unresolved external symbol _speex_wb_mode". I am probably missing some setting with VS6.0 linker... (I am a bit new to windows too) If anyone could point it out, I would appreciate it. - Tim -----Original Message-----

Hi Alexander, > Here is first attempt. I'm sending it here for review - am I understand > you correctly? If general approach is correct, I'll change code to use > modes from modes.c. I haven't tested, but it looks sane. Just a few comments: - printf("\tERROR not enough bits left after wb\n"); this is actually now an error. It just means you got to the end of the

Hi, Thanks! can this program generate speex.lib instead of libspeex.lib?? the OpenSpeak link to speex.lib instead of libspeex.lib I can compiled the libspeex.lib but not speex.lib. Correct me if I am wrong Thanks ----- Original Message ----- From: "Alexander Chemeris" <ipse.sipx@gmail.com> To: <alex@gorex.com.hk> Cc: <speex-dev@xiph.org> Sent: Tuesday, May 29,

On 11/28/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > I think the amount of Windows crap is getting a bit ridiculous. Does > anyone know of a solution to keep things manageable? I mean, the same > autotools files manage the build for Linux PCs, Blackfins and MacOS (and > others). Yet, we need one set of files for each MS compiler version > (good thing they

Hi, I would like to know where i can find some info about the speex header format, if there's any. I've seen ogg header format, but as i understand, ogg is used for encapsulating speex in audio files. I want to know if there's any speex header for example when i send speex data on rtp payload. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have a video conference like application that I've been working on for a while now, and a recent change is causing some odd problems, and I was wondering if anyone else had seen problems like this. The issue I'm seeing is that when using the sound card for capture, the audio will eventually get about 1-2 seconds out of synch (delayed), from the video. However, if I use USB devices

>> Oh, your table looked fine. I think it's mine that was wrong for the >> "null mode" (which nobody ever uses I guess!). > > I'm not sure, but I guess it may be used in VBR or DTX mode? > At least that's why I kept it. Of course it *can* be used (and needs fixing). It just seems few people did :-) > So, what's the next step towards

On 02/04/2008, Alexander Chemeris <Alexander.Chemeris at sipez.com> wrote: > On 4/1/08, Keith Kyzivat <kkyzivat at sipez.com> wrote: > > IIRC, under ARM, I believe I was having issues with --without-libogg. > > I resorted to just downloading libogg sources, setting up my > > cross-compilation environment, and cross compiling it per the general build > >

On 12/13/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > I am a newbie here and just started using speex in our lab. > > During compiling my voice application with windows-compiled version provided > > today, I am getting "unresolved external symbol _speex_wb_mode". > > I am probably missing some setting with VS6.0 linker... (I am a bit new