1. 31 Jan, 2021 1 commit
  2. 30 Jan, 2021 1 commit
  3. 28 Jan, 2021 3 commits
  4. 14 Jan, 2021 1 commit
  5. 13 Jan, 2021 1 commit
  6. 12 Jan, 2021 2 commits
  7. 11 Dec, 2020 1 commit
  8. 06 Dec, 2020 2 commits
  9. 04 Dec, 2020 1 commit
  10. 02 Dec, 2020 1 commit
  11. 20 Nov, 2020 2 commits
  12. 16 Nov, 2020 1 commit
  13. 05 Nov, 2020 1 commit
  14. 04 Nov, 2020 1 commit
  15. 02 Nov, 2020 1 commit
    • Chris White's avatar
      gstinfo: colorize PIDs in log messages · e231f1d3
      Chris White authored
      The PIDs on log lines were supposed to be colorized before, but the
      escape sequence was incorrect.  With this change, the code uses the
      correct sequence to colorize those PIDs.  E.g., instead of `\033[334m`
      (incorrect), use `\033[34m` (correct).
      This makes the log messages easier to read.  It also reduces the chance
      that a buggy terminal will choke on the invalid escape sequence.
      Part-of: <!691>
  16. 30 Oct, 2020 2 commits
  17. 29 Oct, 2020 1 commit
    • Nicolas Dufresne's avatar
      aggregator: Include min-upstream-latency in buffering time · c983df16
      Nicolas Dufresne authored
      While we can fixe the upstream latency using the min-upstream-latency, we
      are now forced to use queues (hence more thread) in order to store the pending
      data whenever we have an upstream source that has lower latency.
      This fixes the issue by allowing to buffer the fixed upstream latency. This is
      particularly handy on single core systems were having too many threads can
      cause serious performance issues.
      Part-of: <!684>
  18. 27 Oct, 2020 1 commit
  19. 26 Oct, 2020 1 commit
  20. 14 Oct, 2020 1 commit
  21. 13 Oct, 2020 1 commit
    • Mathieu Duponchelle's avatar
      gstvalue: don't write to const char * · a613240c
      Mathieu Duponchelle authored
      Our various deserializing functions require NULL terminators
      to not over consume substrings (eg fields of an array). Instead
      of writing a NULL terminator to the passed-in string, which may
      result in segfaults, make a copy of the substring we're interested
      Fixes #446
      Part-of: <!673>
  22. 12 Oct, 2020 1 commit
  23. 10 Oct, 2020 3 commits
  24. 03 Oct, 2020 4 commits
    • Víctor Manuel Jáquez Leal's avatar
      padtemplate: add missing annotation · f97a4e23
      Víctor Manuel Jáquez Leal authored
      Adds missing "transfer full" annotation for caps parameter in
      Part-of: <!660>
    • Mathieu Duponchelle's avatar
      gstmeta: intern registered impl string · e149981a
      Mathieu Duponchelle authored
      Subsequent lookups in the hashtable are probably better done
      on memory we're confident is allocated to us :)
      It was easy to trigger invalid reads by calling gst_meta_register
      with dynamically allocated memory, freeing that memory, then
      calling gst_meta_get_info()
      Part-of: <!657>
    • Seungha Yang's avatar
      info: Load DbgHelp.dll using g_module_open() · ca4edf67
      Seungha Yang authored
      ... and update meson file so that enable it only using required headers.
      "dependency(...)" is unlikely successful for Windows SDK libraries
      since it doesn't ship pkg-config file. So it needs to be changed
      to "find_library()" to link corresponding .lib file. That would
      result to most MSVC build system will link dbghelp.dll. However,
      one drawback of the change is that gstreamer-1.0.dll will mandate
      dbghelp.dll although it should be optional. So g_module_open() way
      can be the most safe way in this case.
      Part-of: <!659>
    • Matthew Waters's avatar
      padtemplate: mark documentation caps as may be leaked · 14228b63
      Matthew Waters authored
      The template itself is already marked as such and the caps, the
      documentation caps are a logical extension of those two.
      Part-of: <!658>
  25. 02 Oct, 2020 3 commits
  26. 01 Oct, 2020 1 commit
    • Sebastian Dröge's avatar
      aggregator: Wake up source pad in PAUSED<->PLAYING transitions · 56d69620
      Sebastian Dröge authored
      When going to PLAYING we will now have a clock and can stop waiting on
      the condition variable and instead start waiting on the clock if
      necessary for the current configuration.
      In the other direction when going to PAUSED the clock might have
      disappeared and we might need to wait on the condition variable again
      Part-of: <!653>
  27. 30 Sep, 2020 1 commit