1. 28 Feb, 2019 1 commit
  2. 26 Feb, 2019 4 commits
  3. 25 Feb, 2019 2 commits
  4. 20 Feb, 2019 1 commit
  5. 19 Feb, 2019 1 commit
  6. 18 Feb, 2019 1 commit
  7. 15 Feb, 2019 2 commits
  8. 13 Feb, 2019 1 commit
  9. 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
  10. 09 Feb, 2019 1 commit
  11. 08 Feb, 2019 2 commits
    • Thibault Saunier's avatar
      device-provider: Allow notifying application of device changes · 97aa8238
      Thibault Saunier authored
      Thi introduces new APIs to post a `DEVICE_CHANGED` message on the
      bus so the application is notifies when a device is modified. For
      example, if the "defaultness" of a device was changed or any property
      that can be changed at any time. Atomically changing the device
      object notifying that way allow us to abtract away the internal threads.
      
      New APIS:
        - gst_message_new_device_changed
        - gst_message_parse_device_changed
        - gst_device_provider_device_changed
      97aa8238
    • Nirbheek Chauhan's avatar
      meson: Extract flex version using a regex inside a script · c164b88a
      Nirbheek Chauhan authored
      Different builds of Flex on different platforms output different strings
      in --version. For example:
      
      macOS:
      flex 2.5.35 Apple(flex-31)
      
      Windows:
      win_flex.exe 2.6.4
      C:\Program Files (x86)\GnuWin32\bin\flex.EXE version 2.5.4
      
      We need to look for a string that looks like a version, which means
      a regex till https://github.com/mesonbuild/meson/issues/1609 is fixed.
      
      Fixes #356
      c164b88a
  12. 05 Feb, 2019 1 commit
    • Nirbheek Chauhan's avatar
      misc: Fix various compiler warnings on MinGW · febfabb3
      Nirbheek Chauhan authored
      gstharness.c: Use G_GSIZE_FORMAT instead of hard-coding %zu
      error: unknown conversion type character 'z' in format [-Werror=format]
      
      gst-inspect.c: GPid is void* on non-UNIX, and we only use it on UNIX
      error: initialization makes pointer from integer without a cast [-Werror]
      
      gstmeta.c: Use and then discard value
      error: value computed is not used [-Werror=unused-value]
      
      With this, gstreamer builds with -Werror on MinGW
      febfabb3
  13. 29 Jan, 2019 4 commits
  14. 28 Jan, 2019 1 commit
  15. 26 Jan, 2019 1 commit
    • Nicolas Dufresne's avatar
      pad: Remove unneeded 64bit upcast in debug trace · c816ec4f
      Nicolas Dufresne authored
      The hook->hook_id is a gulong for which there are no portability issues
      when tracing in printf format with %lu. So use %lu and remove the upcast
      to 64 bit. This makes the code more consistent with everything else
      tracing that hook_id and other gulong id.
      c816ec4f
  16. 25 Jan, 2019 1 commit
    • Nicolas Dufresne's avatar
      gst-inspect: Re-add DEFAULT_LESS_OPTS with initial value · 35300f82
      Nicolas Dufresne authored
      Commit 56b4fbef refactored the pipe code
      to use GLib utility, but the patch was hading some other changed. LESS
      env was now hardcoded in the middle instead of from a define and was
      changed from FXR to -RX. The "-" is not even valid for LESS env, and
      with the lost of F, we would still use a pager when the content fits the
      terminal.
      35300f82
  17. 24 Jan, 2019 2 commits
    • Sebastian Dröge's avatar
      taglist: Remove (scope call) annotation from gst_tag_register() · 5688773b
      Sebastian Dröge authored
      This was added in 7fdb15d6 but it is wrong. (scope call) is for
      closures that only have to stay valid for the scope of the call, but the
      tag merge function has to stay valid for the whole lifetime of the
      application instead.
      
      There's no appropriate scope annotation for that so we have to skip
      these functions for now.
      5688773b
    • Seungha Yang's avatar
      tests: info: Fix spurious validation · 5b19d30d
      Seungha Yang authored
      Should be equality check, not assignment.
      Additionally, use fail_unless_equals_* macro for better readability
      and debugging easier, if possible.
      5b19d30d
  18. 23 Jan, 2019 1 commit
  19. 22 Jan, 2019 1 commit
  20. 17 Jan, 2019 5 commits
  21. 16 Jan, 2019 1 commit
  22. 15 Jan, 2019 1 commit
  23. 14 Jan, 2019 1 commit
    • Daniel Drake's avatar
      deviceprovider: fix counting number of times started · e0c9b045
      Daniel Drake authored
      GstDeviceProvider has a started_count private variable counter,
      and the gst_device_provider_start() documentation emphasizes the
      importance of balancing the start and stop calls.
      
      However, when starting a provider that is already started, the
      current code will never increment the counter more than once.
      
      So you start it twice, but it will have start_count 1, which is the
      maximum value it will ever see.
      
      Then when you stop it twice, on the 2nd stop, after decrementing the
      counter in gst_device_provider_stop():
      
        else if (provider->priv->started_count < 1) {
          g_critical
              ("Trying to stop a GstDeviceProvider %s which is already stopped",
              GST_OBJECT_NAME (provider));
      
      and the program is killed.
      
      Fix this by incrementing the counter when starting a device provider that
      was already started.
      e0c9b045
  24. 11 Jan, 2019 1 commit
  25. 10 Jan, 2019 1 commit
  26. 09 Jan, 2019 1 commit