rtspsrc: When seeking, consider the current element state or pending state...
rtspsrc: When seeking, consider the current element state or pending state instead of the RTSP state If we consider the RTSP state, what can happen is that it is PLAYING but the element already asynchronously tried to PAUSE and it just did not happen yet. We would then override this setting to PAUSED (while the element actually is in PAUSED) and set the RTSP state to PLAYING again. This would then cause us to produce packets while the sinks are all PAUSED, piling up thousands of packets in the rtpjitterbuffer and other elements and finally failing.
Showing with 7 additions and 3 deletions