<br><br><div class="gmail_quote">2009/4/2 Anthony Minessale <span dir="ltr"><<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Its the buffering and startup of the shout stream taking up the time,<br><br>HINT put the shoutcast stream into a local stream with a .loc file and then play that in the conference.<br></blockquote></div><br>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. <br>
<br>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/><br>
<br>I'll go the local stream route for now....<br clear="all"><br>-- <br>-Rupa<br>