[gstreamer-bugs] [Bug 585956] New: [mp3parse] indexing improvements

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

  GStreamer | gst-plugins-ugly | Ver: git
           Summary: [mp3parse] indexing improvements
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gst-plugins-ugly
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: t.i.m at zen.co.uk
     GNOME version: Unspecified
   GNOME milestone: Unspecified


+++ This bug was initially created as a clone of Bug #585576 +++

There was this nice fix for mp3parse that it doesn't build an index table over
time when it cannot seek anyways, which is supposed to stop the unbounded
memory growth when listening to internet radio (for embedded devices, extra CPU
load is also a factor).

Problem is that souphttpsrc initially assumes that servers support seeking.
Try:
GST_DEBUG=mp3parse:4 gst-launch-0.10 playbin2
uri=http://gffstream.ic.llnwd.net/stream/gffstream_stream_wdr_einslive_a
2>&1|fgrep index

The server sends no Content-Length header, so there is no stream duration
(which makes it questionable to assume seekability(?)).

Either souphttpsrc should have better prediction of seekability or maybe
mp3parse should suppress index table building when the upstream duration query
fails.


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