[Live-devel] RTSP trick play, extra PES packet issue...

[Ross Finlayson]

>There are some MPEG2 TS files, and each one was :
>
>1.	Mermaid.ts
>Original MPEG2 TS file
>2.	Mermaid.tsx
>Index of #1
>3.	Mermaid_FF2x_openRTSP.ts
>FF 2x, generated from openRTSP
>FF from 00:15 to 01:15
>The result was almost like #4, except some broken frame
>4.	Mermaid_FF2x_test.ts
>FF 2x, generated from testMPEG2TransportStreamTrickPlay
>FF 2x from 0:15
>5.	Mermaid_FF8x_test.ts
>FF 8x, generated from testMPEG2TransportStreamTrickPlay
>FF 8x from 0:15
>6.	Mermaid_RW2x_openRTSP.ts
>RW 2x, generated from openRTSP
>RW 2x from 01:15 to 00:15
>The result was almost like #7, except some broken frame
>7.	Mermaid_RW2x_test.ts
>RW 2x, generated from testMPEG2TransportStreamTrickPlay
>RW 2x from 01:15 to 00:00
>8.	Mermaid_RW8x_test.ts
>RW 8x, generated from testMPEG2TransportStreamTrickPlay
>RW 8x from 01:15 to 00:00
>FYR.
>
>But also, would like to ask some questions...
>
>After analyzed packet with WireShark(tm), we found that LIVE555 will send an
>extra PES head packet in each UDP packet

Our Transport Stream RTP streaming code will transmit exactly the 
Transport Stream data that it was given (plus RTP headers, of 
course).  Therefore, if you are seeing extra PES header data in the 
network packets, then this data must have been present in the 
Transport Stream data that's being streamed.  Therefore this extra 
PES header data will (most likely) also be in at least some of the 
".ts" files that you list above.

To make it easier for me to track down your problem, could you please 
say which of the seven ".ts" files that you list above contain this 
extra PES header data?
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20100105/e48cf1eb/attachment.html>