1. 10 Sep, 2019 1 commit
  2. 29 Jun, 2019 1 commit
  3. 29 Mar, 2019 1 commit
  4. 28 Feb, 2019 1 commit
  5. 27 Feb, 2019 1 commit
    • Haihao Xiang's avatar
      msdkdec: force the alignment of width/height to 16 for vp8/vp9 · a751b330
      Haihao Xiang authored
      MSDK library requires 16 alignment for vp8/vp9, otherwise a pipeline
      for vp8/vp9 decoding might fail.
      
      example pipeline:
      gst-launch-1.0 filesrc location=vp8_1280x720.webm ! matroskademux ! \
      msdkvp8dec ! fakesink
      
      0:00:00.150565444 10657 0x55c8484036d0 ERROR                msdkdec
      gstmsdkdec.c:1056:gst_msdkdec_handle_frame:<msdkvp8dec0>
      DecodeFrameAsync failed (invalid video parameters)
      a751b330
  6. 19 Feb, 2019 1 commit
  7. 31 Jan, 2019 2 commits
  8. 08 Jan, 2019 1 commit
  9. 23 Nov, 2018 1 commit
  10. 03 Jul, 2018 1 commit
    • Sreerenj Balachandran's avatar
      msdk: dec: Add dynamic-configuration change support · 1e95c03c
      Sreerenj Balachandran authored
      The patch adds a serios of changes to support dynamic resolution
      change and efficient utilization of resources.
      Major changes:
      
      -- Use MSDK's apis to retrieve the headers instead of only relying
      on upsteram notification. For eg: avc decoder requires SEI header
      information for dpb count calculation which we don't get from caps.
      
      -- For all codecs other than VP9, we force the reset of decoder
      if resoultion changes to fit with gstreamer flow. VP9 enfource
      the hard reset only if the new resolution is bigger.
      
      -- delay the src caps setting till msdk api's invokation in
      handle_frame to avoid caching multiple configuration values
      
      -- ensure pool negotiation is based on decoder's allocation_caps.
      
      --dynamic resoluttion change use an explicit allocation_query
      to reclaim the buffers before closing the decoder (thanks to v4l2dec)
      
      --In case if we don't get upstream notification of res change (for eg,
      this can can happen for vp9 frames with ivfheader where ivfparse
      is not able to notify the dynamic changes), we handle the the case
      based on MFX_ERR_INCOMPATIBLE_VIDEO_PARAM which is the return value
      of MFXVideoDECODE_DecodeFrameAsync
      
      -- calculate the minimum surfaces to be preallocated based on
      msdk suggestion, downstream requirement, async depth and scratch surface
      count for smooth display.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=796566
      1e95c03c
  11. 16 May, 2018 3 commits
  12. 13 Feb, 2018 1 commit
  13. 04 Nov, 2017 1 commit
  14. 01 Nov, 2017 1 commit
  15. 30 Oct, 2017 1 commit
  16. 12 Dec, 2016 2 commits
  17. 14 Nov, 2016 1 commit