> If we Must encrypt the transport stream then what parts of the stream should
> we leave it in the clear? Should we specifically leave the I-frames?
The Transport Stream fields (including the PCR and PID) at the start of each
188-byte Transport Stream 'packet' must all remain unencrypted. Also
Finlayson
Sent: Wednesday, April 23, 2014 6:31 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Regarding trick mode files
Thanks for your input and in fact the problem was related to the client
STB's.
If that's the case, then we can't help you. On
> Thanks for your input and sorry for the late reply. Infact the problem was
> related to the client STB’s.
If that's the case, then we can't help you. Only the manufacturer of the STB
can do help you with problems with their product (unless they want to contact
me directly about this, in whic
gards,
M. Nambirajan
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
Ross Finlayson
Sent: Tuesday, April 22, 2014 9:39 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Regarding trick mode files
The output ( x4, x15, x60 and x300
> The output ( x4, x15, x60 and x300 ) of the MPEG4 HD file plays out ok in VLC.
By this I presume you meant that you used the
"testMPEG2TransportStreamTrickPlay" utility to generate Transport Stream files
(corresponding to various fast-forward speeds of the original), and played
these files lo
Hi Ross,We are using the latest version of the Live555 Media Server and a MPEG4HD content wrapped in TS file format to test content play in trick mode. We are using ADB and Amino STB's as client devices. We use "testMPEG2TransportStreamIndexer.exe" to generate the indexer file. We have created a .t
