1. 10 May, 2020 2 commits
  2. 05 May, 2020 1 commit
  3. 20 Apr, 2020 1 commit
  4. 24 Mar, 2020 1 commit
  5. 26 Feb, 2020 1 commit
    • Jan Schmidt's avatar
      clocksync: Add new clocksync element · 81d55fb4
      Jan Schmidt authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      The clocksync element is a generic element that can be
      placed in a pipeline to synchronise passing buffers to the
      clock at that point. This is similar to 'identity sync=true',
      but because it isn't GstBaseTransform-based, it can process
      GstBufferLists without breaking them into separate GstBuffers
      81d55fb4
  6. 13 Feb, 2020 1 commit
  7. 26 Dec, 2019 1 commit
    • Seungha Yang's avatar
      pluginfeature: Allow updating initial rank of plugin feature · 52706146
      Seungha Yang authored and Tim-Philipp Müller's avatar Tim-Philipp Müller committed
      Introducing "GST_PLUGIN_FEATURE_RANK" environment variable in order for users
      to adjust rank of plugin(s) via environment.
      
      A "feature" and "rank" key-value pair should be separable by ":",
      and each key-value pair is recognized per "," delimiters. The rank
      can be a numerical value or one of pre-defined rank values
      such as "NONE", "MARGINAL", "SECONDARY", and "PRIMARY" in case-insensitive manner.
      
      In addition to pre-defined { NONE, MARGINAL, SECONDARY, PRIMARY },
      "MAX" can be passed to key value used to ensure having a higher rank
      than other plugin features.
      
      Example)
      - GST_PLUGIN_FEATURE_RANK=qtdemux:256,h264parse:NONE
      Set rank of qtdemux plugin to 256 (primary) and 0 (none) for h264parse.
      52706146
  8. 13 Nov, 2019 1 commit
  9. 13 Oct, 2019 1 commit
  10. 06 Oct, 2019 1 commit
  11. 02 Jul, 2019 1 commit
  12. 01 Jun, 2019 1 commit
  13. 31 May, 2019 1 commit
  14. 25 May, 2019 1 commit
  15. 18 May, 2019 1 commit
  16. 16 May, 2019 7 commits
  17. 14 May, 2019 2 commits
  18. 13 May, 2019 5 commits
  19. 08 May, 2019 1 commit
  20. 22 Apr, 2019 1 commit
  21. 19 Apr, 2019 2 commits
  22. 18 Apr, 2019 1 commit
  23. 10 Apr, 2019 1 commit
  24. 01 Apr, 2019 1 commit
  25. 04 Mar, 2019 1 commit
  26. 26 Feb, 2019 1 commit
  27. 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