[gstreamer-bugs] [Bug 580851] New: rtspsrc: various; sanity of ranges, setting of base_time and eof behaviour

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=580851

  GStreamer | gst-plugins-good | Ver: git
           Summary: rtspsrc: various; sanity of ranges, setting of base_time
                    and eof behaviour
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: manauw at skynet.be
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


(a) live WMS server may report range as e.g. npt=3.000-3.000 during DESCRIBE,
and as 0.000-5370199679810142.208 upon PLAY.  Neither of these provide
something useful (and may lead to overflow problems), so some sanity checks can
be helpful.

(b) During flushing seek processing, base_time of udpsrc is reset to have
timestamps/running_time resume at 0.  However, the base_time of rtspsrc is not
reset, so there is an inconsistency in subsequent downstream (initial)
timestamps depending on UDP or interleaved TCP.

(c) If eof is reached, server might close connection or send eof
message/request.  In any case, this is announced as "connection closed" but a
subsequent state change might still try to perform TEARDOWN etc with subsequent
read/write errors.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=580851.