> 2. Seek in that stream.
> Range: clock=20130322T20.000Z-
>
> The response to #2:
> Range: clock=20130322T20Z-20130322T204538Z
>
> 3. And then, after teardown, start up the same stream with the same seek-time.
> PLAY rtsp://192.168.1.103/archive/TVF-01a/ RTSP/1.0
> Range: clock=2013032
Is this intended, or is it somehow server dependent?
I don't know. Please show the complete RTSP protocol exchange for each
case, so I can try to figure out what's happening.
I've attached the protocol exchange for the following example:
1. Start up an archive stream without any ti
> Is this intended, or is it somehow server dependent?
I don't know. Please show the complete RTSP protocol exchange for each case,
so I can try to figure out what's happening.
> Is there a way to confirm what position is currently playing when starting up
> a stream?
>
> Is there a way to
In the following examples I'm writing about streams that are (in the code)
referred to as indexed by 'absolute' time. For video storage and security I
believe they're often referred to as archive streams.
Seeking while already streaming
When doing a "seek" while the stream is playing, i.e.
