similar to: Getting SING errors

Hi Jean-Marc, I used the following code after init of the encoder to get the frame size of my RTP packets. char pcm_data[3200]; char speex_data[3200]; SpeexBits bits; memset(pcm_data, '\0', 3200); memset(speex_data, '\0', 3200); speex_bits_init(&bits); speex_bits_reset(&bits); speex_encode_int(codec_info->enc,

This was reported by me (and most likely others). Here is the exchange about this. The reason the problem is visible in Delphi is that Borland (C++ and Delphi) initialize the FPU differently from other RTLs. Also, there is another problem that will be visible with Delphi --------------------------------------------------------- ------------- Yes, that's definitely a bug in the vbr code,

Dear R-ers, While browsing the R sources, I found the following piece of code in src\main\memory.c: static void reset_pp_stack(void *data) { R_size_t *poldpps = data; R_PPStackSize = *poldpps; } To me, it looks like the poldpps pointer is a nuissance; can't you just cast the data pointer and derefer it at once? Say, static void reset_pp_stack(void *data) { R_PPStackSize = *

I have been searching for the R manual, unable to solve my problem. Questions 1) How can I put the x axis at the top of the plot? 2) I am plotting data from a CTD. I want to add series sal, obs and fluo at the same plot by using points(sal,deepth) ets. The data have different values so I want to use multiple x axis (4) with different scaling. How can I do that?

I am using the Deepayan's Sweave trick to set graphics parameters for all graphs: ltheme = canonical.theme(color=TRUE) sup = trellis.par.get("superpose.line") ltheme$superpose.line$col = c('black',"red","blue","#e31111","green", "gray") .... Works perfectly, there is only a minor nuissance that trellis.par.get opens a device

Hi, I am using speex 1.2beta2 on a narrowband 16-bit, 8khz system that has a severe program space problem and will not fit speex in its normal operation. In an attempt to shrink speex I placed a breakpoint in every function and ran a decode and encode and removed the breakpoints that I hit. in the functions that had a breakpoint that I didn't hit I commented out those functions (as well as

Hi Jean Marc & List, So I have been fiddling with the denoiser (again). While poking around I noticed that nb_preprocess is basically a counter that is mod-ded with 100 (the default), which causes Smin[] to be re- seeded with the value in Stmp[] (min of the previous adaptation period). Smin[] is then used to update the noise probability, which is (probably) less likely when adaptation

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

for the bits init I am using speex_bits_set_bit_buffer and I don't use the write to or read from because the data is already in the buffer I am reading from and I am writing to the final buffer so I don't need to move arrays around. what part is the vocoder part of the decode? Thanks for your help! -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/06/07

I'm glad to hear that my data size can be shrunk considerably, however I do not know the minimum values that I would set the static arrays to be. I hate to be a bother but could you tell me the minimum values for these arrays/structures in the state structure? Thanks! encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch

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.

hi, i am trying to compile a fixed point version of lipspeex on desktop windows environment. a short reason for the complicated story is that we need to keep the 'engine' part of our project same across the various ports of our voip project (blame the pointy haired boss). now, when i compile with FIXED_POINT defined in the Visual C++ 6.0, i get these errors:

But that's what a jitter buffer will do, eventually - drop a packet. And it's better to drop a silence packet. Cheers, .a -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Wednesday, December 21, 2005 3:39 PM To: Alex Bakaev Cc: Shantanu Gramsci; speex-dev@xiph.org Subject: RE: [Speex-dev] Bitrate problem On Wed, 2005-12-21 at 15:29 -0800,

I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem

Hi Tom, Of course the current tuning of the denoise is approximative and could probably be improved... That being said, the modulo 100 isn't the adaptation time itself, but rather the window over which to look for minima. The main idea is this: if the power in a certain bin isn't too much higher than the minimal value for a certain window, then we can adapt the noise estimate. The

Hi! It seems that using a different compiler (I assume the development is done with MSC) uncovers various issues with the floating point. Here is the second one I'm seeing - DOMAIN error from sqrt(). In the open_loop_nbest_pitch(), this line: g = DIV32(corr[i-start], 10+SHR32(MULT16_16(spx_sqrt(e0),spx_sqrt(energy[i-start]) ),6)); The values are: e0 is 7.2 i is 142, start is 17

Hi, I have done a search on this in vain. How can I add a note to the foot of a graph example below |-----------------------| | Title | | -------- | | | my | | | | graph | | | | | | | | ______| | |note: source | |-----------------------| Many thanks Ronnie

-----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Thorvald Natvig Sent: Monday, March 20, 2006 12:11 PM To: speex-dev@xiph.org Subject: Re: [Speex-dev] Who is using the jitter buffer? But I must say that it really does work well at the moment, at least from the "minimizing latency" point of view :) How do you timestamp the

> how about tcp? > in tcp you write a packet that got a possible length. > you send one packet after another, whitch stamp is incrementet by one > and if your incoming packet is gone in other steps than 1, the client has > to resend it. > Let me think some days about it and i will get another system. > Time is relative. > > Hm, you send a packet that needs to be in a