similar to: ultra wide band packet questions

Hi, So I got a crash on the following code: k1=SUBMODE(lpc_enh_k1); k2=SUBMODE(lpc_enh_k2); which in the newer codebase is: bw_lpc(SUBMODE(lpc_enh_k1), st->interp_qlpc, awk1, st->lpcSize); bw_lpc(SUBMODE(lpc_enh_k2), st->interp_qlpc, awk2, st->lpcSize); I am not sure if the newer code will have the same issue but the following check is

Hi, Can someone please tell me how should I go about changing the frame size which is hardcoded to 160 for NB and WB and 320 for UWB. For NB speech(8KHz) the framesize of 160 is 20ms frame but for WB and UWB its 10ms. What are the parameters being affected by simply changing the framesize and sub-frame size in "modes.c" How to change the buffer size and how its affected. can we have a

Sir Can u kindly tell me what kind of coding does speex use in Ultra Wide Band ? And from where can I read the details of it ? Abhishek IIT - Madras, India. <p> ___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now

Hi, I am currently encoding 32 Khz/Qual-10/UWB encode mode, with MANUAL_ALLOC enabled ( similar to the c5x/c6x configuration). In file sb_celp.c, I noticed the scratch memory grow during recursive (UWB -> WB) calls to 'sb_encode'. 1. 'stack' was not tracked (with 'tmp_stack' as done at other palaces) after/before - auto-correlation/Levinson-Durbin scope (~line

Hello, To start with, thanks a lot for making such a great voice codec available! Having recently upgrading to speex rc1, It occurred to us that there seems to have been a regression in the quality of encoding since version beta1. We are compressing some 22khz wave files in wb mode with maximum quality / complexity in VBR, and the result was really great with speex beta1. With rc1 (or beta3),

> 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, One question that I hope someone on the list just knows the answer to without having to delve too deeply into the code: How does UWB mode divvy up the bandwidth and pack it in the bitstream? I know from the documentation that WB mode codes the first 0-4K kHz band as a Narrowband packet, and then adds on the 4-8 kHz band coded separately (so that a NB decoder can decode a WB bitstream

Hi list! There seem to be some oddities in using ABR. The first thing I notice is that because "abr_count" increases without bound, after a while the weight of the bitrate history will completely swamp any change in the current bitrate and the ABR adjustment will essentially stop happening. This seems to be true in any mode (not just UWB) and perhaps a solution is to cap

Hello, In the internet draft describing the SDP parameters for speex I find this: mode: Speex encoding mode. Can be {1,2,3,4,5,6,any} defaults to 3 in narrowband, 6 in wide and ultra-wide. In the documentation I can only find the following request: SPEEX_SET_MODE There is no description though what this request does. I think the mode somehow maps to the bitrate, but I

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

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

It looks like I'll need to go further into the guts of speex to do this. I do, however, see some lines in nb_celp.c/nb_decode() that look interesting. I guess I'll play with it. I doubt that it will be terribly clean, though. Jean-Marc: Take a look at line 1195 in nb_celp.c (CVS). It reads "speex_warning ("More than to wideband layers found: corrupted

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

re: At 03:22 PM 10/25/2005, Jean-Marc Valin wrote: >Are you really sure you didn't have some corruption elsewhere? Totally possible- this is the first time this has happened that I know of in many many hours of usage- On the other hand, this null check isn't in my code base and it was in nb_decode_lost, and nb_encode- so I figured it was just an oversight- Tom

Hi Jean-Marc, > Can you confirm I'm understanding everything correctly? You encode > with > the same encoder and then decode with either A) blackfin assembly and > fixed-point or B) fixed-point only on Blackfin. Then A) sounds bad and > B) sounds good. If you do the same in narrowband, it sounds OK. Is > that > correct? If that's the case, it's *probably* some

hello, i switched to use the encoder.processData() and encoder.getProcessedData() of jspeex. however it looks to me like a memory leak ... memory usage is increasing very fast and there is no visible stop ... after about five minutes java.lang.OutOfMemory occurs. I think it must be the jspeex component, because before i added jspeex to my app usage was constant at about 5mb. is it possible

Dear Jean-Marc: in Section Speex wideband mode (sub-band CELP), Subsection Bit allocation of the speex manual, you pointed out that the mode ID of wideband is 3 bits (it is consistent with the source code), however, in the following table (Table Quality versus bit-rate for the wideband encoder), there are 11 different modes (from 0 to 10). I am confused about this inconsistency, as 3 bits can

I am trying to join my Linux workstation to my ADS domain. Unfortunately, I'm not having much success. net ads join hangs forever (or at least for more than 12 hours) when run. The computer account is created in the domain, but the process never completes. tdbdump secrets.tdb shows no results, and wbinfo shows users and groups from the trusted domains but not from the domain I am trying to

hi, I have a small and quick question. When speex divide the UWB speech signal into High and low bands, JMV said to me in HA that : "For ultra-wideband (0-16 kHz, 32 kHz sampling), I first split the band into wideband (0-8 kHz) and "very high band" (8-16 kHz). Then, the wideband itself is split into low (0-4 kHz) and high (4-8 kHz) band. So there's a total of 3 bands

if the new draft in the manual is used. I don't find how to tell the decoder which mode(NB/WB/UWB) is used in the encoder. The RTP header don't contain the mode field and I don't find the mode information in the coded frame either. Does this mean we have to use NB decoder in all cases? Lianghu On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > >