[gstreamer-bugs] [Bug 641047] [mpegaudioparse] Multiple issues with new mpegaudioparse element from -bad, lower rank?

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=641047
  GStreamer | gst-plugins-bad | unspecified

--- Comment #10 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2011-02-03 18:42:47 UTC ---
As for the seeking/duration query stuff:

My feeling is that when the pipeline is prerolled (ie. baseparse has output
some buffers), it should answer both SEEKING query and duration query in some
way, even if the duration isn't very good yet at that point. 

We have a mechanism to let the application know that the duration estimate has
changed (GST_MESSAGE_DURATION) and should be re-queried.

We don't have such a mechanism for seekability. However, the seeking query
handler has the option of saying 'seekable from [0 ; -1]' (I think).

Not answering these queries until "enough" buffers have been processed sounds
like a hack to make things easier for the likes of tagreadbin and
gst-discoverer to me. I think ultimately we need better API for this, so we can
communicate the reliability of the duration value returned to the app.

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