I've got a source (hardware encoder) which delivers MPEG2 transport stream frames with PCR's that are non-monotonic. This completely breaks the MPEG2TransportStreamFramer as it uses these to determine the packet duration. Anyone have any idea whether (a) it's even valid for the hardware encoder to do this
I don't believe it is, no.
and (b) how to calculate a sensible duration when this is the case?
I suggest reprocessing your Transport Stream files (before you index and/or stream them) so that their PCRs make sense.
-- 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
