1. 23 Sep, 2021 1 commit
  2. 21 Sep, 2021 1 commit
  3. 20 Sep, 2021 3 commits
  4. 16 Sep, 2021 1 commit
  5. 15 Sep, 2021 6 commits
  6. 12 Sep, 2021 1 commit
  7. 09 Sep, 2021 2 commits
  8. 07 Sep, 2021 1 commit
  9. 03 Sep, 2021 1 commit
  10. 02 Sep, 2021 1 commit
  11. 31 Aug, 2021 1 commit
  12. 30 Aug, 2021 2 commits
  13. 25 Aug, 2021 1 commit
  14. 24 Aug, 2021 1 commit
  15. 20 Aug, 2021 5 commits
  16. 18 Aug, 2021 2 commits
  17. 17 Aug, 2021 3 commits
    • Devarsh Thakkar's avatar
      ext: alsa: Fix fallback paths for setting buffer and period times · 297b1e68
      Devarsh Thakkar authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      Below fallback paths were introduced in
      if setting period time after buffer time failed :
      1) Set period time and then buffer time if it doesn't work
      2) Set only buffer time
      3) Set only period time
      These all were not functioning properly since they were using old
      copy of snd_pcm_hw_params_t which already had some fields set
      as per previous try and this was causing issues as driver was
      referring to that old value while trying to set them again in
      fallback paths.
      So now we always use the initial copy of snd_pcm_hw_params_t
      for every fallback  and same is also being done at
      Also we change the sequence to set period time earlier than
      buffer time since period bytes being the smaller unit, most of the times
      if underlying alsa device has a dependency then it is of period bytes
      to be a multiple of some value (as per underlying DMA constraint)
      and rest of the parameters like buffer bytes need to be adjusted
      as per period bytes.
      The same sequence is also followed in alsa-utils at
      Fix 2) and 3) scenarios by returning success if the exclusive setting is passed
      and not doing any further setting for buffer time or period time.
      Add new fallback path of not setting any buffer time and period time
      if all above fallback paths fail. The same is also being
      followed at aforementioned pulseaudio commit.
      In case of alsasink, remove the retry goto label, since it is not
      required anymore as fallback paths take care of setting default
      values if driver is not accepting any of the fallback paths.
      Use separate label for exit to free params structs and return err
      code. This also fixes leak in no_rate goto path in alsasink
      Part-of: <!1212>
    • Jakub Adam's avatar
      videoencoder: pass upstream HDR information through codec state · b4a00f78
      Jakub Adam authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      Don't copy HDR metadata from sink pad, because its caps may not have
      been set yet if GstVideoEncoder::negotiate is called from
      GstVideoEncoder::set_format, as e.g. vpx encoder does.
      Part-of: <!1175>
    • Jakub Adam's avatar
      videoutils: add HDR metadata fields to GstVideoCodecState · b3c7b9be
      Jakub Adam authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      Part-of: <!1175>
  18. 16 Aug, 2021 2 commits
    • Sebastian Dröge's avatar
      video-overlay-composition: Allow empty overlay compositions · a14f4f48
      Sebastian Dröge authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      Allowing to pass NULL to the constructor removes the need to
      special-case the first rectangle in calling code and generally
      simplifies application code.
      Part-of: <!1256>
    • Per Förlin's avatar
      gstrtspconnection: Add support to ignore x-server header reply · 535c02c7
      Per Förlin authored and Nirbheek Chauhan's avatar Nirbheek Chauhan committed
      When connecting to an RTSP server in tunnled mode (HTTP) the server
      usually replies with a x-server header. This contains the address
      of the intended streaming server. However some servers return an
      "invalid" address. Here follows two examples when it might happen.
      1. A server use Apache combined with a separate RTSP process to handle
         Https request on port 443. In this case Apache handle TLS and
         connects to the local RTSP server, which results in a local
         address or ::1 in the x-server reply. This address is
         returned to the actual RTSP client in the x-server header.
         The client will receive this address and try to  connect to it
         and fail.
      2. The client use a ipv6 link local address with a specified scope id
         fe80::aaaa:bbbb:cccc:dddd%eth0 and connects via Http on port 80.
         The RTSP server receives the connection and returns the address
         in the x-server header. The client will receive this address and
         try to connect to it "as is" without the scope id and fail.
      In the case of streaming data from RTSP servers like 1. and 2. it's
      useful to have the option to simply ignore the x-server header reply
      and continue using the original address.
      Part-of: <!1192>
  19. 13 Aug, 2021 1 commit
  20. 10 Aug, 2021 1 commit
    • Matthew Waters's avatar
      glbuffer: support persistent buffer mappings · 04856a38
      Matthew Waters authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      Requires OpenGL 4.4 or EXT_buffer_storage
      Current mesa exposes GL_ARB_buffer_storage when retrieving the relevant
      functions returns no-ops and causes failures.
      Improves throughput of uploads by roughly 30%-60% and download throughput by
      roughly 10-30% across depending on the exact scenario and hardware.
      Part-of: <!1191>
  21. 02 Aug, 2021 1 commit
  22. 30 Jul, 2021 2 commits