1. 28 Mar, 2018 1 commit
  2. 07 Dec, 2017 1 commit
  3. 18 Sep, 2017 1 commit
  4. 14 Jul, 2017 1 commit
  5. 20 Jun, 2017 1 commit
  6. 04 May, 2017 1 commit
  7. 27 Apr, 2017 1 commit
  8. 07 Apr, 2017 1 commit
  9. 14 Mar, 2017 1 commit
    • Olivier Crête's avatar
      pulse example: Remove · d9cd0e2e
      Olivier Crête authored
      That example only tested the property probe interface, which has been removed.
      The same kind of thing can now be done with the generic gst-device-monitor tool.
      d9cd0e2e
  10. 24 Feb, 2017 2 commits
  11. 12 Jan, 2017 2 commits
  12. 14 Dec, 2016 1 commit
  13. 20 Nov, 2016 1 commit
  14. 01 Nov, 2016 2 commits
  15. 30 Sep, 2016 1 commit
  16. 14 Sep, 2016 1 commit
  17. 01 Sep, 2016 2 commits
  18. 26 Aug, 2016 1 commit
  19. 13 Jul, 2016 1 commit
  20. 11 Jul, 2016 2 commits
  21. 06 Jul, 2016 2 commits
  22. 24 Mar, 2016 2 commits
  23. 15 Mar, 2016 1 commit
  24. 01 Mar, 2016 1 commit
  25. 19 Feb, 2016 2 commits
  26. 24 Dec, 2015 2 commits
  27. 21 Dec, 2015 1 commit
  28. 14 Dec, 2015 1 commit
  29. 04 Dec, 2015 1 commit
    • Nicolas Dufresne's avatar
      vpxdec: Use GstMemory to avoid copies · 189c2918
      Nicolas Dufresne authored
      With the VPX decoders it's not simple to use downstream buffer pool,
      because we don't know the image size and alignment when buffers get
      allocated. We can though use GstAllocator (for downstream, or the system
      allocator) to avoid a copy before pushing if downstream supports
      GstVideoMeta. This would still cause a copy for sink that requires
      specialized memory and does not have a GstAllocator for that, though
      it will greatly improve performance for sink like glimagesink and
      cluttersink. To avoid allocating for every buffer, we also use a
      internal buffer pool.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=745372
      189c2918
  30. 25 Nov, 2015 1 commit
  31. 21 Oct, 2015 1 commit