[FFmpeg-trac] #8666(undetermined:new): ffmpeg hardware accel command line settings are inconsistent
FFmpeg
trac at avcodec.org
Wed May 13 00:34:42 EEST 2020
#8666: ffmpeg hardware accel command line settings are inconsistent
-------------------------------------+-------------------------------------
Reporter: Va1DER | Owner:
Type: enhancement | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by heleppkes):
Replying to [ticket:8666 Va1DER]:
>
> Examples:
> cuvid (decode) must be specified with with -c:v codec switch.
> cuda (decode) must be specified with -hwaccel cuda
>
-hwaccel is the primary method to trigger hardware decoding. The cuvid
decoder is deprecated, and uses the same hardware capabilities. With
-hwaccel you do not need to know what the input codec is.
> ffmpeg -i input.mkv -vencoder=software -c:v h264 output.mp4
> ffpmeg -i input.mkv -vencoder=cuda -c:v h264 output.mp4
> ffpmeg -i input.mkv -vencoder=qsv -c:v h264 output.mp4
>
I really don't see the advantage in this. You still need to know that its
called "qsv" or "cuda", and its longer to boot. -c:v h264_nvenc or -c:v
h264_qsv isnt really any different, just less verbose extra options.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8666#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list