Changes between Version 91 and Version 92 of HWAccelIntro

Timestamp:

Jan 18, 2024, 4:59:34 AM (3 years ago)

Author:

Roger Pack

Comment:

Probably right?

HWAccelIntro

@@ -249 +249 @@
 }}}
 
+Here's an example using scale_cuda and encoding in hardware, scale_cuda is available if compiled with ffnvcodec and `--enable-cuda-llvm` (default is on, requires nvidia llvm to be present at runtime):
+
+{{{
+ffmpeg -hwaccel cuda -hwaccel_output_format cuda -i file.mkv -noautoscale -filter_complex [0:0]scale_cuda=1280:-2[out] -map [out] -c:v hevc_nvenc -cq 28 output.mp4
+}}}
+
 == cuda-nvcc and libnpp ==
 
@@ -256 +262 @@
 }}}
 
-Both of these are basically "older" cuvid things that require the nvidia SDK to be present when compiled and run.  libnpp provides scale_npp (and a few other filters) whereas ffnvcodec provides scale_cuda ("GPU accelerated video resizer"), and a few other filters if you also configure it with `--enable-cuda-llvm` (requires nvidia llvm to be present at runtime).  They might have different options/flexibility.  Might be similar performance.  These have funky licensing (nonfree).
+Both of these are basically "older" cuvid options that require the nvidia SDK to be present when compiled and run.  libnpp provides scale_npp (and a few other _npp filters).  They might have different options/flexibility than their XX_cuda equivalent.  Might be similar performance.  These have more funky licensing (nonfree).  cuda-nvcc has basically been replaced with ffnvcodec + cuda-llvm, scale_npp with scale_cuda.
 
 = libmfx (Intel Media SDK) =