1. 11 Dec, 2020 3 commits
  2. 10 Dec, 2020 7 commits
  3. 08 Dec, 2020 1 commit
  4. 07 Dec, 2020 5 commits
  5. 04 Dec, 2020 3 commits
    • Thibault Saunier's avatar
      gst: Add new structure/caps/_to_string using the brackets for nesting · c35d4712
      Thibault Saunier authored
      This adds `gst_structure_serialize` and `gst_caps_serialize` which use
      the newly introduced bracket delimiters for nested structures.
      Part-of: <!532>
    • Thibault Saunier's avatar
    • Thibault Saunier's avatar
      structure: Add support for brackets as nested structures/caps specifiers · 322caf88
      Thibault Saunier authored
      This introduces a more human friendly syntax to specify nested
      structures It does so by using 2 different markers for opening and
      closing them instead of abusing quotes which lead to requiring an insane
      amount of escaping to match nesting levels.
      The brackets (`[` and `]`) have been chosen as they avoid complex
      constructions with curly brackets (or lower/higher than signs) where you
      could have structures embedded inside arrays (which also use curly
      brackets), ie. `s, array=(structure){{struct}}` should be parsed as an
      array of structures, but the cast seems to imply something different. We
      do not have this issue with brackets as they are currently used for
      ranges, which can only be casted to numeric types.
      This commit does not make use of that new syntax for serialization as
      that would break backward compatibility, so it is basically a 'sugar'
      syntax for humans. A notice has been explicitly made in the
      documentation to let the user know about it.
      Part-of: <gstreamer/gstreamer!532>
  6. 03 Dec, 2020 1 commit
  7. 02 Dec, 2020 3 commits
  8. 20 Nov, 2020 1 commit
  9. 10 Nov, 2020 1 commit
  10. 06 Nov, 2020 1 commit
    • Edward Hervey's avatar
      systemclock: Use clock_nanosleep for higher accuracy · 17feeb1b
      Edward Hervey authored
      The various wait implementation have a latency ranging from 50 to 500+
      microseconds. While this is not a major issue when dealing with a low number of
      waits per second (for ex: video), it does introduce a non-negligeable jitter for
      synchronization of higher packet rate systems.
      The `clock_nanosleep` syscall does offer a lower-latency waiting system but is
      unfortunately blocking, so we don't want to use it in all scenarios nor for too
      This patch makes GstSystemClock use clock_nanosleep (if available) as such:
      * Any wait below 500us uses it
      * Any wait below 2ms will first use the regular waiting system and then
        #	modified:   gst/gstsystemclock.c
      Part-of: <gstreamer/gstreamer!688>
  11. 05 Nov, 2020 5 commits
  12. 04 Nov, 2020 4 commits
  13. 31 Oct, 2020 1 commit
    • Chris White's avatar
      gstinfo: colorize PIDs in log messages · e74040b4
      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: <gstreamer/gstreamer!689>
  14. 30 Oct, 2020 1 commit
  15. 29 Oct, 2020 1 commit
  16. 27 Oct, 2020 1 commit
  17. 22 Oct, 2020 1 commit
    • Philippe Normand's avatar
      devicemonitor: Stop only the already started providers · 41677a52
      Philippe Normand authored
      If a device provider fails to start (for instance the pulseaudio provider unable
      to connect to the PulseAudio daemon) then the monitor should not keep track of
      it in its `started` providers list. Otherwise a false positive critical warning
      would be raised.
      This patch also switches the started_count type from bool to int, for
      consistency. This is a counter, after all.
      API: gst_device_provider_is_started
      Part-of: <!679>