1. 08 Jul, 2020 1 commit
    • Víctor Manuel Jáquez Leal's avatar
      vaapisink: rank it as secondary · 13d090b5
      Víctor Manuel Jáquez Leal authored
      iHD doesn't provide a full implemention for rendering surfaces and
      i965 has problems in wayland. And I suspect this path is followed
      by other driver implementations.
      
      This patch demotes the rank of vaapisink to secondary, so it will
      not be autoplugged avoiding bad experience of users.
      
      Part-of: <!336>
      13d090b5
  2. 07 Jul, 2020 1 commit
  3. 05 Jul, 2020 3 commits
  4. 03 Jul, 2020 2 commits
    • He Junyan's avatar
      libs: encoder: h265: no need to check the high compression tune. · abea5e81
      He Junyan authored
      The h265 encoder just support tune mode:
        (0): none             - None
        (3): low-power        - Low power mode
      So, no need to check and set the high compression parameters.
      
      And by the way, the current ensure_tuning_high_compression manner
      of choosing the hightest profile idc as the best compression profile
      is not correct. Unlike h264, in h265 the higher profile idc number
      does not mean it has more compression tools, and so it has better
      compression performance. It may even be un-compatible with the lower
      profile idc. For example, the SCREEN_CONTENT_CODING profile with idc
      9 is not compatible with 3D_MAIN profile with idc 8.
      
      Part-of: <!348>
      abea5e81
    • Tim-Philipp Müller's avatar
      Back to development · 19903e1a
      Tim-Philipp Müller authored
      19903e1a
  5. 02 Jul, 2020 1 commit
  6. 23 Jun, 2020 1 commit
  7. 22 Jun, 2020 2 commits
  8. 19 Jun, 2020 3 commits
  9. 17 Jun, 2020 1 commit
    • Michael Olbrich's avatar
      libs: wayland: display: only handle the first output · 4b2f7a18
      Michael Olbrich authored
      Right now, all outputs are handled. The means that the registry object for
      all but the last are leaked. As a result the sizes are not used correctly.
      
      With two outputs, at first the mode and physical size of the second output
      are used. If the first output changes the mode, then the physical size of
      the second output is used in combination with the resolution of the first
      output. The resulting pixel aspect ratio is incorrect.
      
      There seems to be no way to determine on which output the window is shown,
      so just use the first one to get consistent results.
      
      Part-of: <!341>
      4b2f7a18
  10. 11 Jun, 2020 1 commit
    • He Junyan's avatar
      plugins: pluginbase: Do not destroy display when _close() · 72c4a161
      He Junyan authored
      When the element's state changes to NULL, it can still receive
      queries, such as the image formats. The display is needed in such
      queries but not well protected for MT safe.
      For example, ensure_allowed_raw_caps() may still use the display
      while it is disposed by gst_vaapi_plugin_base_close() because of
      the state change.
      
      We can keep the display until the element is destroyed. When the
      state changes to NULL, and then changes to PAUSED again, the display
      can be correctly set(if type changes), or leave untouched.
      
      Fix: #260
      Part-of: <!343>
      72c4a161
  11. 09 Jun, 2020 1 commit
  12. 05 Jun, 2020 17 commits
  13. 03 Jun, 2020 4 commits
  14. 27 May, 2020 2 commits