[gstreamer-bugs] [Bug 353680] qos-query + qos reporting

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

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #11 from Stefan Kost (gstreamer, gtkdoc dev)  2007-05-23 06:49 UTC -------
I am fine with postponing this for later (you've got valid points in your
comment).

* regaring the term 'frames'. Bytes does not make sense imho. Only percent
would make sense imho (there is GST_FORMAT_PERCENT). Its maybe even better,
because then one can formulate some test criteria that warn if a test-case
drops more that a certain percentage of frames. The modification for percent
would be simple - I can return
  percent_dropped=percent_dropped/(frames_rendered+frames_dropped);
  (percent_dropped=0.0 if (frames_rendered+frames_dropped)==0)
The value would be a double.

* qos.data file. Right, I can turn '-r' intp '-r <datafile>'. If only '-r' is
given, I can just print the sumary table. or should I better add '--qos-data
<datafile>' and if that is not given write no datafile.

Jan, its not so much the frustration, it more that this can be quite useful if
it can be savely used accross gstreamer, but right now I am reluctant to not
have too many local changes. It would be nice to have this in 0.10.14 in a
solid way.


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