On 05/11/2020 15:53, Hendrik Leppkes wrote:
---
Changelog | 1 +
configure | 7 +
libavcodec/Makefile | 2 +
libavcodec/av1dec.c | 25 +-
libavcodec/dxva2.c | 10 +-
libavcodec/dxva2_av1.c | 504 +++++++++++++++++++++++++++++++++++++++++
libavcodec/hwaccels.h | 3 +
libavcodec/version.h | 2 +-
8 files changed, 550 insertions(+), 4 deletions(-)
create mode 100644 libavcodec/dxva2_av1.c
...
diff --git a/libavcodec/dxva2_av1.c b/libavcodec/dxva2_av1.c
new file mode 100644
index 0000000000..d04c96becf
--- /dev/null
+++ b/libavcodec/dxva2_av1.c
@@ -0,0 +1,504 @@
...
+ // XXX: setting the StatusReportFeedbackNumber breaks decoding on some
drivers
+ // we never use the status reporting functionality, so just skip on that
+ //pp->StatusReportFeedbackNumber = 1 + DXVA_CONTEXT_REPORT_ID(avctx,
ctx)++;
If it's worth mentioning this at all then it would probably help to note
exactly what drivers are breaking.
+ return 0;
+}
+
Is there is an Intel implementation of this yet? Maybe poke one of the Intel
people to try it if possible.
I don't have anything to test this, but from just reading through it looks
pretty good to me.
Thanks,
- Mark
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
