Skip to content
Snippets Groups Projects
  1. May 31, 2021
  2. May 27, 2021
  3. May 24, 2021
  4. May 23, 2021
  5. May 16, 2021
  6. May 14, 2021
  7. May 12, 2021
  8. May 11, 2021
  9. May 07, 2021
  10. May 06, 2021
  11. May 04, 2021
    • François Laignel's avatar
      Introduce gst_element_request_pad_simple · 1a8dfdfc
      François Laignel authored
      The name `gst_element_get_request_pad()` is confusing to people
      learning GStreamer. `gst_element_request_pad_simple()` aims at
      providing the exact same functionality, while making it more
      explicit it is a simplified `gst_element_request_pad()`.
      
      `gst_element_request_pad_simple()` is consistent with other
      functions such as `gst_element_seek_simple`.
      
      This commit deprecates `gst_element_get_request_pad()` so that a
      compilation warning is emitted when used and incite developers
      to use the more explicit `gst_element_request_pad_simple()`.
      
      See also gstreamer/gstreamer-rs!743 (comment 886586)
      
      Part-of: <gstreamer/gstreamer!802>
      1a8dfdfc
  12. Apr 21, 2021
  13. Apr 19, 2021
    • Miguel París Díaz's avatar
      pad: clear probes holding mutex · fad60301
      Miguel París Díaz authored
      Protect clearing probes against concurrent modification which might happen
      due to dispose does NOT guarantee that the object is not used anymore, as
      it could be referenced again and so being continued used.
      So, as in the rest of places where probes hook list is used, on dispose
      it should be accessed holding the mutex "GST_OBJECT_LOCK (pad);" as
      GHookList is not thread-safe.
      
      Part-of: <gstreamer/gstreamer!798>
      fad60301
  14. Apr 16, 2021
    • Edward Hervey's avatar
      queue2: Refuse all serialized queries when posting buffering messages · 4eef67cc
      Edward Hervey authored and Edward Hervey's avatar Edward Hervey committed
      When posting buffering messages there are no safe places or timing to avoid
      deadlocks.
      
      Previously the code was trying to be "smart" by only forwarding serialized
      queries if the queue was empty ... but that could happen when queue2 hadn't yet
      posted a 100% buffering message. Meaning the pipeline might be paused and
      pushing a serialized query downstream might never complete.
      
      Therefore let's completely disable forwarding of serialized queries when
      `queue2` is used as a buffering element (meaning `ALLOCATION` and `DRAIN`
      queries).
      
      Part-of: <!796>
      4eef67cc
  15. Apr 12, 2021
  16. Apr 10, 2021
  17. Apr 08, 2021
  18. Apr 07, 2021
  19. Apr 06, 2021
  20. Apr 02, 2021
  21. Mar 31, 2021
  22. Mar 26, 2021
  23. Mar 24, 2021
  24. Mar 19, 2021
  25. Mar 18, 2021
Loading