[gstreamer-bugs] [Bug 627942] [queue2] wrong percent-filled estimation during on-disk buffering

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Wed Aug 25 13:14:02 PDT 2010


https://bugzilla.gnome.org/show_bug.cgi?id=627942
  GStreamer | gstreamer (core) | git

--- Comment #9 from Wim Taymans <wim.taymans at gmail.com> 2010-08-25 20:14:00 UTC ---
(In reply to comment #8)
> Right, looks like I got confused when reading the log. I didn't know it made
> sense to have percent > 100 ;)

See, the percent is for doing buffering between a high/low watermark, the high
watermark is expressed with max_level (which is usually a lot less than the
total size of the media) and high-percent. 

The method of operation is that you can start playback as soon as you have
max_level bytes buffered in the queue (at which point the percent is 100%). For
normal memory caching, this max_level is then also the point where the input is
blocked and the queue is considered full (nothing goes in anymore until
something has gone out); this all to not exhaust main memory. 

For on-disk caching, there is no reason to block the input because we can just
write to disk as much as we want and thus the percent and max_level go past
100% easily.

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