similar to: [PATCH] Make Queue announcements more consistent (1.4.26.2)

This is the core trace (gdb) bt #0 0xb7e5a231 in strcasecmp () from /lib/libc.so.6 #1 0xb7ce0a3f in local_ast_moh_start (chan=0x82496a8, mclass=0xb720f828 "default", interpclass=0x0) at res_musiconhold.c:646 #2 0x08083695 in ast_moh_start (chan=0x64, mclass=0x64 <Address 0x64 out of bounds>, interpclass=0x88 <Address 0x88 out of bounds>) at channel.c:4614 #3

On Mon, Jan 24, 2005 at 06:31:21PM -0800, Josh Coalson wrote: > yes, a mere 2 years later it is checked in! > > speed improvement for me is roughly 17% testing flac files on > linux-i386. Thanks! In case you would like to check another old patch, I have attached updated patch for seekable stream decoder, originally posted on 09/07/2003. -- Miroslav Lichvar -------------- next

When I was trying to find yesterday's xmms-plugin bug, i have noticed that seeking in stream without seek-table isn't very good. With attached patch it is much better. -- Miroslav Lichvar -------------- next part -------------- --- src/libFLAC/seekable_stream_decoder.c.orig 2003-02-26 19:41:51.000000000 +0100 +++ src/libFLAC/seekable_stream_decoder.c 2003-07-09 23:49:35.000000000 +0200

Ok, the patch from 2003 about improving seeking still didn't make it to CVS, so here is another try. I made some benchmarking with the test_seeking utility from flac sources to show how bad the current seeking is, especially without seektable. Track used for the experiment had about 50 minutes. In the following table is average number of seeks and number of decoded frames required for one

On Mon, Oct 30, 2006 at 11:13:25AM -0800, Josh Coalson wrote: > my apologies for not doing this before Miroslav... I will definitely > integrate it this time. Thanks. Sending latest version of the patch. Now it can seek in files that have large id3 tag (or any random data) at the end and it won't loop on streams with shuffled frames. -- Miroslav Lichvar -------------- next part

This is a small patch to progressmeter.c that provides peak throughput information. It adds a new field on the progress bar line that displays the 1sec throughput for the connection. At the end of the transfer it spits out the peak throughput seen. I found it useful in some testing situations and maybe someone else might find it handy. --- ../openssh-4.7p1.logging_features/progressmeter.c

I noticed that if the free space cache has an error writing out it''s data it won''t actually error out, it will just carry on. This is because it doesn''t check the return value of btrfs_wait_ordered_range, which didn''t actually return anything. So fix this in order to keep us from making free space cache look valid when it really isnt. Thanks, Signed-off-by:

I am running stable 1.07. I have tweaked the queue app a little, so I'd like verification from someone running stock... When the queue tries to announce the position, I go ahead and read the options for the escape context, which are in the queues.conf as the thank-you. However, pressing any key during the announcement is ineffective. As soon as the announcement is over, I can press the

A friend and I have recently added the ability to announce the callers position in the call queue every x seconds.. or even just inject an anouncement every x seconds. All setup in queues.conf and can be setup per queue. My next project is to add the ability to announce the callers estimated wait time. I want some feedback to see whats the best method to calculate that? What do you want just

The Asterisk Development Team has announced the release of Asterisk 1.2.35, 1.4.26.2, 1.6.0.15, and 1.6.1.6. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ These releases have been created in response to an IAX2 denial of service vulnerability. For more information about the details of this vulnerability, please read the security

The Asterisk Development Team has announced the release of Asterisk 1.2.35, 1.4.26.2, 1.6.0.15, and 1.6.1.6. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ These releases have been created in response to an IAX2 denial of service vulnerability. For more information about the details of this vulnerability, please read the security

> On Mon, Feb 8, 2010 at 2:20 AM, Olle E. Johansson <oej at edvina.net > wrote: >> >> 7 feb 2010 kl. 15.09 skrev Per Jessen: >> >>> Thomas Winter wrote: >>> >>>> Hi, >>>> >>>> my Asterisk on debian lenny died after 80 days. >>>> >>>> server kernel: [7572666.186852] asterisk[3673]:

Hi, I have a case where SIP channels will not be destroyed, resulting in further calls to ChanIsAvail() to fail. The process (I believe) to replicate this is the following: - Make a call to another SIP phone that is an "intercom" call (Auto-Answer) - For whatever reason, the phone happens to go UNREACHABLE during this call - Phone comes back REACHABLE, but channel still exists in

Hi, my Asterisk on debian lenny died after 80 days. server kernel: [7572666.186852] asterisk[3673]: segfault at 10 ip 7f3b8e90b4aa sp 40bf5f00 error 4 in l ibpthread-2.7.so[7f3b8e903000+16000] Anything what can be done to find out the reason? best regards Thomas

Ok, here is a patch waiting for new CVS :). It works fine for me, but please check it before commiting... -- Miroslav Lichvar -------------- next part -------------- --- src/libFLAC/bitbuffer.c.orig 2003-01-30 17:36:01.000000000 +0100 +++ src/libFLAC/bitbuffer.c 2003-01-30 21:53:18.000000000 +0100 @@ -51,6 +51,25 @@ */ static const unsigned FLAC__BITBUFFER_DEFAULT_CAPACITY = ((65536 - 64) *

G'day Timothy, On Tue, 19 Dec 2017 18:28:00 -0600 Timothy Axberg <axbergtimothy at gmail.com> wrote: > Should I repost the question with reply-all? Nope, we got all from Jeff's post. :) > On Tue, Dec 19, 2017 at 6:13 PM, Jeff Newmiller > <jdnewmil at dcn.davis.ca.us> wrote: > > > You also need to reply-all so the mailing list stays in the loop. > >

Should I repost the question with reply-all? On Tue, Dec 19, 2017 at 6:13 PM, Jeff Newmiller <jdnewmil at dcn.davis.ca.us> wrote: > You also need to reply-all so the mailing list stays in the loop. > -- > Sent from my phone. Please excuse my brevity. > > On December 19, 2017 4:00:29 PM PST, Timothy Axberg < > axbergtimothy at gmail.com> wrote: > >Sorry about

I am experiencing a change in behaviour of my Queues in 1.4.9 vs 1.4.8. I do not pass the 'n' option to any call to Queue() in my dialplan. Yet since I upgraded to 1.4.9, I have occasionally seen this on my console: -- Nobody picked up in 20000 ms -- Exiting on time-out cycle That log message "Exiting on time-out cycle" is exclusive to the logic in app_queue meant to

Hi, I need to determinate HSD value from a matrix like that Thesis Days A1 Cx 0 66.07 Cx 0 60.24 Cx 0 42.86 Tw 0 66.07 Tw 0 60.24 Tw 0 42.86 Aa 0 66.07 Aa 0 60.24 Aa 0 42.86 Qe 0 66.07 Qe 0 60.24 Qe 0 42.86 Cx 56 310.86 Cx 56 223.17 Cx 56 186.77 Tw 56 149.42 Tw 56 127.75 Tw 56 138.59 Aa 56 130.24 Aa 56 214.83 Aa 56 137.95 Qe 56 186.64 Qe 56 189.09 Qe 56 187.87 this is my script

I am relatively new to NLME, so the solution to the problem I describe here may be obvious. But I've spent several days trying to get the right syntax to formulate random effects for this model appropriately. The full model is: nlme(a ~ a.mitscherlich(a.qe, a.max, lcp, light), data=light, fixed = a.max + a.qe + lcp ~ trt, random = a.max + a.qe + lcp ~ 1 | bench/line,