Bug in rtspsrc when using TCP

Holland, James jholland at tycoint.com
Tue May 23 14:49:01 UTC 2017

Hello all,

There seems to be a bug in rtspsrc. Stream selection doesn't work when protocols flag is set to only accept TCP.

There is a callback for the select-stream signal, through which one can select the stream they wish to SETUP/PLAY. (By returning true in the callback).

When TCP transport is set, via the protocols flag, it breaks if the select-stream callback function is called (and any stream other than the first stream is selected).

If TCP transport is set and the select-stream callback isn't used, the stream is played completely fine. This can be seen in wireshark.

I have written a small client application and a small server application (a fork of the gstreamer rtsp server with added streams) that demonstrate this issue:





This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170523/919110ed/attachment.html>

More information about the gstreamer-devel mailing list