Tony has a valid point here. Is there any way for you to try on different hardware? Portaudio, in the grand scheme of things, isn't very high on the food chain when it comes to FS development, especially with 1.0 only a few weeks away. Please see if you can reproduce these symptoms on other hardware, preferably better hardware, and then report back. Believe, if there is a problem with FS then Tony and Mike will definitely address it, but if it's just a hardware issue then it would be better for those guys to be spending their time frying the bigger fish. Thanks, MC ________________________________ From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Friday, May 09, 2008 10:51 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] mod_portaudio send3rtppacket/60msinsteadof1packet/20ms I think that is where i have to draw the line and say get some better hardware........ I did my best but if the box sucks that badly at timing i am not sure what else to do because it's working flawlessly on mine which proves it depends on the box and i dont 'even like portaudio On Fri, May 9, 2008 at 6:34 AM, Sluschny, Thomas <Thomas.Sluschny@siemens.com> wrote: ok, now it looks better, i. e. the switch_core_timer_check() times the ReadAudioStream function, but not perfect, now i see packets with differences of 15, 30, 45, 0 ms, e. g. 15, 15, 30, 15, 15, 15, 31, 16, 15, 31, 15, 16, 16, 29 ms and so on Looks like we already stuck with time resolution, but the switch_yield(1000) in ReadAudioStream() seems to work properly, strange ... I don't have the time to go deeper into and i next read my emails on tuesday :( I don't want to hijack this thread from Csaba, should we make a jira entry, Csaba? (for Anthonys clients sake :) ) Thomas