The 2-3 second delay is (obviously) being caused by packet data getting buffered, so the question you need to answer is "Where is this buffering occurring?". I can tell you for sure that the buffering is *not* occurring in our "LIVE555 Streaming Media" code. (The only buffering delay that ever occurs in our code is the 100 ms (by default) delay that we introduce to correct for reordered incoming packets - and that occurs only immediately after a packet loss.)
So, the buffering (and thus the 2-3 second delay) must be occurring in the operating system (perhaps device drivers) of the sender and/or the receiver - *not* in our code. I suspect that your sender's WiFi device driver is buffering outgoing packets, apparently because your outgoing data rate is approaching (or exceeding) the capacity of the WiFi network. If you are streaming via multicast, then you should note that WiFi routers' multicast performance - especially by default - is notoriously bad. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
