1. 30 Sep, 2016 3 commits
  2. 27 Sep, 2016 1 commit
  3. 26 Sep, 2016 4 commits
  4. 24 Sep, 2016 2 commits
  5. 22 Sep, 2016 2 commits
  6. 19 Sep, 2016 2 commits
  7. 17 Sep, 2016 2 commits
  8. 15 Sep, 2016 2 commits
  9. 13 Sep, 2016 1 commit
  10. 12 Sep, 2016 1 commit
  11. 10 Sep, 2016 5 commits
  12. 09 Sep, 2016 2 commits
  13. 08 Sep, 2016 1 commit
    • Sebastian Dröge's avatar
      basesink: Use the average durations based on timestamps for the QoS proportion... · c1bd6677
      Sebastian Dröge authored
      basesink: Use the average durations based on timestamps for the QoS proportion when doing trickmodes
      
      The durations of the buffers are (usually) assuming that no frames are being
      dropped and are just the durations coming from the stream. However if we do
      trickmodes, frames are being dropped regularly especially if only key units
      are supposed to be played.
      
      Fixes completely bogus QoS proportion values in the above case.
      c1bd6677
  14. 05 Sep, 2016 4 commits
  15. 04 Sep, 2016 1 commit
  16. 02 Sep, 2016 1 commit
  17. 01 Sep, 2016 4 commits
  18. 31 Aug, 2016 2 commits
    • Carlos Rafael Giani's avatar
      multiqueue: Add higher-resolution low/high-watermark properties · 5988095f
      Carlos Rafael Giani authored
      low/high-watermark are of type double, and given in range 0.0-1.0. This
      makes it possible to set low/high watermarks with greater resolution,
      which is useful with large multiqueue max sizes and watermarks like 0.5%.
      
      Also adding a test to check the fill and watermark level behavior.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=770628
      5988095f
    • Carlos Rafael Giani's avatar
      multiqueue: Distinguish between buffering percentage and buffering level · 67874ea8
      Carlos Rafael Giani authored
      To make the code clearer, and to facilitate future improvements, introduce
      a distinction between the buffering level and the buffering percentage.
      
      Buffering level: the queue's current fill level. The low/high watermarks
      are in this range.
      
      Buffering percentage: percentage relative to the low/high watermarks
      (0% = low watermark, 100% = high watermark).
      
      To that end, get_percentage() is renamed to get_buffering_level(). Also,
      low/high_percent are renamed to low/high_watermark to avoid confusion.
      mq->buffering_percent values are now normalized in the 0..100 range for
      buffering messages inside update_buffering(), and not just before sending
      the buffering message. Finally the buffering level range is parameterized
      by adding a new constant called MAX_BUFFERING_LEVEL.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=770628
      67874ea8