[Bug 770954] Client cannot decide destination/port in SETUP

["GStreamer" (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=770954

Sebastian Dröge (slomo) <***@coaxion.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@coaxion.net

--- Comment #1 from Sebastian Dröge (slomo) <***@coaxion.net> ---
That would require adding a new updsink, which potentially causes pipelines
getting stuck. The queues after the tee might be full (because the pipeline is
blocked, waiting for the actual client sink to be added) and then the newly
added client sink never prerolls because it will never get data.

At this point it might be nicer to write a custom RTSP server sink element (and
maybe even a source element) for UDP, that handles multiple sockets internally
from one thread (and does not require queues, threads per udpsrc, ...). We
almost completely manage the sockets already anyway.

["GStreamer" (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=770954

GStreamer system administrator <***@gstreamer.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE

--- Comment #2 from GStreamer system administrator <***@gstreamer.net> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/issues/27.