[Bug 580093] tcpserversink,src: signal actually used port when port=0 was set

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Oct 12 13:26:02 PDT 2012


https://bugzilla.gnome.org/show_bug.cgi?id=580093
  GStreamer | gst-plugins-base | git

--- Comment #9 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-10-12 20:25:56 UTC ---
No, I think you're right. What I was thinking of is this:

 - you set the port property to 0

 - then you use the element, and a port
    gets selected automatically, now you
    store that port in the property variable

 - now you shut down the element, and
   start it up again - but now the port is
   no longer 0 but what was used in the
   previous run, which may or may not
   work. A port is no longer selected
   automatically.

 - to work around that, you'd have to
   get the port from the addr in the 
   property getter *if* the property
   is 0 and addr exists, I think. Not
   really sure if that's how it's supposed
   to work tbh.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list