Hello Mike
In my particular case, I was looking for lost packets (RTSP over UDP) in order to figure out how I should deal with those in the codec and also what the RTCP packets were containing, since I couldn't figure out the weird data I was getting. The graphs don't tell me much either. Not only do they contain bars that span the entire Y-axis, they also suffer from severe redraw issues, once you zoom in on some spots... I tend to look mostly at the list of packets and then use "Jump To" to further inspect the packets in the main window. roland From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 4:25 PM To: [EMAIL PROTECTED] Subject: [Live-devel] Very large P-frames in a recording Roland Thanks for the suggestion. We've confirmed that the large frames contain only a single picture by searching for the MPEG-2 start codes. We're working on a filter that will truncate a frame when it exceeds a given size, so that excessively large frames are not written to the file. What exactly do you look for in Wireshark? I can see that it recognizes the RTP streams, but I didn't see where to get a more detailed analysis -- it's hard for me to tell what the analysis graphs are really measuring. -=- Mike Miller Rockwell Collins, Inc. Cedar Rapids, IA
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
