[Bug 712782] New: Require a feature to display buffered status when using push source
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed Nov 20 19:59:17 PST 2013
https://bugzilla.gnome.org/show_bug.cgi?id=712782
GStreamer | gst-plugins-good | unspecified
Summary: Require a feature to display buffered status when
using push source
Classification: Platform
Product: GStreamer
Version: unspecified
OS/Version: Mac OS
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-good
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: justin.joy.9to5 at gmail.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
The original question was about how to display buffer status.
http://lists.freedesktop.org/archives/gstreamer-devel/2013-September/042771.html
Then, firstly, I suggested a proposal to accumulate all bytes inside of each
element by a certain query.
http://lists.freedesktop.org/archives/gstreamer-devel/2013-November/043983.html
After prototyping, I found my first suggestion was wrong because it would make
big burden to each element.
Finally, I found if the upper layer of gstreamer pipeline has content-length,
read-position, and average bitrate, it can estimate the buffer status during
playing time. To get these information, it is only required to expose internal
monitoring data in case of souphttpsrc.
QUERY_POSITION is about current playing, read-position is about a position
where it downloads. If src provides its read-position, the upper layer can
display how much buffer is fulled like youtube player does.
I know more general approach would be better, but I found that other cases like
mms doesn't have similar internal data. It means that it's hard to pursue
general way in this step.
--
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