similar to: 8.4kbps data rate in 8kbps nb mode

Indeed there was a bug in the speex_bits_insert_terminator() function. It's now fixed in svn. The only people this bug affected are the ones relying on detection of the end of packed Speex frames and some wasted bytes when using 8 kbps mode. Jean-Marc Le jeudi 17 novembre 2005 ? 23:18 +0000, Andrew White a ?crit : > Hi Jean-Marc, > > Thanks for your response. > > I wrote a

> As I can't compile for dos/windows I was relying on the 1.1.6 binaries from > the download area. If you don't feel like recompiling, just discard the last byte and don't rely on the terminator. > Just to let you know, I've been working on a port for the eCOG > microcontroller (www.cyantechnology.com). Cool. > I managed to get a decoder-only build by adding a

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

> Use speex_mode_query with SPEEX_SUBMODE_BITS_PER_FRAME > You need to pass the submode number with the pointer and the number of > bits per frame is returned using the same pointer. Note that with > speex_mode_query, the first argument is the mode (e.g. &speex_nb_mode), > not the encoder/decoder state. Thank you Jean-Marc, This works well. Now a followup question. Is there

I need to shrink speex so it will fit on an embedded processor along with some other code. The chip has only 20k of ram. I have done some work with libspeex.dsp by removing references to all modes but narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the structures for the other submodes and the functions that they called.

Hello, I do test runs of speex using speexenc -n [name].wav [name].spx The wav-files (6 different speech files) hereby are sampled at 44100Hz. Most interestingly, all Frames have SubModeID 5. I haven't tracked the Assignment of the SubModeID through the source code, so I just wanted to ask, if I can assume "speexenc -n" to use SubModeID 5 always? Ciao, Bj?rn -- You will

Hi, Jean-Marc Valin wrote: >> I haven't tracked the Assignment of the SubModeID through the source >> code, so I just wanted to ask, if I can assume "speexenc -n" to use >> SubModeID 5 always? > > Only if you never change the bit-rate. But speexenc -n was a dumb idea > in the first place... I know ... Thats why I downsampled the WAV-File to 8kHz (I got

I have successfully DECODED speex on TI C5509: #define TESTENC_BYTES_PER_FRAME 20 /* 8kbps */ #define TESTENC_QUALITY 4 /* 8kbps */ I am trying to generate the files I need with speexenc.exe: speexenc -n --quality 4 -V male.wav male.spx But I can't decode the files on C5x. Yes, I have seen that speexenc.exe adds Ogg header and

Hi Jean-Marc, will you include these optimizations for minimal ram usage in the main version? Maybe if Peter sends a Patch... Thanks, Alain Jean-Marc Valin escreveu: > Sounds like you did most of what you needed to do. Using a coverage > analysis tool might help you remove bits of code here and there (e.g. > unused _ctl() cases), but the main part is done. About the preprocessor,

On Tue, Feb 25, 2020 at 05:45:06PM +0200, Ville Syrj?l? wrote: > On Tue, Feb 25, 2020 at 04:19:27PM +0100, Andrzej Hajda wrote: > > On 25.02.2020 12:21, Ville Syrj?l? wrote: > > > On Mon, Feb 24, 2020 at 03:14:54PM +0100, Andrzej Hajda wrote: > > >> On 19.02.2020 21:35, Ville Syrjala wrote: > > >>> From: Ville Syrj?l? <ville.syrjala at

> For encoding into and decoding from "raw Speex stream" (if you can call > it that), I suggest you start with the sampleenc.c and sampledec.c > example code in Appendix B of the Speex Manual. There is no such a thing as a "raw Speex format". Also, sampleenc.c and sampledec.c are good for learning how to use the API, but the compressed format shouldn't be used in

Hello developers, I have a question about supported bitrates for SPEEX. Regardless of whether I specify a 10kbps or a 8kbps bitrate, the encoded .spx file is the same size and have the same PESQ value. This makes me wonder if SPEEX supports arbitrary bitrates, or only a certain set. A few more details about my configuration: I am using SPEEX encoder version 1.1.12 I am encoding a narrowband

On Tue, Feb 25, 2020 at 04:19:27PM +0100, Andrzej Hajda wrote: > On 25.02.2020 12:21, Ville Syrj?l? wrote: > > On Mon, Feb 24, 2020 at 03:14:54PM +0100, Andrzej Hajda wrote: > >> On 19.02.2020 21:35, Ville Syrjala wrote: > >>> From: Ville Syrj?l? <ville.syrjala at linux.intel.com> > >>> > >>> Get rid of mode->vrefresh and just

Hi all, I'm trying to use libspeex 1.1.10 on an ARM926EJ-Sid(wb) rev 3 (v5l). I executed the speexenc and speexdec test files and they can encode and decode. But I'm getting 95% of cpu utilization on the codification and 44% on the decodification. I saw in the post: http://lists.xiph.org/pipermail/speex-dev/2005-June/003485.html that this version of speex works fine on ARM

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

Hi, I tried the same options suggested in your post and the problem continues. What do you suggest? 2005/9/15, Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca>: > Hi Eduardo, > > All I can say is that the timings you have are a bit odd. What > optimizations options are you using (I suggest -O3)? Also, perhaps you > can try --enable-arm4-asm just in case. I've had the

Hi Jean-Marc, Hi Jim, I have also seen some problems with the 1.1.8 release on the C55x. So far I have boiled down the issues to the following: 1) We need our own "fixed_xx.h" header file. I don't know why, and haven't had time to investigate, but there is a definite improvement when I use the attached fixed_c55x.h file which has turned all the maths into inline functions.

> I had the idea of implementing a lot of the operations in FFTs. ( for > example, it is possible to do auto-correlation and FIR filtering using > FFTs.) There are two advantages to this. > 1. It's almost always faster > 2. By swapping fft implementations, it could be easy to recompile for > fixed or floating point versions. No. FFT's require higher precision than

Hello everyone, I'm finally beginning to use Speex for a project. As expected, the implementation so far has been very easy and I am thrilled with the capabilities and flexibility of Speex, especially the new features in 1.1. My efforts so far have resulted in a couple of questions: 1) I was interested in fetching the default quality setting for narrowband:

Hi, Is there any way to determine frame size in bits or bytes of encoded frame in WB mode for given quality? That is I need to know how many bits encoded frame will occupy in RTP packet. I see SPEEX_SUBMODE_BITS_PER_FRAME request, but it works like this only for NB mode, and for WB mode it return size of WB "subframe" (?) only. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM