I guess it's related to PCR rolling over within that file
Yes. The MPEG Transport Stream file indexing mechanism requires that
the PCRs be increasing throughout the file.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-de
I guess it's related to PCR rolling over within that file
[st...@centosp4 readable]$ head -1 1431_20090215193000.ts | dvbsnoop -if
- -s ts -tssubdecode | grep clock
program_clock_reference:
==> program_clock_reference: 2480569434945 (0x2418d75c341) [=
PCR-Timestamp: 2
Is there a possible bug that after you request something higher than 3570
seconds it is not working on transport stream files? It always brings me
back to the same scene.
Transport file length : 20177187044 (20GB)
Index file lenght : 1151033004 (1.1 GB)
Thanks.
On Thu, Apr 2, 2009 at 11:18 AM, S
I can't use the live555 client, I'm using an Amino STB. My first test failed
(maybe I used the wrong stream with no trick play), but my second test just
worked.
Thanks.
On Wed, Apr 1, 2009 at 5:21 PM, Ross Finlayson wrote:
> Seems like there is an option in RTSP to specify a range in time that
Seems like there is an option in RTSP to specify a range in time
that you want to start your stream.
Yes, and we support it, for both RTSP clients and RTSP servers.
For RTSP clients: Note the "start" and "end" parameters to
"RTSPClient:: playMediaSession()" and "RTSPClient::
playMediaSubsessi
Seems like there is an option in RTSP to specify a range in time that you
want to start your stream.
I did a web page for a STB that when a certain button is pressed (for
example), I take the current Position and add 30 to it and set the position.
The new npt is sent to the server but mediaServer
