vdpau: do not use buggy HEVC support by default

Multimedia / FFmpeg - wm4 [googlemail.com] - 3 July 2017 06:56 EDT

NVIDIA broke its own API when using VDPAU decoding. If you retrieve the decoded YUV data, or if you map the surfaces with GL interop, the result are interlacing artifacts. The only way to get non-broken data is by using the vdpau video mixer to convert it to RGB. There is no way to block the non-working operations in a reasonable way (a VdpVideoSurface has to support all operations).

NVIDIA refuses to fix this issue (they "fixed" it by making it work with the video mixer, but the rest is still broken). There is no sign of that changing.

Do not use HEVC by default with the generic hwaccle API. Detect whether it's the NVIDIA native implementation, and exit with an error. (The same thing work with the MESA implementation.)

As an escape hatch and to allow applications to use the decoder if they really want to (perhaps because they make sure to explicitly use the
video mixer), reuse AV_HWACCEL_FLAG_ALLOW_PROFILE_MISMATCH to disable this check.

Once NVIDIA fixes the bug, working driver versions could be detected, and it could be allowed again.

64ecb78b7 vdpau: do not use buggy HEVC support by default
libavcodec/vdpau.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)

  • Share