1. 23 Nov, 2018 2 commits
  2. 21 Nov, 2018 2 commits
  3. 15 Nov, 2018 2 commits
  4. 14 Nov, 2018 1 commit
  5. 13 Nov, 2018 1 commit
  6. 12 Nov, 2018 6 commits
  7. 11 Nov, 2018 2 commits
    • Sjoerd Simons's avatar
      glupload: dmabuf: be explicit about gl formats used · 989f5338
      Sjoerd Simons authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      Rather then letting gst_gl_memory_setup_buffer guess the GL format used
      for an eglimage after importing a dmabuf be explicit about it. This
      fixes issues where dmabuf import may have used another format then
      gst_gl_format_from_video_info would guess on the basis of the available
      GL extensions.
      In particular on etnaviv the gst_gl_format_from_video_info would
      assuming a luminance + alpha GL format is used for YUY2, but the dmabuf
      import will always use RG88. Which causes images to end up somewhat pink when
      displayed on the screen.
    • Sjoerd Simons's avatar
      gl/egl: Determine correct format on dmabuf import · 99ac4e66
      Sjoerd Simons authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      When importing an egl image from dmabuf gst_gl_format_from_video_info
      was used to work what the result GL format will be. Unfortunately that
      will only work if the conventional format and the choosen DRM fourcc for
      the format match up.
      On etnaviv platforms there is no support for GL_EXT_texture_rg, so the
      GL format chosen for YUY2 ends up being GST_GL_LUMINANCE_ALPHA. However
      DRM does not do luminance + alpha as it's a legacy GL thing, so the
      dmabuf import ends up using DRM_FORMAT_GR88.
      To fix this, tie the DRM_FORMAT and the GL format together so they
      always match up.
  8. 05 Nov, 2018 1 commit
  9. 01 Nov, 2018 3 commits
  10. 31 Oct, 2018 1 commit
  11. 30 Oct, 2018 10 commits
  12. 17 Oct, 2018 1 commit
  13. 15 Oct, 2018 1 commit
  14. 11 Oct, 2018 1 commit
  15. 10 Oct, 2018 1 commit
    • Stian Selnes's avatar
      rtpbasepayload: rtpbasedepayload: Add source-info property · f766b85b
      Stian Selnes authored and Olivier Crête's avatar Olivier Crête committed
      Add a source-info property that will read/write meta to the buffers
      about RTP source information. The GstRTPSourceMeta can be used to
      transport information about the origin of a buffer, e.g. the sources
      that is included in a mixed audio buffer.
      A new function gst_rtp_base_payload_allocate_output_buffer() is added
      for payloaders to use to allocate the output RTP buffer with the correct
      number of CSRCs according to the meta and fill it.
      RTPSourceMeta does not make sense on RTP buffers since the information
      is in the RTP header. So the payloader will strip the meta from the
      output buffer.
  16. 04 Oct, 2018 5 commits