1. 23 Nov, 2018 1 commit
    • Nirbheek Chauhan's avatar
      gst-inspect: Use less -F -X everywhere as the pager · a3abe8b9
      Nirbheek Chauhan authored
      This emulates the default behaviour of git help pages, and also fixes
      a bug on macOS where `less -F` doesn't display anything at all when
      the output is shorter than one terminal screen.
      
      Also moved the DEFAULT_PAGER define to after the includes, because
      it's an unprefixed define.
      
      Fixes #330
      a3abe8b9
  2. 12 Nov, 2018 3 commits
  3. 10 Nov, 2018 4 commits
  4. 09 Nov, 2018 2 commits
  5. 08 Nov, 2018 3 commits
    • Tim-Philipp Müller's avatar
      Fix distcheck · b92e34eb
      Tim-Philipp Müller authored
      Follow-up to !18 and #320.
      b92e34eb
    • Michael Olbrich's avatar
      gst: add some gdb python macros · bc621cc3
      Michael Olbrich authored
      This adds gdb pretty printer for some GStreamer types.
      For GstObject pointers the type and name is added, e.g.
      "0x5555557e4110 [GstDecodeBin|decodebin0]".
      For GstMiniObject pointers the object type is added, e.g.
      "0x7fffe001fc50 [GstBuffer]".
      For GstClockTime and GstClockTimeDiff the time is also printed in human
      readable form, e.g. "150116219955 [+0:02:30.116219955]".
      
      Fixes #320
      bc621cc3
    • Sebastian Dröge's avatar
      clock: Move clock GWeakRef to a private GstClockEntry struct · 1fda8c3b
      Sebastian Dröge authored
      There's no need for it to be in the public struct and we can keep the
      padding for things to be added in the future.
      1fda8c3b
  6. 07 Nov, 2018 2 commits
    • Matthew Waters's avatar
      query: add a new bitrate query · 4fc4ad87
      Matthew Waters authored
      Allows determining from downstream what the expected bitrate of a stream
      may be which is useful in queue2 for setting time based limits when
      upstream does not provide timing information.
      
      Implement bitrate query handling in queue2
      
      gst-plugins-base#60
      4fc4ad87
    • Matthew Waters's avatar
      queue2: avoid ping-pong between 0% and 100% buffering messages · c4ccff78
      Matthew Waters authored
      If upstream is pushing buffers larger than our limits, only 1 buffer
      is ever in the queue at a time.  Once that single buffer has left the
      queue, a 0% buffering message would be posted followed immediately by a
      100% buffering message when the next buffer was inserted into the queue
      a very short time later.  As per the recommendations, This would result
      in the application pausing for a short while causing the appearance of
      a short stutter.
      
      The first step of a solution involves not posting a buffering message if
      there is still data waiting on the sink pad for insertion into the queue.
      This successfully drops the 0% messages from being posted however a
      message is still posted on each transition to 100% when the new buffer
      arrives resulting in a string of 100% buffering messages.  We silence
      these by storing the last posted buffering percentage and only posting a
      new message when it is different from or last posted message.
      c4ccff78
  7. 06 Nov, 2018 6 commits
  8. 05 Nov, 2018 19 commits