Ok. I tried your test program. I tried with scale of 1 and 2. If the client sends "Range: npt=30.000-60.000" the server plays starting at 30 seconds into the clip (clip timing information - not wall time) and plays for 30 seconds wall time (which for scale 2 will be 60 seconds of clip time).
Shouldn't the server only stream 30 seconds according to the PTS/DTS and ignore the wall clock time for range not equal to 1? Thanks. From: Ross Finlayson Sent: Monday, July 23, 2012 1:17 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Range Header Thanks. I don't think I made myself clear though. When I fast forward with a range it doesn't stop at the requested end time (but it does stop a little while after it). When I fast forward with a range it seems to get confused and play to much. I don't follow this (perhaps one of the "with"s should have been a "without"?). But in any case, the best way to test issues like this is to use the "openRTSP" RTSP client tool. Note the 'trick play' options: "-s <initial-seek-time>", "-z <scale>", and "-d <duration>" See: http://www.live555.com/openRTSP/ I presume that your server is using indexed Transport Stream files for 'trick play'. If you can reproduce - using "openRTSP" - a specific problem with one of your files, then please tell us about it (by putting it on a publicly accessible web server), and let us know the specific "openRTSP" commands that cause a problem. Then we can test this for ourselves. 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
