1. 29 Mar, 2012 1 commit
  2. 28 Mar, 2012 8 commits
  3. 27 Mar, 2012 7 commits
  4. 26 Mar, 2012 4 commits
  5. 23 Mar, 2012 1 commit
  6. 21 Mar, 2012 1 commit
  7. 20 Mar, 2012 2 commits
    • Wim Taymans's avatar
      pad: improve docs of get/pull_range · f9c85a53
      Wim Taymans authored
      Improve the docs of the get/pull_range functions, define the lifetime of the
      buffer in case of errors and short reads.
      Make sure the code does what the docs say.
      f9c85a53
    • Wim Taymans's avatar
      buffer: improve gst_buffer_new_wrapped_full() · 7bcc3baf
      Wim Taymans authored
      Make it possible to wrap all kinds of memory by exposing all properties to
      gst_buffer_new_wrapped_full(). This makes it possible to also create writable
      memory without a free function or memory with extra padding.
      7bcc3baf
  8. 16 Mar, 2012 2 commits
    • Wim Taymans's avatar
      pad: change the semantics of get/pull_range a little · db1318ab
      Wim Taymans authored
      Make it so that one can specify a buffer for get/pull_range where the downstream
      element should write into. When passing NULL, upstream should allocate a buffer,
      like in 0.10.
      We also need to change the probes a little because before the pull probe, there
      could already be a buffer passed. This then allows us to use the same PROBE
      macro for before and after pulling.
      While we're at the probes, make the query probe more powerful by handling the
      GST_PAD_PROBE_DROP return value. Returning _DROP from a query probe will now
      return TRUE upstream and will not forward the probe to the peer or handler.
      Also handle _DROP for get/pull_range properly by not dispatching to the
      peer/handler or by generating EOS when the probe returns DROP and no buffer.
      Make filesrc handle the non-NULL buffer passed in the get_range function and
      skip the allocation in that case, writing directly into the downstream provided
      buffer.
      Update tests because now we need to make sure to not pass a random value in the
      buffer pointer to get/pull_range
      db1318ab
    • Wim Taymans's avatar
      6b908502
  9. 15 Mar, 2012 8 commits
  10. 14 Mar, 2012 6 commits
    • Wim Taymans's avatar
      memory: Add 0 padding · edd2ffe4
      Wim Taymans authored
      Change gst_allocator_alloc() so that we can also spicify flags and padding.
      Add 2 new flags to mark the memory 0 prefixed/padded. This allows us to
      remove some resizes in the base classes.
      When allocating memory, memset prefix and padding with 0 when the flags tell
      us to.
      On resize, clear the zero padding flags if we can't guarantee the memory is
      still 0 filled.
      Update tests.
      edd2ffe4
    • Wim Taymans's avatar
      query: also include padding in ALLOCATION query · 3d76e601
      Wim Taymans authored
      Negotiating padding is needed on second thought so include it in the
      ALLOCATION query.
      Make the bufferpool take padding into account when allocating.
      Make basesrc take padding into account.
      Use padding and prefix when allocating in basetransform.
      3d76e601
    • Mark Nauwelaerts's avatar
      f2d81f4c
    • Wim Taymans's avatar
      pad: implement DRAIN handling · e3328629
      Wim Taymans authored
      When we forward the DRAIN query and there is nothing to forward it to, assume we
      are drained.
      When a basesink receives a drain query, reply with TRUE.
      e3328629
    • Wim Taymans's avatar
      query: add new drain query · 318baf4c
      Wim Taymans authored
      With the new serialized downstream queries we can implement a drain query that
      makes an element waits until a downstream element replies to the query.
      318baf4c
    • Wim Taymans's avatar
      pad: make serialized queries push sticky events first · 05cd564b
      Wim Taymans authored
      Before we can proceed with a serialized query, we need to be sure that all
      sticky events were pushed.
      05cd564b