1. 18 Apr, 2019 2 commits
  2. 15 Apr, 2019 6 commits
  3. 11 Apr, 2019 2 commits
  4. 10 Apr, 2019 4 commits
  5. 09 Apr, 2019 2 commits
    • Víctor Manuel Jáquez Leal's avatar
      libs: encoder: h264,h265: initial and minimal QP can be zero · d4bc0cb6
      Víctor Manuel Jáquez Leal authored
      Currently the minimal value for either min_qp and init_qp are 1,
      but VA documentation specifiy that zero is also valid and means
      to ignore the quantiser.
      
      The default value is not changed though to avoid behaivor changes
      to users.
      d4bc0cb6
    • Haihao Xiang's avatar
      meson: build test-vaapicontext when using X11 · 81203a60
      Haihao Xiang authored and Víctor Manuel Jáquez Leal's avatar Víctor Manuel Jáquez Leal committed
      x11_dep and libva_x11_dep are optional and meson ignores these
      dependencies even if they are added into the dependency list.
      
      This fixes the error below when libva-x11 is not avaiblabe:
      
      cc -Itests/elements/tests@elements@@test-vaapicontext@exe
      -Itests/elements -I../../gstreamer-vaapi/tests/elements -I.
      -I../../gstreamer-vaapi/ -Igst-libs -I../../gstreamer-vaapi/gst-libs
      -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
      -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/orc-0.4
      -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
      -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
      -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/
      -I/usr/include/libdrm -I/usr/include/harfbuzz -I/usr/include/pango-1.0
      -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo
      -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2
      -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0
      -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall
      -Winvalid-pch -O2 -g -fvisibility=hidden -fno-strict-aliasing -pthread
      -DHAVE_CONFIG_H  -MD -MQ
      'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o'
      -MF
      'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o.d'
      -o
      'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o'
      -c ../../gstreamer-vaapi/tests/elements/test-vaapicontext.c
      ../../gstreamer-vaapi/tests/elements/test-vaapicontext.c:29:10: fatal
      error: va/va_x11.h: No such file or directory
       #include <va/va_x11.h>
      81203a60
  6. 01 Apr, 2019 1 commit
  7. 30 Mar, 2019 1 commit
  8. 29 Mar, 2019 3 commits
  9. 28 Mar, 2019 1 commit
  10. 26 Mar, 2019 1 commit
  11. 25 Mar, 2019 1 commit
  12. 21 Mar, 2019 2 commits
  13. 11 Mar, 2019 1 commit
  14. 04 Mar, 2019 1 commit
  15. 01 Mar, 2019 1 commit
  16. 27 Feb, 2019 1 commit
    • Víctor Manuel Jáquez Leal's avatar
      plugin: if any caps in downstream, negotiate raw video · 3e992d8a
      Víctor Manuel Jáquez Leal authored
      When downstream has any caps, vaapi should not shovel vaapi featured
      buffers, but rather plain raw video, assuming always the worst case
      scenario (downstream cannot handle featured video memory but raw
      system memory buffers).
      
      This patch query the peer caps without any filter, to know if
      donwstream just ask for any caps, if so jump to the color space
      checking, otherwise do the caps intersection and continue with the
      feature selection algorithm.
      
      Fixes: #139
      3e992d8a
  17. 26 Feb, 2019 2 commits
  18. 21 Feb, 2019 1 commit
    • He Junyan's avatar
      vaapivideomemory: Prefer same format for surface and image · ee21fd90
      He Junyan authored and Víctor Manuel Jáquez Leal's avatar Víctor Manuel Jáquez Leal committed
      
      
      We prefer to use the same format between image and surface for gst
      vaapi allocator. The old way may choose different formats between
      image and surface. For example, the RGBA image may have a NV12 surface.
      
      So we need to do format conversion when we put/get image to surface.
      
      Some drivers such as iHD can not support such conversion and always
      cause a data flow error. There may also have some performance cost
      for format conversion when put/get images.
      
      So we prefer to use the same format for image and surface in the
      allocator. If the surface can not support that format, we then
      fallback to find a best one as the surface format.
      
      Co-authored-by: Víctor Manuel Jáquez Leal's avatarVíctor Jáquez <vjaquez@igalia.com>
      ee21fd90
  19. 17 Feb, 2019 2 commits
  20. 16 Feb, 2019 3 commits
  21. 11 Feb, 2019 1 commit
  22. 08 Feb, 2019 1 commit