- The absolute timestamp I ask for doesn't match what I receive, Many hours
off, but at least it's consistent.
For what it's worth, this sounds like it could potentially be a time zone
issue. I've run into issues in the past where some of the routines I used
interpreted my UTC timestamp as
> - The absolute timestamp I ask for doesn't match what I receive, Many hours
> off, but at least it's consistent.
>
> For what it’s worth, this sounds like it could potentially be a time zone
> issue. I’ve run into issues in the past where some of the routines I used
> interpreted my UTC tim
- The absolute timestamp I ask for doesn't match what I receive, Many hours
off, but at least it's consistent.
For what it's worth, this sounds like it could potentially be a time zone
issue. I've run into issues in the past where some of the routines I used
interpreted my UTC timestamp as a t
> The functionality works ok when using the Cisco Active X control, but I get
> the exact same issue when sending RTSP commands manually via a telnet client
> (which is expected, just confirming liveMedia doesn't introduce anything).
OK, so it should be easy to figure out what RTSP commands the
FYI, the latest version (2012.08.20) of the "LIVE555 Streaming Media" code
adds optional RTSP server and RTSP client support for streams that are
indexed by 'absolute' time - i.e., using strings of the form
"MMDDTHHMMSSZ" or "MMDDTHHMMSS.Z".
Ross Finlayson
Ross, Thank you very muc
> After doing some testing with openRTSP and looking through the code it
> appears like "Absolute Time" is currently not supported for RTSP streams.
> I.e. I can't specify a specific time that the stream should seek to, e.g.
> Range: clock=20120629T07.00Z, all according to paragraph 3.7 at
> I'm curious if there is a reason that absolute time has been left out, i.e.
> are there problems implementing it, or is it just that people for some reason
> haven't been showing any interest in it?
Until recently, there just hasn't been any interest in supporting seeking by
'absolute time';
After doing some testing with openRTSP and looking through the code it appears
like "Absolute Time" is currently not supported for RTSP streams. I.e. I can't
specify a specific time that the stream should seek to, e.g. Range:
clock=20120629T07.00Z, all according to paragraph 3.7 at
http://w
