similar to: Re: Forward of moderated message

I'm finally picking my dovecot project back up now, and after upgrading rc19 to rc27, I sent a test message to an existing account which resulted in log entries like these: Mar 16 08:45:37 node7 deliver(user at example.com): Corrupted transaction log file /var/indexes/example/com/u/us/user/.INBOX/dovecot.index.log: Append with UID 3, but next_uid = 15368 Mar 16 08:45:37 node7

hi kuhlen, what you said is correct. i am talking about how you are going to arrange these codewords into an array, i.e. in the function _make_decode_table. there he uses node bytes and leaf words for memory management. i got a 24 bit platform. so if i assume that max. codeword length that could be possible as 24 bits can i allocate a memory of (2 * used entries - 2), to arrange the whole tree in

On Sun, 2010-01-31 at 13:28 +1100, Lang Hames wrote: > Hi Sebastian, > > It boils down to this: The previous heuristic solver could return > infinite cost solutions in some rare cases (despite finite-cost > solutions existing). The new solver is still heuristic, but it should > always return a finite cost solution if one exists. It does this by > avoiding early reduction of

Hi Sebastian, It boils down to this: The previous heuristic solver could return infinite cost solutions in some rare cases (despite finite-cost solutions existing). The new solver is still heuristic, but it should always return a finite cost solution if one exists. It does this by avoiding early reduction of infinite spill cost nodes via R1 or R2. To illustrate why the early reductions can be a

BTW, in checking the -ansi stuff, I noticed the following warning: testecho.c: In function `main': testecho.c:40: warning: passing argument 5 of `speex_echo_cancel' from incompatible pointer type Looks like you forgot to update this after changing the working array type. Just-guessing patch attached. -r -------------- next part -------------- Index: libspeex/testecho.c

Are you sure you're not just inverting the two inputs? Jean-Marc On Wed, 2005-11-09 at 22:16 -0800, Jason Harper wrote: > I ran some further tests on mdf and here are the > results: > 1. reduced tail length to 100ms, aligned mic and > speaker signals to within 10ms - almost no echo > attenuation > 2. aligned mic and speaker signals to within 5 samples > - still almost

This kind of behaviour is odd. One of the reason could be the fact that you're using a really long impulse response. Try syncing your signals and making the tail length more in the order of 100 ms to 300 ms. Jean-Marc Le dimanche 06 novembre 2005 ? 21:25 -0800, Jason Harper a ?crit : > Thanks for alerting me to the new changes. I just > tried the latest code from SVN, but

On Mon, Aug 11, 2008 at 12:34 PM, Jean-Marc Valin < jean-marc.valin at usherbrooke.ca> wrote: > OK, here's what happens. There is indeed a small difference between > beta3 and rc1, but the fundamental problem isn't there. I've attached > plots of the speaker signal (blue) alongside the mic signal (green). You > can see the delay is in the order of 1000 samples.

I'm pretty much sure of it. When I test inverting the inputs, my output is pretty much the same as my speaker signal. Whereas the way that I normally test the output is my mic signal with very little attenuation. If you are interested I can send my test files; they are about 94KB each. -Jason --- Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > Are you sure you're

Thanks for alerting me to the new changes. I just tried the latest code from SVN, but unfortunately I still have just about the same results. The estimated echo that gets subtracted from the actual echo is such a small signal that it doesn't really result in any noticeable echo attenuation. I currently have my filter size set to 2 seconds even though the echo in my microphone file is only

I ran some further tests on mdf and here are the results: 1. reduced tail length to 100ms, aligned mic and speaker signals to within 10ms - almost no echo attenuation 2. aligned mic and speaker signals to within 5 samples - still almost no echo attenuation 3. ran testecho using the same file for mic and speaker - very good echo cancellation (of course this is expected, but I needed to do a sanity

I've tried some further debugging to see what mdf is actually doing. Instead of sending: tmp_out = (float)ref[i] - st->y[i+st->frame_size] to the output, I just sent st->y[i+st->frame_size] to see what was being subtracted from the microphone input. When I open this in Audacity, I see a very small signal at about -40dBm. The actual echo in my sample has a power closer to -20dBm.

I've recently made changes to the AEC. Please try the code in SVN and see if it works better. Jean-Marc Le jeudi 03 novembre 2005 ? 22:36 -0800, Jason Harper a ?crit : > I've tried some further debugging to see what mdf is > actually doing. Instead of sending: > tmp_out = (float)ref[i] - st->y[i+st->frame_size] > to the output, I just sent >

On Sat, Aug 9, 2008 at 12:59 PM, Jean-Marc Valin < jean-marc.valin at usherbrooke.ca> wrote: > Hi Benny, > > Can you send me your pair of testecho input files that work well with > beta3 and not with rc1? I'll have a look. > > Thanks for the help. The files are on their way now, the upload will take few more minutes to complete. In the mean time let me explain more

OK, here's what happens. There is indeed a small difference between beta3 and rc1, but the fundamental problem isn't there. I've attached plots of the speaker signal (blue) alongside the mic signal (green). You can see the delay is in the order of 1000 samples. That's way too much to do anything useful because the tail doesn't even "see" the echo. You need to reduce

I have my login log format set like so: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c When I log in using a full email address, though, I only get the username part of the address: Jan 24 13:28:29 node7 dovecot: pop3-login: Login: user=<justin>, method=PLAIN, rip=137.118.2.60, lip=137.118.7.247 Jan 24 13:28:30 node7 dovecot: POP3(justin): Disconnected: Logged

Dear gluster experts, We have encountered a severe performance issue related to quota feature of gluster. My underlying fs is lvm with xfs format. The problem is if quota is enabled the io performance is about 26MB/s but with quota disabled the io performance is 216MB/s. Any one known what's the problem? BTW I have reproduce it several times and it is related to quota indeed. Here's the

When I ran test 4 as originally described there is substantial echo cancellation (but not as good as when the files are perfectly aligned). When I invert the inputs, there is no noticeable cancellation. I'm using testecho with the preprocess line commented out. Preprocess seems to work very well at cleaning up the residual echo when mdf does its job, so I'm just focusing on testing mdf.

Hi all, I'm currently testing out the speex echo canceller to determine if it is suitable for use in a client's product. I have a few questions regarding problems that I'm having and I would appreciate it if anyone could help me out. 1. I provide to .wav files as arguments to testecho and the output generated always seems to be 44100 Hz even though the sampling rate in

Greetings everyone, I was about to compare AEC performance between 1.1.12 and 1.2beta1 when I noticed something. If I configure (and compile) speex-1.1.12 with ./configure --enable-shared=no --enable-static=yes it compiles and works as expected: I can run a mic and speaker signal through testecho, it runs in a reasonable amount of time (about 23 secs for 3 minutes of audio) and I get back