> I'm using the most current version of live555 on an embedded linux > platform to deliver an MPEGTS stream via RTSP. I am having issues where if > I use `testRTSPClient`, the debug prints for all payload/RTP packets have > the '!' at the end meaning they are not synchronized via RTCP. Where > should I start debugging this? Our network situation is a bit odd as we're > running the streaming server on a device that is also an wifi access > point. I don't want to blame the hardware or its configuration, but I > would believe it could be a timing issue. > > For sake of debugging, our server is EXACTLY `testMPEG2TransportStreamer`.
Unfortunately I was not able to reproduce this problem, running both “testMPEG2TransportStreamer” (with "#define IMPLEMENT_RTSP_SERVER 1” uncommented) and “testRTSPClient” on the same computer. In each case, “testRTSPClient” stopped displaying “!” (meaning that it had received a RTCP “SR” packet, to synchronize its presentation times) within a second or two. If you haven’t already done so, then I suggest also running “testMPEG2TransportStreamer” and “testRTSPClient” on the same computer. If that works OK, but running over a LAN does not work, then presumably you have a network problem that’s (somehow) starving out the smaller RTCP packets. One thing to note is that the frequency of RTCP reports depends on the estimated bitrate of the data stream, which we currently estimate at 5000 kbps (i.e., 5 Mbps). See line 86 of “testProgs/testMPEG2TransportStreamer.cpp”. If the stream’s bitrate is actually more than this, then you can increase this value accordingly (which will cause RTCP reports to get sent more often). 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