|number of items in the 'rtsp_streams' variable |
|struct RTSPStream **||rtsp_streams|
|streams in this session |
|indicator of whether we are currently receiving data from the server. |
|the seek value requested when calling av_seek_frame(). |
|RTSP command sequence number. |
|copy of RTSPMessageHeader->session_id, i.e. |
|copy of RTSPMessageHeader->timeout, i.e. |
|timestamp of the last RTSP command that we sent to the RTSP server. |
|the negotiated data/packet transport protocol; e.g. |
|the negotiated network layer transport protocol; e.g. |
|brand of server that we're talking to; e.g. |
|plaintext authorization line (username:password) |
|authentication state |
|The last reply of the server to a RTSP command. |
|RTSPStream->transport_priv of the last stream that we read a packet from. |
|some MS RTSP streams contain a URL in the SDP that we need to use for all subsequent RTSP requests, rather than the input URI; in other cases, this is a copy of AVFormatContext->filename. |
|The synchronized start time of the output streams. |
|The following are used for Real stream selection. |
|enum AVDiscard||real_setup_cache [MAX_STREAMS]|
|stream setup during the last frame read. |
|the last value of the "SET_PARAMETER Subscribe:" RTSP command. |
|The following are used for RTP/ASF streams. |
|cache for position of the asf demuxer, since we load a new data packet in the bytecontext for each incoming RTSP packet. |
some MS RTSP streams contain a URL in the SDP that we need to use for all subsequent RTSP requests, rather than the input URI; in other cases, this is a copy of AVFormatContext->filename.
the seek value requested when calling av_seek_frame().
This value is subsequently used as part of the "Range" parameter when emitting the RTSP PLAY command. If we are currently playing, this command is called instantly. If we are currently paused, this command is called whenever we resume playback. Either way, the value is only used once, see rtsp_read_play() and rtsp_read_seek().
indicator of whether we are currently receiving data from the server.
Basically this isn't more than a simple cache of the last PLAY/PAUSE command sent to the server, to make sure we don't send 2x the same unexpectedly or commands in the wrong state.