Changes between Version 81 and Version 82 of HWAccelIntro

Timestamp:

Jul 20, 2022, 2:39:17 PM (4 years ago)

Author:

Balling

Comment:

--

HWAccelIntro

@@ -80 +80 @@
 Note that VDPAU cannot be used to decode frames in memory, the compressed frames are sent by libavcodec to the GPU device supported by VDPAU and then the decoded image can be accessed using the VDPAU API. This is not done automatically by FFmpeg, but must be done at the application level (check for example the {{{ffmpeg_vdpau.c}}} file used by {{{ffmpeg.c}}}). Also, note that with this API it is not possible to move the decoded frame back to RAM, for example in case you need to encode again the decoded frame (e.g. when doing transcoding on a server).
 
-Several decoders are currently supported through VDPAU in libavcodec, in particular H.264, MPEG-1/2/4, and VC-1.
+Several decoders are currently supported through VDPAU in libavcodec, in particular H.264, MPEG-1/2/4, and VC-1, AV1.
 
 = VAAPI =
@@ -177 +177 @@
 == NVDEC/CUVID == 
 
-NVDEC offers decoders for H.264, HEVC, MJPEG, MPEG-1/2/4, VP8/VP9, VC-1. Codec support varies by hardware (see the [https://developer.nvidia.com/video-encode-decode-gpu-support-matrix GPU compatibility table]).
+NVDEC offers decoders for H.264, HEVC, MJPEG, MPEG-1/2/4, VP8/VP9, VC-1, AV1. Codec support varies by hardware (see the [https://developer.nvidia.com/video-encode-decode-gpu-support-matrix GPU compatibility table]).
 
 Note that FFmpeg offers both NVDEC and CUVID `hwaccel`s. They differ in how frames are decoded and forwarded in memory.
@@ -213 +213 @@
 
 The {{{-hwaccel_device}}} option can be used to specify the GPU to be used by the hwaccel in ffmpeg.
+
+AV1 NVDEC HW decoding requires using -c:v av1:
+
+
+{{{
+ffmpeg -hwaccel nvdec -c:v av1 -i input_av1.mp4 output.ts
+}}}