Skip to content

rtsp-stream: fix get_rates raciness

Prior to this patch, we considered that a stream was blocking whenever a pad probe was triggered for either the RTP pad or the RTCP pad.

This led to situations where we subsequently unblocked and expected to find a segment on the RTP pad, which was racy.

Instead, we now only consider that the stream is blocking when the pad probe for the RTP pad has triggered with a blockable object (buffer, buffer list, gap event).

The RTCP pad is simply blocked without affecting the state of the stream otherwise.

Fixes #929 (closed)

Edited by Mathieu Duponchelle

Merge request reports