1. 20 May, 2016 2 commits
  2. 19 May, 2016 3 commits
  3. 18 May, 2016 1 commit
  4. 13 May, 2016 2 commits
  5. 11 May, 2016 5 commits
  6. 09 May, 2016 10 commits
  7. 06 May, 2016 1 commit
  8. 29 Apr, 2016 3 commits
  9. 27 Apr, 2016 2 commits
  10. 26 Apr, 2016 3 commits
  11. 25 Apr, 2016 1 commit
  12. 22 Apr, 2016 3 commits
    • Víctor Manuel Jáquez Leal's avatar
      vaapidecode: search driver in whitelist · 53851b0e
      Víctor Manuel Jáquez Leal authored
      If the backend driver vendor string is not in a white-list, and the
      environment variable GST_VAAPI_ALL_DRIVERS is not set either, the decoder will
      change it state from NULL to READY, hence the auto-plug mechanism will look
      for another decoder.
      
      This patch assumes the GstContext has already being shared along the pipeline
      and the element has a valid GstVaapiDisplay instance.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=764673
      53851b0e
    • Víctor Manuel Jáquez Leal's avatar
      plugins: rework set_context() vmethod definition · bccdda84
      Víctor Manuel Jáquez Leal authored
      In bug 757598 was added the set_context() vmethod chain up in
      GstVaapiPluginBase. But it is buggy, since the parent_class address is
      assigned to the last element which called gst_vaapi_plugin_base_class_init().
      
      No error has shown up since none of the element's base classes redefined
      set_context() vmethod from GstElement, so always the correct function was
      called. Still this code is wrong and this patch make it right.
      
      Since set_context() is the same code, a macro is used to implement that code
      in all the gst-vaapi elements.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=765368
      bccdda84
    • Víctor Manuel Jáquez Leal's avatar
      vaapipostproc: resize if negotiated and allocation caps are different · e519f2ea
      Víctor Manuel Jáquez Leal authored
      Since commit 859a2b2f, in vaapidecode, allocation query can be different from
      the negotiated caps.
      
      When connecting the vaapidecoder to the vaapipostprocessor, the last one will
      resize the frame to the negotiated, if and only if, some other parameter is
      activated to avoid the passthrough. If it is not, the surface won't be mapped
      into a image. If not, the image won't be resized and the output buffer would be
      mapped.
      
      This patch will break the passthrough if the allocation query is different
      from the negotiation caps, forcing the resizing.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=765095
      e519f2ea
  13. 18 Apr, 2016 4 commits