On 02/10/2020 15:28, Fei Wang wrote:
Example cmdline:
ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -v verbose \
-c:v av1 -i input.ivf -pix_fmt yuv420p -vsync passthrough -f md5 \
-y out.md5
Signed-off-by: Fei Wang <[email protected]>
---
Changelog | 1 +
configure | 3 +
libavcodec/Makefile | 1 +
libavcodec/av1dec.c | 18 ++-
libavcodec/hwaccels.h | 1 +
libavcodec/vaapi_av1.c | 274 ++++++++++++++++++++++++++++++++++++++
libavcodec/vaapi_decode.c | 6 +
libavcodec/version.h | 2 +-
8 files changed, 304 insertions(+), 2 deletions(-)
create mode 100644 libavcodec/vaapi_av1.c
I think this is ok, but I can't test it myself. Can you rebase against the
recent changes in av1dec and retest that it is still good?
A kindof-related question: how does the selection of reference frames for skip
modes work? VAAPI isn't being given the SkipModeFrame array, and it doesn't
appear to have the order hints to be able to work out which frames it should be
using itself.
Thanks,
- Mark
_______________________________________________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
