Reply to thread

Message

<blockquote data-quote="georgius" data-source="post: 1156217" data-attributes="member: 107951">Even live stream has total stream length, but it's guessed by currently downloaded stream length. Total stream length and currently downloaded stream length is used at least in OV to show user, where is your playback position within stream. And also calculation of guess of total stream length can be used as sign of properly working protocol part. If it is not increasing, there is surely some problem (except HTTP stream with known total length - but tthis is not case of live stream).Yes, RTP timestamps have to be increasing.The smallest part of stream, which can be processed by filter, is &quot;fragment&quot;. Some streams are fragmented naturally (like Adobe streams from F4M manifest, Microsoft streams or Apple streams from M3U8 playlists). All other streams must be fragmented to work with filter. E.g. in HTTP stream is fragmentation based on received data - each received part of data is considered as fragment, in RTSP is fragmentation based on RTP timestamps. So, if RTP timestamps are not changing, then protocol thinks that fragment is not already downloaded and cannot be sent for further processing in filter.</blockquote>

[QUOTE="georgius, post: 1156217, member: 107951"] Even live stream has total stream length, but it's guessed by currently downloaded stream length. Total stream length and currently downloaded stream length is used at least in OV to show user, where is your playback position within stream. And also calculation of guess of total stream length can be used as sign of properly working protocol part. If it is not increasing, there is surely some problem (except HTTP stream with known total length - but tthis is not case of live stream). Yes, RTP timestamps have to be increasing. The smallest part of stream, which can be processed by filter, is "fragment". Some streams are fragmented naturally (like Adobe streams from F4M manifest, Microsoft streams or Apple streams from M3U8 playlists). All other streams must be fragmented to work with filter. E.g. in HTTP stream is fragmentation based on received data - each received part of data is considered as fragment, in RTSP is fragmentation based on RTP timestamps. So, if RTP timestamps are not changing, then protocol thinks that fragment is not already downloaded and cannot be sent for further processing in filter. [/QUOTE]

Verification