I can actually see using this feature as well.
Matt S.
On Thursday, May 31, 2012 7:21:06 AM, Wiser, Tyson wrote:
More seriously we need to seek in absolute mode because we would like
to query video according to the time we recorded it (and not a
relative time relative to begin of RTSP session).
More seriously we need to seek in absolute mode because we would like to query
video according to the time we recorded it (and not a relative time relative to
begin of RTSP session).
This is the first time I've ever heard of someone doing this (or even wanting
to do this). Because it's allow
> Perhaps Don Quixote wrote RFC 2326 chapter 12.19…
I think you mean chapter 12.29. (But anyway...)
> More seriously we need to seek in absolute mode because we would like to
> query video according to the time we recorded it (and not a relative time
> relative to begin of RTSP session).
Thi
boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : mercredi 23 mai 2012 12:35
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] How to specify Range in RTSPClient that are not using
npt
We try to find a way to send a range in absolute, it seems that a way could be
to
> We try to find a way to send a range in absolute, it seems that a way could
> be to specify in the RTSP PLAY command :
> - Range: clock=19961108T142300Z-19961108T143520Z
Why? Once again, I don't see the point. With a "Range:" header like this (in
fact, any "Range:" header other than "0-" or
Hi Ross,
We try to find a way to send a range in absolute, it seems that a way could be
to specify in the RTSP PLAY command :
- Range: clock=19961108T142300Z-19961108T143520Z
Reading the clock of RTSPClient it seems that no overide is possible.
In RTSPClient.cpp this seems done
