[FFmpeg-devel] [FFmpeg-cvslog] avcodec/vdpau: Enable HEVC support for working Nvidia driver versions

Carl Eugen Hoyos ceffmpeg at gmail.com
Sun Jan 27 20:48:17 EET 2019


2019-01-27 19:43 GMT+01:00, Dominik 'Rathann' Mierzejewski
<dominik at greysector.net>:
> On Sunday, 27 January 2019 at 19:29, Carl Eugen Hoyos wrote:
>> 2019-01-27 19:06 GMT+01:00, Dominik 'Rathann' Mierzejewski
>> <dominik at greysector.net>:
>> > Hello,
>> >
>> > On Wednesday, 31 October 2018 at 03:44, ManojGuptaBonda wrote:
>> >> ffmpeg | branch: master | ManojGuptaBonda <mbonda at nvidia.com> | Mon Oct
>> >> 29
>> >> 13:57:54 2018 +0530| [4a6d5f3cadaabefe6c3548e575bb7e713997762f] |
>> >> committer: Philip Langdale
>> >>
>> >> avcodec/vdpau: Enable HEVC support for working Nvidia driver versions
>> >>
>> >> The driver bugs that caused decoded HEVC content to have an incorrect
>> >> memory layout have been fully fixed in the 410.xx driver release so
>> >> we can start exposing support.
>> >>
>> >> > http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=4a6d5f3cadaabefe6c3548e575bb7e713997762f
>> >
>> > I have a user requesting a backport of this and
>> > 4a976200d7853588336005a394dd31d905f5caf6
>> > to 4.0 branch which we use in Fedora/RPM Fusion 29:
>> > https://bugzilla.rpmfusion.org/show_bug.cgi?id=5149
>>
>> Wouldn't a user who uses an outdated version of FFmpeg
>> typically also use an outdated Nvidia driver?
>
> No. Why would you say that? First, 4.0.x is not outdated from
> where I'm sitting and second, we've updated the packaged
> nVidia drivers in RPM Fusion for F29 to 415 already.

Thank you for explaining, I misunderstood.

Why are you updating Nvidia drivers but not FFmpeg?
Do you expect that (current) 4.0 has less bugs
than the last 4.1 release?

Carl Eugen


More information about the ffmpeg-devel mailing list