No. Our code delivers data (in this case, to the OS pipe, and from there to your "ffplay" command) once it arrives. The 'increasing delay' that you're seeing has to be caused by your downstream code (your "ffplay" command) not consuming data fast enough. Either your "ffplay" command is CPU bound, or else it's displaying at a frame rate that's slower than that of the incoming data.
In the latter case, what might be happening is that your receiving computer's clock is running at a slightly slower rate than the sending computer's clock. In that case - because you're using a simple FIFO (i.e., pipe) feeding into your application (i.e., "ffplay") - there's nothing that you can do. (A more sophisticated media player application would typically start dropping frames once it noticed that its internal 'jitter buffer' was filling up (due to mismatched clock speeds).) Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
