Thank you Kevin, I have the impression it got better, but I yet didn't have the chance to test it much. If there are I/O problems, are there any logs for this / are there logs in general for monitor and MixMonitor? Thanks :-)
2012/7/25 Kevin P. Fleming <[email protected]> > On 07/25/2012 06:42 AM, Stefan at WPF wrote: > >> Hmm is it possible, that the monitor command changes the quality? If not >> I guess I also once have to try compiling it from source, though I >> wanted to avoid that. >> > > It certainly can, since recording the call causes disk I/O as the audio is > written out. In addition, Monitor is more prone to this problem than > MixMonitor is, because Monitor's call recording is done in the same thread > that handles the call's audio normally. If you switch to MixMonitor, you'll > probably have better results, unless your system just can't handle > recording the call without overloading its CPU. > > > -- > Kevin P. Fleming > Digium, Inc. | Director of Software Technologies > Jabber: [email protected] | SIP: [email protected] | Skype: kpfleming > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at www.digium.com & www.asterisk.org > > -- > ______________________________**______________________________**_________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/**mailman/listinfo/asterisk-**users<http://lists.digium.com/mailman/listinfo/asterisk-users> >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
