> Also, we would like to find out which frames are key frames so we will try to > get that by passing the packets to ffmpeg which should construct the frame > and tell us whether its a key frame.
That makes no sense. The things that you feed into “ffmpeg” (and other decoders) are *frames* (or, in the case of H.264 or H.264: “NAL units”), not RTP packets (or payloads within RTP packets). Frames (or “NAL units”) are what the LIVE555 reception code gives you. Once again: You have absolutely no need to deal with RTP packet headers. But if you want to write your own RTP processing code (ignoring what LIVE555 does for you), then feel free, but be aware (as always) that if you want to do this within the LIVE555 library code, then any changes you make will be subject to the LGPL. Or you may choose to write your own RTP reception/handling library (not using the LIVE555 code at all). In either case, you can expect no support on this mailing list. 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
