[FFmpeg-devel] [FFmpeg-cvslog] avcodec/vdpau: Enable HEVC support for working Nvidia driver versions
jamrial at gmail.com
Mon Jan 28 05:54:07 EET 2019
On 1/27/2019 3:43 PM, Dominik 'Rathann' Mierzejewski wrote:
> 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>:
>>> 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.
>>> I have a user requesting a backport of this and
>>> to 4.0 branch which we use in Fedora/RPM Fusion 29:
>> 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.
> If you're trying to say we can upgrade 4.0.x to 4.1.x without
> recompiling any dependent packages and you guarantee everything will
> work just like with 4.0.x, then I would be willing to entertain that
ffmpeg 4.1 is meant to be ABI compatible with 4.0, so you should be able
to replace the 4.0 libraries and anything linking to them should still
work without the need to be recompiled.
Now, "work just like with 4.0.x" is impossible to guarantee because
there were like five months of development between the two releases, and
some modules may behave slightly differently.
More information about the ffmpeg-devel