search for: uwb

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 by just ignoring the second band; rather...

...BR. 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 "abr_count" at some value. The other thing is that the ABR calculations are only done for the highest submode, and in UWB that is a problem in that the ABR code adjusts the bitrate by changing that submode's quality. This really doesn't work...

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 variable frame size implementati...

...rc and List, So I have started finally fiddling around with Ultra-wideband mode. It appears to be very similar in operation to Wide mode, except that when peering into the packet structure it looks like (and these are kind of questions as much as statements here): 1. update rate 0 is not used in UWB- only 1-4? 2. The total bits used for each UWB update rate seem to be as follows: 0:36 bits (a guess) 1:72 bits 2:148 bits 3:224 bits 4:384 bits I found one case where these numbers didn't work (for update rate 1), where it appeared to be maybe 68 bits instead of 72- is this a variable number...

...lising global parameters [2004/05/20 10:08:46, 3] param/params.c:pm_process(566) params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" [2004/05/20 10:08:46, 3] param/loadparm.c:do_section(3384) Processing section "[global]" doing parameter workgroup = UWB doing parameter server string = Samba 3.0.3 doing parameter printcap name = CUPS doing parameter load printers = yes doing parameter printing = cups doing parameter log file = /var/log/samba/%m.log doing parameter max log size = 50 doing parameter security = ads doing parameter user...

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 the >> SPEEX_GET_LOOKAHEAD cont...

Hello I just wrote a little application using speex. I am compressing and packing singel frames to transmit them. Now I read in the manual, that it's possible to achieve higher bit rates by packing more than one frames at once. Unfortunately there is no table included at the manual, that shows the "real" bitrates of ultra wide band mode. So my question is: Can someone provide that

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

...> >> I want to do a careful measure of mic-to-net and net-to-spkr delays >> in sip media engine and to make it really precise I need to know >> delays, introduced by Speex algorithms. In particular, I'm interested >> in delays of: >> 1) encoder in NB, WB and UWB modes, >> > > NB: 25 ms, WB: ~28 ms, UWB: ~30 ms > > >> 2) decoder (I guess it should be 0?) >> > > 5 ms > > >> 3) resampler. I think it varies depending on input rate to output rate >> ratio. Any generic formula or at least valu...

...rames, 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 tested it with testenc in NB, WB and UWB modes with VBR enabled > to test in as many cases as possible. It seems to work fine. > Though, while testing I discovered possible bug - original version > of wb_skip_table[] (nb_celp.c:1081) does not seem to be correct. > Element 0 should be 4 instead of 0 and last four elements shoul...

...l. Anyway, it's now fixed in CVS (both trunk and 1.0.x branch). Thanks for the bug report. Jean-Marc Le mar 03/06/2003 à 01:16, Christian Buchner a écrit : > Hi there. > > I am having a little trouble understanding the frame sizes chosen > by the codec. > > testenc_uwb.c from the speex-1.0 source distribution has a framesize > of 640 hardcoded and makes use of this value exclusively. > > However, a mode query on the actual codec returns 320 as a framesize > for this mode. > > int tmp; > speex_mode_query(&speex_uwb_mode, SPEEX_MODE...

> Oops... You've just found a bug. Seems like you're the first one to use > that call. Anyway, it's now fixed in CVS (both trunk and 1.0.x branch). > Thanks for the bug report. Hmm, the call to speex_encode_stereo() takes the frame size as an an argument - and this call generates bits ;) So possibly my bitrate table shows wrong values in the stereo cases. Hmm... Where would

...case I broke something in svn). I rechecked the issue with the following combinations with the 1.1.11- svn version: NB-Mode (8kHz): Complexity = 1, Quality = 1, 5, 9 Complexity = 5, Quality = 1, 5, 9 Complexity = 9, Quality = 1, 5, 9 I also checked the above combinations for the WB (16 KHz) and UWB- Mode (32kHz). And I checked everything with 1.1.10 version, too, as you suggested. I checked by encoding+decoding a test speech sample for each mode with fixed+blackfin optimizations and by comparing the resulting file to the fixed-only-optimized encoded+decoded version of the speech sam...

Le mercredi 10 mai 2006 ? 10:17 +0100, devilal sharma a ?crit : > 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. Sorry, you got your calculations wrong, it's 20 ms regardless of the modes. > What are the parameters being affected by simply changing the > framesize and sub-frame size in "modes.c&quo...

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

...egradation for fricatives, which gives a very audible (and annoying) feeling of a muffled voice. This problem does not seem to affect CBR encoding, only VBR. It does not appear to affect 16k files as much either. Hope that will help you improve speex again! Blaise P.S.: Is there any plan to make uwb mode really usable? At the moment, compressed 32k wave files sound worse than 16k in maximum quality. Would it be a lot of work to make the bitrate of the upper band to depend on the quality setting, instead of being hard-coded at 1.8kb?

...as narrowband does. dev Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> wrote: Le mercredi 10 mai 2006 ? 10:17 +0100, devilal sharma a ?crit : > 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. Sorry, you got your calculations wrong, it's 20 ms regardless of the modes. > What are the parameters being affected by simply changing the > framesize and sub-frame size in "modes.c&quo...

...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 >> wb: nb+sb >> uwb: nb+sb+sb > > Hum... Then SPEEX_SUBMODE_BITS_PER_FRAME macro have > wrong name. Well, I haven't quite defined whether a frame includes all "layers" or just one... > This is what I was trying to ask in my previous mail. > Now it return number of bits in one layer (nb...

Hi there. I am having a little trouble understanding the frame sizes chosen by the codec. testenc_uwb.c from the speex-1.0 source distribution has a framesize of 640 hardcoded and makes use of this value exclusively. However, a mode query on the actual codec returns 320 as a framesize for this mode. int tmp; speex_mode_query(&speex_uwb_mode, SPEEX_MODE_FRAME_SIZE, &tmp); <p>t...

...and, 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 cannot find a table that tells me which mode maps to which bitrate for nb, wb and uwb codecs. And what does it mean when mode=any? Can someone explain me what the mode indicates? Best regards, Michel -- Michel de Boer www.twinklephone.com