I have my burst rate set to something low, 4096 right now. I also wrote a flash/flex app that has the same size buffer which results in the audio being heard immediately when connecting. As far as the audio being real time, the audio stream is about 6 seconds behind which I'm guessing is the result of the size of the lame buffers in the mod_shout modules (i'm using g.711 ulaw), I was going to look into that next week. Anyone have any thoughts about where else the delay may be happening? I hoping to get this down to around 2 seconds.
D- ----- Original Message ----- From: "Rupa Schomaker" <[email protected]> To: [email protected] Sent: Thursday, April 2, 2009 8:05:38 AM GMT -07:00 US/Canada Mountain Subject: Re: [Freeswitch-users] mod_shout delay in trunk 2009/4/2 Anthony Minessale < [email protected] > Its the buffering and startup of the shout stream taking up the time, HINT put the shoutcast stream into a local stream with a .loc file and then play that in the conference. Ah, that is easy enough! Though I think with icecast doing the burst_on_connect thingie there should be enough data (pushed much faster than real time) to fill FS's buffers. But that would require mod_shout to cooperate with that strategy. ie: on connect, drain the socket as fast as it can filling it's own buffers. Once it's own buffers are full start streaming. I think right now it drains the socket only as fast as it needs to. Or maybe not. <shrug/> I'll go the local stream route for now.... -- -Rupa _______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
