Am 04.10.2017 um 11:05 schrieb wm4:
On Tue, 3 Oct 2017 07:17:25 -0700
Philip Langdale <phil...@overt.org> wrote:

I'd propose to use this as a chance to get in line with nvidias new
naming, and call the new cuvid decoder/hwaccel nvdec. This is quite a
deviation from libav, but we need to rename it anyways, so might as
well pick an entirely different name.

I support this.

Seems like the only thing we actually need to rename is the cuvid.c
source file. I can keep the current rename, or rename the new Libav
one, whatever you prefer.

As it's just one file to rename for the current self-contained cuvid decoder, that would be my preferred candidate.

The AVHWAccels for the FFmpeg cuvid decoders can be removed as soon as
Mark Thompsons patches here get in:
https://lists.libav.org/pipermail/libav-devel/2017-October/084967.html

There doesn't actually need to be a separate configure switch for the
cuvid hwaccel, and --enable-cuvid would enable both. A user can
explicitly enable or disable the individual hwaccels and decoders to
get fine control. So there's no name conflict either as soon as the
fake AVHWAccels go.

Yeah, in that case there is no need to rename to nvdec.

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to