1. 08 Apr, 2019 2 commits
  2. 05 Apr, 2019 3 commits
    • Mathieu Duponchelle's avatar
    • Mathieu Duponchelle's avatar
      aggregator: add buffer-consumed pad signal · ae57b1c7
      Mathieu Duponchelle authored
      The signal will be emitted when a buffer was consumed on
      a pad, if the newly-added "emit-signals" property has been
      set to TRUE.
      
      Handlers connected to the signal will receive a valid reference on
      the consumed buffer, allowing for example the retrieval of metas in
      order to forward them once an output buffer is pushed out.
      ae57b1c7
    • Antonio Ospite's avatar
      gst-inspect: fix printing the first field of a GstStructure · 90beb712
      Antonio Ospite authored
      When printing a GstStructure property (e.g. the "stats" property in
      rtpsession) the first field is printed on the same line of the type
      description, and this is both inconsistent compared to  how Enum values
      are printed and confusing as the reader might miss the first field.
      
      To fix this, add a newline before printing GstStructure fields in
      properties.
      
      NOTE: this does not change the existing inconsistent behavior of an
      extra newline *after* a GstStructure property, but the latter is not as
      annoying and it would take more effort to fix because GstStructure
      fields are printed in CAPS descriptions too.
      90beb712
  3. 01 Apr, 2019 1 commit
  4. 24 Mar, 2019 1 commit
    • Antonio Ospite's avatar
      tests: add the valgrind suppression file from the "common" module · 763d01f4
      Antonio Ospite authored
      Other gstreamer repositories have their own valgrind suppression file
      directly in the repository.
      
      Add a suppression file to the core gstreamer repository too, this makes
      it easier to use it with gst-build which does not check out the common
      module.
      
      This is also a little step towards the removal of the common submodule.
      
      NOTE: the added file is the latest version from the "common" repository
      but it has been renamed from gst.supp to gstreamer.supp for symmetry
      with the suppression files in the other repositories.
      763d01f4
  5. 23 Mar, 2019 4 commits
  6. 21 Mar, 2019 2 commits
  7. 20 Mar, 2019 1 commit
  8. 14 Mar, 2019 1 commit
  9. 13 Mar, 2019 1 commit
  10. 12 Mar, 2019 2 commits
  11. 10 Mar, 2019 1 commit
    • Seungha Yang's avatar
      tests: fdsrc: Exclude unit test on Windows · ec0e4ae0
      Seungha Yang authored
      Since elements_fdsrc.test_num_buffers uses blocking pipe on Windows,
      the test will never be finished. But emulating non-blocking fd without
      win32 APIs on Windows is a little tricky.
      ec0e4ae0
  12. 08 Mar, 2019 1 commit
  13. 06 Mar, 2019 3 commits
  14. 04 Mar, 2019 2 commits
  15. 28 Feb, 2019 1 commit
  16. 26 Feb, 2019 4 commits
  17. 25 Feb, 2019 2 commits
  18. 20 Feb, 2019 1 commit
  19. 19 Feb, 2019 1 commit
  20. 18 Feb, 2019 1 commit
  21. 15 Feb, 2019 2 commits
  22. 13 Feb, 2019 1 commit
  23. 12 Feb, 2019 1 commit
    • Tim-Philipp Müller's avatar
      buffer: store sequence number for metas · f62ee975
      Tim-Philipp Müller authored
      For metas where order might be significant if multiple metas are
      attached to the same buffer, so store a sequence number with the
      meta when adding it to the buffer. This allows users of the meta
      to make sure metas are processed in the right order.
      
      We need a 64-bit integer for the sequence number here in the API,
      a 32-bit one might overflow too easily with high packet/buffer
      rates. We could do it rtp-seqnum style of course, but that's a
      bit of a pain.
      
      We could also make it so that gst_buffer_add_meta() just keeps metas in
      order or rely on the order we add the metas in, but that seems too
      fragile overall, when buffers (incl. metas) get merged or split.
      
      Also add a compare function for easier sorting.
      
      We store the seqnum in the MetaItem struct here and not in the
      GstMeta struct since there's no padding in the GstMeta struct.
      We could add a private struct to GstMeta before the start of
      GstMeta, but that's what MetaItem effectively is implementation-
      wise. We can still change this later if we want, since it's all
      private.
      
      Fixes #262
      f62ee975
  24. 09 Feb, 2019 1 commit