1. 10 Nov, 2016 3 commits
  2. 09 Nov, 2016 1 commit
  3. 03 Nov, 2016 2 commits
  4. 02 Nov, 2016 5 commits
  5. 01 Nov, 2016 1 commit
    • Tim-Philipp Müller's avatar
      baseparse: fix draining with less data than min frame size available · 2e278aeb
      Tim-Philipp Müller authored
      baseparse would pass whatever is left in the adapter to the
      subclass when draining, even if it's less than the minimum
      frame size required. This is bogus, baseparse should just
      discard that data then. The original intention of that code
      seems to have been that if we have more data available than
      the minimum required we should pass all of the data available
      and not just the minimum required, which does make sense, so
      we'll continue to do that in the case that more data is available.
      
      Fixes assertions in rawvideoparse on EOS after not-negotiated with
      fakesrc sizetype=random ! queue ! rawvideoparse format=rgb ! appsink caps=video/x-raw,format=I420
      
      https://bugzilla.gnome.org/show_bug.cgi?id=773666
      2e278aeb
  6. 24 Oct, 2016 1 commit
  7. 21 Oct, 2016 1 commit
  8. 15 Sep, 2016 1 commit
  9. 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
  10. 27 Aug, 2016 1 commit
  11. 19 Aug, 2016 1 commit
  12. 20 Jul, 2016 1 commit
  13. 12 Jul, 2016 1 commit
    • Sebastian Dröge's avatar
      basesrc: Fix automatic-eos=false mode if a segment.stop is given · af0d087b
      Sebastian Dröge authored
      If segment.stop was given, and the subclass provides a size that might be
      smaller than segment.stop and also smaller than the actual size, we would
      already stop there.
      
      Instead try reading up to segment.stop, the goal is to ignore the (possibly
      inaccurate) size the subclass gives and finish until segment.stop or when the
      subclass tells us to stop.
      af0d087b
  14. 05 Jul, 2016 1 commit
  15. 04 Jul, 2016 1 commit
  16. 13 Jun, 2016 1 commit
    • Sebastian Dröge's avatar
      basesink: Update start time when losing state only if we were in PLAYING · b9a4a2a9
      Sebastian Dröge authored
      If we were in PAUSED, the current clock time and base time don't have much to
      do with the running time anymore as the clock might have advanced while we
      were PAUSED. The system clock does that for example, audio clocks often don't.
      
      Updating the start time in PAUSED will cause a) the wrong position to be
      reported, b) step events to step not just the requested amount but the amount
      of time we spent in PAUSED. The start time should only ever be updated when
      going from PLAYING to PAUSED to remember the current running time (to be able
      to compensate later when going to PLAYING for the clock time advancing while
      PAUSED), not when we are already in PAUSED.
      
      Based on a patch by Kishore Arepalli <kishore.arepalli@gmail.com>
      
      The updating of the start time when the state is lost was added in commit
      ba943a82 to fix the position reporting when
      the state is lost. This still works correctly after this change.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=739289
      b9a4a2a9
  17. 10 Jun, 2016 2 commits
    • Sebastian Dröge's avatar
      adapter: Rename functions and implement new functions, update test · 8c7da1d4
      Sebastian Dröge authored
      We don't do calculations with different units (buffer offsets and bytes)
      anymore but have functions for:
      1) getting the number of bytes since the last discont
      2) getting the offset (and pts/dts) at the last discont
      
      and the previously added function to get the last offset and its distance from
      the current adapter position.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766647
      8c7da1d4
    • Edward Hervey's avatar
      adapter: Add methods to query current offset · 67ae0ad2
      Edward Hervey authored
      API: gst_buffer_prev_offset
      API: gst_buffer_get_offset_from_discont
      
      The gst_buffer_get_offset_from_discont() method allows retrieving the current
      offset based on the GST_BUFFER_OFFSET of the buffers that were pushed in.
      
      The offset will be set initially by the GST_BUFFER_OFFSET of
      DISCONT buffers, and then incremented by the sizes of the following
      buffers.
      
      The gst_buffer_prev_offset() method allows retrievent the previous
      GST_BUFFER_OFFSET regardless of flags. It works in the same way as
      the other gst_buffer_prev_*() methods.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766647
      67ae0ad2
  18. 07 Jun, 2016 1 commit
  19. 23 May, 2016 1 commit
  20. 15 May, 2016 1 commit
  21. 05 May, 2016 2 commits
  22. 20 Apr, 2016 2 commits
  23. 15 Apr, 2016 1 commit
  24. 12 Apr, 2016 2 commits
  25. 24 Mar, 2016 2 commits
  26. 14 Mar, 2016 1 commit
  27. 15 Feb, 2016 1 commit
  28. 12 Feb, 2016 1 commit