mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-02-08 19:33:07 +00:00

History

Alexandre Courbot 9167a10db1 video: decoder: ffmpeg: fix H.264 decoding with ffmpeg in guest When decoding H.264, ffmpeg tries to set the frame format before receiving the first DRC event, which is currently rejected even though this is valid from the point of view of the client. We need to silently accept the temporary format and all queued output buffers until the initial DRC event is fired, even though we won't emit any frame. BUG=None TEST=`ffmpeg -codec:v h264_v4l2m2m -i Big_Buck_Bunny_720_10s_1MB.mp4 BBB-%d.png` completes successfully in the guest and produces valid frames. Change-Id: I9a190ab2748bd59ff57d54be681f2a1553d1c6a3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3841484 Auto-Submit: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>		2022-11-07 10:50:23 +00:00
..
src	video: decoder: ffmpeg: fix H.264 decoding with ffmpeg in guest	2022-11-07 10:50:23 +00:00
bindgen.sh	health-check: enforce blank line after copyright	2022-09-13 22:24:35 +00:00
build.rs	Update all copyright headers to match new style	2022-09-13 18:41:29 +00:00
Cargo.toml	Reland "Add a VAAPI wrapper crate"	2022-07-13 06:51:27 +00:00
libva-wrapper.h	Update all copyright headers to match new style	2022-09-13 18:41:29 +00:00
README.md	Reland "Add a VAAPI wrapper crate"	2022-07-13 06:51:27 +00:00

README.md

Libva Rust wrapper

Rust wrapper for libva. Provides safe libva abstractions for use within Rust code using its own bindgen-generated bindings.

This crate is used as part of the VirtIO Video VA-API backend. VA-API uses the GPU to perform the actual decoding/encoding of frames. In doing so, it frees the CPU for other uses and reduces power usage in the system. Hardware accelerated media workflows also tend to be faster than their software counterparts.

Note: This create requires the native libva library at link time. It also requires a VA-API driver to be installed on the system. The VA-API driver to use depends on the underlying hardware, e.g.: the implementation for Intel hardware is in intel-media-driver, whereas AMD hardware will depend on Mesa.

An easy way to see whether everything is in order is to run the vainfo utility. This is usually packaged with libva-utils or as a standalone package in some distributions. vainfo will print the VA-API version, the driver string, and a list of supported profiles and endpoints, i.e.:

vainfo: VA-API version: 1.13 (libva 2.13.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.2.2 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileNone                   : VAEntrypointStats
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      etc

For decoding, the desired profile must be supported under VAEntrypointVLD. For example, in order to decode VP8 media, this line must be present in the output of vainfo:

      VAProfileVP8Version0_3          : VAEntrypointVLD

Whereas to decode H264 Main profile media, this line must be present:

      VAProfileH264Main               : VAEntrypointVLD

For more information on VA-API and its usage within ChromeOS, see this guide.

For a brief introduction on how to use this crate, see the libva_utils_mpeg2vldemo test under src/lib.rs.