[gstreamer-bugs] [Bug 575649] New: duration query in time format returns true with length 0

[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=575649

  GStreamer | gst-plugins-base | Ver: git
           Summary: duration query in time format returns true with length 0
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: cascardo at holoscopio.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.23/2.24
   GNOME milestone: Unspecified


Please describe the problem:
When playing a pipeline with a non-pull source (souphttpsrc), oggdemux is not
able to get all the chains to calculate the complete duration of the stream. In
this case, when querying duration with GST_FORMAT_TIME, we should get FALSE,
not TRUE with length 0, which is what it does now.

Steps to reproduce:
1. Create a playbin with a http uri and a ogg file
2. query the duration in time format
3. see that it returns true and the length is 0


Actual results:
duration query returns true and length is 0

Expected results:
duration query should return false

Does this happen every time?
yes

Other information:
ogg->total_time is zero. and it is returned, without querying if it's streaming
or not.


-- 
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=575649.